Difference between revisions of "Start what you finish and finish what you start"

From Pearl Language
Jump to navigation Jump to search
(Similar to {{p|stop starting and start finishing}}.)
(Refactor + embellish.)
Line 3: Line 3:
|theme=Agile, Kanban
|theme=Agile, Kanban
|context=evolving a product or project.
|context=evolving a product or project.
|wish in a single line=ka-ching a day makes product owner say hurray
|wish in a single line=ka-ching a day makes product owner say hurray.
|therefore in a single line=Work the work flow from back to front and help promote items closest to the end of the flow and in your area of skill if at all possible. Focus on increasing liquidity.
|therefore in a single line=Work the work flow from back to front and help promote items closest to the end of the flow and in your area of skill if at all possible. Focus on increasing liquidity.
|wish={{p|ka-ching a day makes product owner say hurray}}. Progressing the items closest to the finish take the least amount of effort and start generating returns from the moment they finish.
|wish={{p|ka-ching a day makes product owner hurray}}. You want your work to have some impact, outcome. You want to get things done. Progressing the items closest to the finish take the least amount of effort and start generating returns from the moment they finish, while opening up a slot that can be replenished with new work.
|therefore=Starting at the back from your work flow, work on progressing any item if you have the skills; or fix a bottleneck if you have the skills; or pull in work from the queue; or find other value added work that will increase liquidity.
|background=One of the core dysfunctions in {{p|scrum}} is pulling all items from the {{p|sprint backlog}} into progress, working on all of them in parallel, and, maybe, finishing them stressfully just before the end of the {{p|sprint}}. The {{p|burn down chart}} shows the ‘student signature’ rather than the healthier gradual, daily reduction of work remaining. The {{p|scrum board}} should display a ‘snow plow pattern’ rather than a “vertical bar pattern’.
 
Having all work {{state|in progress}} creates distress, uncertainty, inconvenience, and makes planning harder. An effective way to address this is by putting a {{p|work in progress limit}} on the {{state|in progress}} state that compels the {{p|squad}} to start working on a new item if and only if finishing one of the items in {{state|in progress}}.
 
|therefore=Start only what you will finish, and finish what you start before starting something new. Starting at the back from your work flow, work on progressing any item if you have the skills; or fix a bottleneck if you have the skills; or pull in work from the queue; or find other value added work that will increase liquidity.
|new=Similar to {{p|stop starting and start finishing}}.
|new=Similar to {{p|stop starting and start finishing}}.
}}
}}


{{Source}}
A.k.a. [[Stop Starting. Start Finishing]]
 
==Sources==
*http://en.wikipedia.org/wiki/Little's_law
 
{{Source
|author=Martien van Steenbergen,
|coder={{mvs}}
}}

Revision as of 10:24, 20 April 2013

…evolving a product or project.

✣  ✣  ✣

{{{wish full}}}

One of the core dysfunctions in scrum is pulling all items from the sprint backlog into progress, working on all of them in parallel, and, maybe, finishing them stressfully just before the end of the sprint. The burn down chart shows the ‘student signature’ rather than the healthier gradual, daily reduction of work remaining. The scrum board should display a ‘snow plow pattern’ rather than a “vertical bar pattern’.

Having all work in progress creates distress, uncertainty, inconvenience, and makes planning harder. An effective way to address this is by putting a work in progress limit on the in progress state that compels the squad to start working on a new item if and only if finishing one of the items in in progress.

Therefore:

{{{therefore full}}}

✣  ✣  ✣

Similar to stop starting and start finishing.


✣  ✣  ✣

[[wish::ka-ching a day makes product owner hurray. You want your work to have some impact, outcome. You want to get things done. Progressing the items closest to the finish take the least amount of effort and start generating returns from the moment they finish, while opening up a slot that can be replenished with new work.|]]

A.k.a. Stop Starting. Start Finishing

Sources