Change Details

As a sprint team, we would like the option to measure work-in-progress (WIP) limits based on card count, to more closely adhere to Kanban standards. On Wikimedia Phabricator we have Points enabled. So, at the moment, a Task has 0 Points as default. So, WIP limits are shown as a total of Story Points and it's not indicative on the actual amount of Task. Current situation: - the "Points count" on a Workboard column is 0, if the column is full of un-Pointed Tasks - WIP cannot be measured by the Kanban standard of task count (it is uncommon for Kanban to use WIP with points - or otherwise it's very uncommon to have a Task = zero by default) Desired situation: - as default, a Task without a Point is assumed as 1 Point - as default, the sum of Task points is therefore the sum of the Tasks Proposal n. 1 - an option: - an option to change a board to show WIP by task count in a column, rather than point total (or, alternatively, replace the existing functionality with this one) - preferably, the option is on the board itself, and not in editing the project It's been suggested that simply defaulting all tasks to 1 point solves this issue. However, that raises other issues (for instance, some teams may already be using the Story Points field for actual story-pointing). Original upstream ticket: https://secure.phabricator.com/T10915 Original Wikimedia ticket: https://phabricator.wikimedia.org/T120042

As a sprint team, we would like the option to measure work-in-progress (WIP) limits based on card count, to more closely adhere to Kanban standards. On Wikimedia's Phabricator instance we have Points enabled. So, at the moment, a Task has 0 Points as default. At the moment, WIP limits are shown as a total of Story Points, but this is a misuse of story points. This means that - if a column is filled with un-pointed tasks, the WIP stays at 0. Bugs are commonly 0 points. - WIP is not measured by the Kanban standard of task count. It is uncommon for Kanban to use WIP with points. Acceptance Criteria: - an option to change a board to show WIP by task count in a column, rather than point total (or, alternatively, replace the existing functionality with this one) - preferably, the option is on the board itself, and not in editing the project It's been suggested that simply defaulting all tasks to 1 point solves this issue. However, that raises other issues (for instance, some teams may already be using the Story Points field for actual story-pointing). Original upstream ticket: https://secure.phabricator.com/T10915 Original Wikimedia ticket: https://phabricator.wikimedia.org/T120042

As a sprint team, we would like the option to measure work-in-progress (WIP) limits based on card count, to more closely adhere to Kanban standards. On Wikimedia's Phabricator instance we have Points enabled. So, at the moment, a Task has 0 Points as default. At the moment, SoWIP limits are shown as a total of Story Points, WIP limits are shown as a totalbut this is a misuse of Sstory Points and it's not indicative on the actual amount of Taskpoints. Current situation: - the "Points count" on a Workboard column is 0, if the column is full of un-Pointed TasksThis means that - WIP cannot be measured by the Kanban standard of task count (it is uncommon for Kanban to use WIP with points - or otherwise it's very uncommon to have a Task = zero by default) Desired situation:if a column is filled with un-pointed tasks, the WIP stays at 0. Bugs are commonly 0 points. - as default, a Task without a Point is assumed as 1 Point - as default,- WIP is not measured by the Kanban standard of task count. the sum of Task points is therefore the sum of the TasksIt is uncommon for Kanban to use WIP with points. Proposal n. 1 - an option:Acceptance Criteria: - an option to change a board to show WIP by task count in a column, rather than point total (or, alternatively, replace the existing functionality with this one) - preferably, the option is on the board itself, and not in editing the project It's been suggested that simply defaulting all tasks to 1 point solves this issue. However, that raises other issues (for instance, some teams may already be using the Story Points field for actual story-pointing). Original upstream ticket: https://secure.phabricator.com/T10915 Original Wikimedia ticket: https://phabricator.wikimedia.org/T120042