• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
How to Plan Agile Iterations
 

How to Plan Agile Iterations

on

  • 1,880 views

 

Statistics

Views

Total Views
1,880
Views on SlideShare
1,477
Embed Views
403

Actions

Likes
0
Downloads
6
Comments
0

1 Embed 403

http://permaling.tumblr.com 403

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • \n
  • \n
  • - Relative estimation is easier\n- It is easier in groups\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

How to Plan Agile Iterations How to Plan Agile Iterations Presentation Transcript

  • Planning MeetingA hands-on guide to running an Agile Planning Meeting
  • 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.)
  • 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
  • Relative Estimation Breed Height (cm) Relative Terrier Bulldog Labrador Saint Bernard Poodle Great DaneGerman Shephard
  • Fractal Rhythm Release (Epics & Themes) Iteration (Stories) Day (Tasks)We are here
  • 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
  • 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
  • Cards facilitate [Courtesy: http://www.infoq.com/articles/agile-kanban-boards]
  • Shared spaces [Courtesy: http://www.infoq.com/articles/agile-kanban-boards]
  • Running planning meeting
  • 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
  • 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
  • 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
  • Thanks! Soren Harnerhttp://permaling.com