ug pres - feb 2010 - succeeding w agile and tfs 2010

8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010

1/107


2/107

2


3/107

3


4/107

4


5/107

5


6/107

6


7/107

7


8/107

8


9/107

9


10/107

10


11/107

11


12/107

12


13/107

13


14/107

14


15/107

15


16/107

16

Variance

ofEstimates

Time

Delivery Date


17/107

17


18/107

18

Category Lowest ReportedImprovement

MedianImprovement

Highest ReportedImprovement

Productivity 14% 88% 384%

Cost 10% 26% 70%


19/107

19

Time

V

alue

Expected Target Value

Release 1.0

Release 1.0


20/107

20


21/107

21


22/107

22
http://upload.wikimedia.org/wikipedia/commons/d/d1/ScrumLargeLabelled.png


23/107

23


24/107

24


25/107

25


26/107

26


27/107

27


28/107

28


29/107

29


30/107

30


31/107


32/107


33/107

As a new customer I want

to register online so I canuse the services offered

Stories are listed on thebacklog in priority order

New stories are added

to the product backlog

The team estimates eachstory using story points

5

8

3

5

8

1

Priority

Product BacklogUser Stories


34/107

Product BacklogUser Stories

3

3

3

Priority

4

4

4

Sprint 3

The product owner re-prioritizes the backlog

Sprint 4

Stories are planned forcompletion in

upcoming sprints


35/107


36/107


37/107

37


38/107

Product backlogquery in Team

Explorer


39/107

New stories createdby the Product Owner


40/107

The new story provides aguide to ensure the story is

written from the customersperspective


41/107

Each story is ranked bypriority and assigned a

story point value (orideal days)


42/107

Product Backlogworkbook for planning

future sprints


43/107

Stories that are too largeare left on the backlog

Each story isplaced in an

upcoming sprint


44/107

Each sprint is addedto Iteration Planning

worksheet

with start/end dates

and the size of the team

The product owner canvisualize the number ofstory points planned for

upcoming sprints


45/107


46/107


47/107


48/107


49/107


50/107


51/107

51


52/107

Each sprint has anExcel workbook toassist the team in

making a commitment


53/107

Dates for the sprintare added


54/107

... and any planned

interruptions


55/107

The team breaksdown the first user

story into tasks


56/107

Each task is

estimated in hours


57/107

The team checkstheir capacity for

the sprint


58/107

The next story isbroken down


59/107


60/107

but one team

member has toomuch work

The team hascapacity


61/107


62/107

The final story is

broken down


63/107

Based on capacity andestimates, the team is

overcommitted


64/107

The final story is

removed


65/107

And replaced with asmaller story fromthe product backlog


66/107

but one teammember still has too

much workThe team is comfortablecommitting to this story


67/107


68/107

Tasks arereassigned


69/107

Work is now loadbalanced across

the team


70/107

The final step isto publish the

data back to TFS

Sprint planning is

complete!


71/107


72/107


73/107


74/107

0

20

40

60

80

100

2/1 2/8 2/15 2/22

Remaining CompletedCompleted work is

reported daily

Product Backlog

User Stories User Stories Tasks (hours)

Iteration Backlog


75/107

0

20

40

60

80

100

2/1 2/8 2/15 2/22

Remaining Completed

Product Backlog


Iteration Backlog


76/107

Product Backlog


Iteration Backlog

0

20

40

60

80

100

2/1 2/8 2/15 2/22

Remaining Completed

Each UserStory has beenimplemented

All work for the sprintis done-done


77/107

The team holds a demoto show the value they

have delivered

and the team has

developed a

potentially shippableincrement

Product Backlog


Iteration Backlog


78/107

The latest

increment isshipped tocustomers

Product Backlog


Iteration Backlog


79/107

What worked?What didnt work?

What can the team doto improve?

The team holds a

retrospective

Stories delivered in the

last sprint are closed

Stories and tasks arecleared from the backlog

the team delivered onits commitment

Product Backlog


Iteration Backlog


80/107

New Stories areadded to the

Product Backlog

Product Backlog


Iteration Backlog


81/107

The backlog is

prioritized and readyfor the team to plan

the next sprint

Product Backlog


Iteration Backlog


82/107


83/107


84/107

84


85/107

Multiple interfaces forupdating work items


86/107

Team Explorer


87/107

Iteration Backlogworkbook


88/107


89/107


90/107


91/107

Team Web Access


92/107

Burndown charttracks remaining and

completed work


93/107


94/107


95/107

Detailed sprint progress

is tracked on the projectportal

The burndown

shows the teamon track

And almost half of thetasks remain openBut the team hasnt

closed any of thethree stories


96/107

The Scrummasteropens an issue to

track the problem theportal has identified


97/107

The issue is openedand tracked in TFS


98/107

Test arepassing

But bugs areclimbing steadily

The portal brings datatogether so it can be

analyzed to ensuresuccess on a sprint


99/107

Rich set of reportstrack progress

Capture retrospectives


100/107

Capture retrospectivesusing the Team wiki on

the Project Portal

Sample documents areprovided as a guide


101/107


102/107

102


103/107


104/107

104


105/107

105


106/107


107/107

http://blogs.msdn.com/bharry/archive/2009/05/19/tfs-2010-project-management.aspx

ug pres - feb 2010 - succeeding w agile and tfs 2010

Documents