17
Consumed Story Points: An Agile Anti-Pattern
"Consumed points" are a sort of burn-down metric that some practitioners use to track progress of a story against its original estimates. It's intended to show percentage of work completed, estimate overruns, or to reduce the need for collaborative communication about story status.
In my coaching practice the ...
3
Bottomline: go for the approach that'll help you solve the end user needs (features or bugfixes) faster.
A task should reflect the issue from end users view. You can do a triage, but I'd avoid rephrasing what the user has complained about.
There are three main reasons to stick to user wording:
it's a waste of time to rewrite what's already written
...
2
It sounds like the underlying challenge you are facing is a lot of items spilling over sprint-to-sprint. Otherwise, you could have one board, pull from the product backlog into a sprint backlog, work those items to done, then pull the next set in the following sprint.
A key part of using sprints is that the timebox provides a constraint. Among other values,...
2
My answer is not a canonical answer but rather my observations and opinions from years of practice.
I have found that project teams typically detest and avoid these types of logs no matter if the project methods are agile or not. And I opine the problem is with the governance around the logs themselves vice the concept of having a log to record things.
...
1
My organization uses hierarchical Kanban boards. We use what is known as SAFe (Scaled Agile Framework for Enterprises).
LeanKit is one product that supports this, but there are others too. Basically you have three different steps in the hierarchy.
Top level: These are enterprise epics and we time box them by quarter. They are organization level goals, very ...
Only top voted, non community-wiki answers of a minimum length are eligible
