Post on 06-Apr-2018
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
1/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
2/107
2
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
3/107
3
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
4/107
4
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
5/107
5
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
6/107
6
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
7/107
7
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
8/107
8
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
9/107
9
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
10/107
10
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
11/107
11
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
12/107
12
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
13/107
13
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
14/107
14
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
15/107
15
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
16/107
16
Variance
ofEstimates
Time
Delivery Date
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
17/107
17
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
18/107
18
Category Lowest ReportedImprovement
MedianImprovement
Highest ReportedImprovement
Productivity 14% 88% 384%
Cost 10% 26% 70%
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
19/107
19
Time
V
alue
Expected Target Value
Release 1.0
Release 1.0
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
20/107
20
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
21/107
21
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
22/107
22
http://upload.wikimedia.org/wikipedia/commons/d/d1/ScrumLargeLabelled.png8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
23/107
23
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
24/107
24
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
25/107
25
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
26/107
26
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
27/107
27
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
28/107
28
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
29/107
29
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
30/107
30
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
31/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
32/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
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
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
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
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
35/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
36/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
37/107
37
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
38/107
Product backlogquery in Team
Explorer
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
39/107
New stories createdby the Product Owner
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
40/107
The new story provides aguide to ensure the story is
written from the customersperspective
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
41/107
Each story is ranked bypriority and assigned a
story point value (orideal days)
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
42/107
Product Backlogworkbook for planning
future sprints
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
43/107
Stories that are too largeare left on the backlog
Each story isplaced in an
upcoming sprint
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
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
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
45/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
46/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
47/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
48/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
49/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
50/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
51/107
51
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
52/107
Each sprint has anExcel workbook toassist the team in
making a commitment
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
53/107
Dates for the sprintare added
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
54/107
... and any planned
interruptions
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
55/107
The team breaksdown the first user
story into tasks
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
56/107
Each task is
estimated in hours
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
57/107
The team checkstheir capacity for
the sprint
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
58/107
The next story isbroken down
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
59/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
60/107
but one team
member has toomuch work
The team hascapacity
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
61/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
62/107
The final story is
broken down
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
63/107
Based on capacity andestimates, the team is
overcommitted
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
64/107
The final story is
removed
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
65/107
And replaced with asmaller story fromthe product backlog
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
66/107
but one teammember still has too
much workThe team is comfortablecommitting to this story
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
67/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
68/107
Tasks arereassigned
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
69/107
Work is now loadbalanced across
the team
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
70/107
The final step isto publish the
data back to TFS
Sprint planning is
complete!
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
71/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
72/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
73/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
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
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
75/107
0
20
40
60
80
100
2/1 2/8 2/15 2/22
Remaining Completed
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
76/107
Product Backlog
User Stories User Stories Tasks (hours)
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
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
77/107
The team holds a demoto show the value they
have delivered
and the team has
developed a
potentially shippableincrement
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
78/107
The latest
increment isshipped tocustomers
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
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
User Stories User Stories Tasks (hours)
Iteration Backlog
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
80/107
New Stories areadded to the
Product Backlog
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
81/107
The backlog is
prioritized and readyfor the team to plan
the next sprint
Product Backlog
User Stories User Stories Tasks (hours)
Iteration Backlog
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
82/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
83/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
84/107
84
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
85/107
Multiple interfaces forupdating work items
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
86/107
Team Explorer
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
87/107
Iteration Backlogworkbook
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
88/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
89/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
90/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
91/107
Team Web Access
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
92/107
Burndown charttracks remaining and
completed work
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
93/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
94/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
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
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
96/107
The Scrummasteropens an issue to
track the problem theportal has identified
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
97/107
The issue is openedand tracked in TFS
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
98/107
Test arepassing
But bugs areclimbing steadily
The portal brings datatogether so it can be
analyzed to ensuresuccess on a sprint
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
99/107
Rich set of reportstrack progress
Capture retrospectives
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
100/107
Capture retrospectivesusing the Team wiki on
the Project Portal
Sample documents areprovided as a guide
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
101/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
102/107
102
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
103/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
104/107
104
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
105/107
105
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
106/107
8/3/2019 UG Pres - Feb 2010 - Succeeding w Agile and TFS 2010
107/107
http://blogs.msdn.com/bharry/archive/2009/05/19/tfs-2010-project-management.aspx