@yot88 Work in iterations 2 weeks iterations from mid-week to mid-week releasable product at the end of each iteration continuous integration -> continuous deployment Deadlines help to focus : limit wip
@yot88 Planning -3 players Product Owner played by a product manager, or a BA The creators Software engineers, Testers, UX, UI,… The facilitator Dedicated or not Product ownership is considered a practice rather than a role.
@yot88 Planning -artefacts vertical slices of business functionality from multiple projects or products Blue cards Tasks related to blue cards Bugs White cards Red cards Planning board Planning poker
@yot88 Retrospective “Teams may also hold a retrospective as part of the iteration end routine, although not all teams hold retrospectives, and even those who do may not hold them at every iteration.” Formal or not (dialogue)
@yot88 Work in routine Event Frequency Iteration Every 2 weeks –10 working days Stand-up meeting Everyday -Maximum 15 Minutes Iteration review meeting End of every iteration 20 minutes at end of Iteration Retrospective event End of every iteration Formal retrospective End of every iteration (new teams) (60-90 minutes) every second (mature teams) Informal retrospective Every second iteration (30mins) for mature teams Demo At least every iteration which does not release Release Minimum quarterly high-performing teams will release many times during Iteration Sanitize the board & count the points
@yot88 Plan beyond the iteration The quarterly plan looks at most 12 weeks into the future Roadmap looks at the next quarter Iteration plan : output of the next two weeks More certainty Filled to approximately the capacity of each iteration : WIP limit for iterations
@yot88 Plan beyond the iteration Quarter & Roadmap are only horizons planning != scheduling Plan = looking into the future to learn about what might happen : perhaps preparefor it with Design thinking for example
@yot88 Goodhart ‘s law if a team tries to target a certain number of points, it will meet its goal, but may not do any more work. Such teams exhibit inflation in estimates : exactly as with financial inflation, the numbers are bigger but the value less.
@yot88 Kanban-style flow Xanpanallows both planned and unplanned work Work can flow from iteration to iteration Blue cards must bring value (Small stories regularly don’t)
Quality is free All successful software needs rework how easy is the rework? Low quality makes rework harder, and therefore slower. High quality makes rework easier, and therefore faster.
Poor quality Rework destroys flow stories and tasks can’t truly be considered ‘done’ hidden work is flowing between iterations Metrics are destroyed Inordinate amounts of time prioritizing, reporting, doing rework instead of delivering value inordinate amounts of money on testing resources and cycles
@yot88 Just do it : action over words Keep or drop Identify a practice, tool, technique, whatever from somewhere else. Decide what it would mean to your team: what would you do differently? Set a time frame Make the change at the end of the period : check
thirion
oripsolob
fullfull
asial_edu
utsumit
signer
2720japanoke
matleenalaakso
yokokohno
kakikbe
ashitanoterakoya
wingnus
cassininazir
eitanlees
revolveconf
bkeepers
mclloyd
eileencodes
garrettdimon
geeforr
thekraken
cherdarchuk
smashingmag
philnash