agile scheduling

15
Agile Scheduling 2013 – Jun By: Mohamed Saad 1

Upload: inovaeg

Post on 28-Oct-2014

421 views

Category:

Technology


0 download

DESCRIPTION

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

TRANSCRIPT

Page 1: Agile scheduling

1

Agile Scheduling2013 – Jun

By: Mohamed Saad

Page 2: Agile scheduling

2

Agenda

Release Planning Essentials Iteration Planning Selection an Iteration Length

Page 3: Agile scheduling

3

Release Planning Essentials

The Release Plan

Page 4: Agile scheduling

4

Release Planning Essentials

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)

Page 5: Agile scheduling

5

Release Planning Essentials

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

Page 6: Agile scheduling

6

Release Planning Essentials

Updating the Release Plan› Is done at end of each Iteration

Page 7: Agile scheduling

7

Iteration Planning

Iteration Planning› Tasks are not allocated During Iteration

Planning› How Iteration Planning Differs from Release

Planning

Page 8: Agile scheduling

8

Iteration Planning

Velocity-Driven Iteration Planning› Adjust Priorities› Determine target Velocity› Identify Iteration Goal› Select User Stories

Page 9: Agile scheduling

9

Iteration Planning

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

Page 10: Agile scheduling

10

Iteration Planning

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

Page 11: Agile scheduling

11

Iteration Planning

Commitment-Driven Iteration Planning

Page 12: Agile scheduling

12

Iteration Planning

Commitment-Driven Iteration Planning (Cont.)› Ask for a Team Commitment

Summing the Estimates Include Maintenance work from previous

projects time

Page 13: Agile scheduling

13

Selecting an Iteration Length

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

Page 14: Agile scheduling

14

Selecting an Iteration Length

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

Page 15: Agile scheduling

15

References

Agile Estimating and Planning by Mike Cohn.