Iterate with Principle – The Plan
Agile
in a Flash by Jeff Langr and Tim Ottinger (card #25)
> Team commits to stories they
can complete
> Team works stories from
prioritized card wall
> Team minimizes stories in
process
> Team collaborates daily
> Customer accepts only
completed stories
> Team reflects and commits to
improvements
--
Team
commits to stories they can complete. Start each iteration with a short planning
session to understand the customer’s stories and determine what the team is
confident they can deliver.
Team
works stories from prioritized card wall. The customer posts prioritized stories;
your team selects the highest-priority story and moves it to an in-progress bucket.
The card wall, real or virtual, is visible to everyone.
Team
minimizes stories in process. Your team works on the smallest
sensible number of stories at once, maximizing completion rate so that many
stories are truly done well before iteration’s end.
Team
collaborates daily.
Having few stories in process means you must collaborate frequently throughout
the day. A sole stand-up meeting isn’t enough.
Customer
accepts only completed stories. Stories must pass all programmer and
acceptance tests. Anything less than 100 percent gets your team zero credit;
incomplete work provides no business value. Don’t over-commit.
Team
reflects and commits to improvements. Iterations are opportunities for incremental
change, whether to improve quality, throughput, morale, or any other process
and team concerns. Run a retrospective!
Everything else is implementation
details, which are up to your team to determine.
No comments:
Post a Comment