Agile scheduling

495 views

Published on

How to Schedule your project based on Agile
1- Type of project and how to select deadline
2- How to select Iteration Length
3- How to build your Iterations

Published in: Technology, Economy & Finance
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
495
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
9
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Agile scheduling

  1. 1. Agile Scheduling 1 2013 – Jun By: Mohamed Saad
  2. 2.  Release Planning Essentials  Iteration Planning  Selection an Iteration Length 2
  3. 3.  The Release Plan 3
  4. 4.  The Release Plan  Determine The Condition of Satisfaction › Feature-driven project: Must include some features in release › Date-driven project: Must be released by date  Estimate the User Stories › Discussed in Estimating Size (Story Points or Ideal Days) 4
  5. 5.  Select an Iteration Length  Estimate Velocity  Prioritizing User Stories › Discussed in Planning for value considering Financial, Cost, Knowledge and Risk  Select Stories and Release Date › Feature-driven VS Date-driven › Determine the release planning task vs. determining each iteration stories 5
  6. 6.  Updating the Release Plan › Is done at end of each Iteration 6
  7. 7.  Iteration Planning › Tasks are not allocated During Iteration Planning › How Iteration Planning Differs from Release Planning 7
  8. 8.  Velocity-Driven Iteration Planning › Adjust Priorities › Determine target Velocity › Identify Iteration Goal › Select User Stories 8
  9. 9.  Velocity-Driven Iteration Planning (Cont.) › Split User Stories into Tasks  Include only work that values to this project: no email responding or discussions should be included  Include Unit Testing: as separate task or include it in task estimate  Include Meetings in tasks  Include bugs fixing in tasks estimate: if it’s not detected within the iteration should be included in next iterations  Handling Dependences: try to use natural order if possible  Handle work that is difficult to split: split in to two tasks  Determine effect and estimate.  Make do the work 9
  10. 10.  Velocity-Driven Iteration Planning (Cont.) › Estimate Tasks  Estimates Is in ideal hours  Involve some design details  Chose right size: try to split tasks to fit in to one day 10
  11. 11.  Commitment-Driven Iteration Planning 11
  12. 12.  Commitment-Driven Iteration Planning (Cont.) › Ask for a Team Commitment  Summing the Estimates  Include Maintenance work from previous projects time 12
  13. 13.  Range of Iteration Length › 2-weeks to 4-weeks (1-Month)  Factors in Selecting an Iteration Length › The Overall length of the Release: should have at least 4-5 Iterations › The Amount of Uncertainty: short iterations decreases uncertainty › The Ease of Getting Feedback: if it’s hard to get feedback will use long iterations 13
  14. 14.  Factors in Selecting an Iteration Length (cont.) › How Long Priorities Can Remain Unchanged: it took around 1.5 iteration to see new changes › Willingness to Go without Outside Feedback › The Overhead of Iteration: time wasted by meeting for (review iteration and start new iteration) › How Soon a feeling of Urgency is Established: as long as the end date of an iteration is far we don’t feel pressure 14
  15. 15.  Agile Estimating and Planning by Mike Cohn. 15

×