Your SlideShare is downloading. ×
How to Plan Agile Iterations
How to Plan Agile Iterations
How to Plan Agile Iterations
How to Plan Agile Iterations
How to Plan Agile Iterations
How to Plan Agile Iterations
How to Plan Agile Iterations
How to Plan Agile Iterations
How to Plan Agile Iterations
How to Plan Agile Iterations
How to Plan Agile Iterations
How to Plan Agile Iterations
How to Plan Agile Iterations
How to Plan Agile Iterations
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

How to Plan Agile Iterations

1,854

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,854
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • \n
  • \n
  • \n
  • - Relative estimation is easier\n- It is easier in groups\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Transcript

    • 1. Planning MeetingA hands-on guide to running an Agile Planning Meeting
    • 2. Complexity Pieces Systems PRD/MRD Stories Hypothesis Experts Logistics Generalists Emergent Specialists Stochastic StakeholdersDeterministic Reflection Gantt Charts Feedback LoopsUp-front Design Patterns Fractal Technical Dynamic Social Complexity Complexity Complexity When software is socially complex. (There isn’t a right or wrong way.)
    • 3. Cone of uncertainty“statistically predictable levels of project estimate uncertainty at each stage of the project” [Courtesy Jeff Atwood & Steve McConnell] http://www.codinghorror.com/blog/2006/06/the-mysterious-cone-of-uncertainty.html
    • 4. Relative Estimation Breed Height (cm) Relative Terrier Bulldog Labrador Saint Bernard Poodle Great DaneGerman Shephard
    • 5. Fractal Rhythm Release (Epics & Themes) Iteration (Stories) Day (Tasks)We are here
    • 6. Stories vs Tasks• stories have value to stakeholders • seek feedback and test hypothesis • work as one • delivered in full (binary)• tasks may not and will expand to fill time
    • 7. Release / LaunchPrioritized Backlog (200sp)1. Lorem ipsum dolor sit amet (36pts)2. Consectetur adipisicing elit (30pts)3. ed do eiusmod tempor incididunt utlabore et dolore magna aliqua (32pts)4. Enim ad minim veniam, quis nostrudexercitation (24pts)5. llamco laboris nisi ut aliquip ex eacommodo consequat. (24pts)6. Duis aute irure dolor in reprehenderit involuptate velit esse cillum dolore eu fugiatnulla pariatur. (32pts) Velocity = 45 sp / itr6. Excepteur sint occaecat cupidatat nonproident, sunt in culpa qui officia deseruntmollit anim id est laborum. (22pts) 200 / 45 ≈ 5 Iterations Remaining 48pts 35pts 52pts ship ship ship plan plan plan Iterations = Story Points / Velocity
    • 8. Cards facilitate [Courtesy: http://www.infoq.com/articles/agile-kanban-boards]
    • 9. Shared spaces [Courtesy: http://www.infoq.com/articles/agile-kanban-boards]
    • 10. Running planning meeting
    • 11. 1. Pre-meetingEngage stakeholders and prepare • collect cards for new stories • reprioritize stories with product owner • update velocity and charts • solicit feedback from stakeholders • hold retrospective; add cards
    • 12. 2. Hold MeetingEstimate and pick stories for nextiteration (< 2 hrs) • Planning poker — involve team, not “experts” — on new stories • Pick stories for next iteration • Clarify stories with Product Owner • Don’t assign stories or re-estimatePlanning poker: http://planningpoker.com/detail.html
    • 13. Post-meeting, daily routine• work stories in priority order• clarify story with product owner, seek feedback• document behavior with tests• deploy/ship working software• leave no in-progress work
    • 14. Thanks! Soren Harnerhttp://permaling.com

    ×