agenda −scrum with tfs 2010 using msf for agile 5.0 −planning the project −how do you plan the...

68
SCRUM with Team Foundation Server 2010

Upload: bailey-popish

Post on 15-Dec-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

SCRUM with Team Foundation Server 2010

Agenda

− Scrum with TFS 2010 using MSF for Agile 5.0− Planning the Project

− How do you plan the project?− Project planning in TFS 2010

− Planning a Sprint− What is sprint planning?− Sprint planning in TFS 2010

− Running a Sprint− How do you run a sprint?− Running a sprint in TFS 2010

How do you Plan the Project?

− Product Backlog− Evolving backlog of user stories

(requirements)− Describes what users need and value− Owned by the Product Owner− Prioritized by business value− Each story is written from the user’s

perspective

Planning the Project

“As a new customer I want to register online

so I can use the services offered”

Stories are listed on the backlog in priority order

New stories are added to the product

backlog

The team estimates each story using story

points

5

8

3

5

8

1

Pri

ori

ty

Product Backlog

User Stories

Product Backlog

User Stories

Planning the Project

3

3

3

4

4

4

Sprint 3

The product owner re-prioritizes the backlog

Sprint 4

Stories are planned for completion in upcoming sprints

Pri

ori

ty

Product Backlog in TFS 2010

− Product Backlog query− Creating new user

stories− Prioritizing− Estimating story

points− Add user stories to

upcoming sprints

Product Backlog

Product backlog query in Team

Explorer

Product Backlog

New stories created by the Product Owner

Product Backlog

The new story provides a guide to ensure the

story is written from the customer’s perspective

Product BacklogEach story is ranked

by priority and assigned a story

point value

Product Backlog

Product Backlog workbook for

planning future sprints

Product Backlog Workbook

Stories that are too large are left on the

backlogEach story is placed in an

upcoming sprint

Product Backlog Workbook

Each sprint is added to Iteration

Planning worksheet…

… with start/end dates and the size of

the team

The product owner can use the velocity of the team to help plan for upcoming

sprints

Agenda

− Scrum with TFS 2010 using MSF for Agile 5.0− Planning the Project

− How do you plan the project?− Project planning in TFS 2010

− Planning a Sprint− What is sprint planning?− Sprint planning in TFS 2010

− Running a Sprint− How do you run a sprint?− Running a sprint in TFS 2010

What is Sprint Planning?

− The product owner and the team add user stories to the sprint

− Each story is decomposed into tasks− The team makes a commitment to

each user story

Product Backlog

User Stories

Planning a Sprint

User Stories Tasks (hours)

Iteration Backlog

Commi

t!

Commi

t!3

3

3

Can’t Commi

t!

The team breaks down

each story into tasks

The team thinks this story

is more work than they can commit to…

Based on estimates the team commits to each story

During the sprint planning meeting, the product owner and the team add User Stories

to the sprint

Product Backlog

User Stories User Stories Tasks (hours)

Iteration Backlog

Planning a Sprint

User Stories Tasks (hours)

3

3

3

3

Commi

t!

The larger story is removed from the

sprint and the team considers a smaller story on

the backlog

? Commi

t!

Commi

t!

The team can commit to this smaller story

The sprint is now planned and the team is ready to get

started!

Sprint Planning

− Break down user stories into tasks

− Load balance− Commit− Track interruptions− Track progress

Iteration Backlog Workbook

Each sprint has an Excel workbook to assist the team in

making a commitment

Iteration Backlog Workbook

Dates for the sprint are added…

Iteration Backlog Workbook

... and any planned

interruptions

Iteration Backlog Workbook

The team breaks down the first user story into

tasks

Iteration Backlog Workbook

Each task is estimated in

hours

Iteration Backlog Workbook

The team checks their capacity for the sprint

Iteration Backlog Workbook

The next story is broken down…

Iteration Backlog Workbook

Iteration Backlog Workbook

… but one team member has too much

work

The team has capacity…

Iteration Backlog Workbook

Iteration Backlog Workbook

The final story is broken down

Iteration Backlog Workbook

Based on capacity and estimates, the

team is overcommitted

Iteration Backlog Workbook

The final story is removed…

Iteration Backlog Workbook

And replaced with a smaller story

from the product backlog

Iteration Backlog Workbook

… but one team member still has too much work

The team is comfortable

committing to this story…

Iteration Backlog Workbook

Tasks are reassigned

Iteration Backlog Workbook

Tasks are reassigned

Iteration Backlog Workbook

Work is now load balanced

across the team

Iteration Backlog Workbook

The final step is to publish the data back to

TFSSprint planning

is complete!

Agenda

− Scrum with TFS 2010 using MSF for Agile 5.0− Planning the Project

− How do you plan the project?− Project planning in TFS 2010

− Planning a Sprint− What is sprint planning?− Sprint planning in TFS 2010

− Running a Sprint− How do you run a sprint?− Running a sprint in TFS 2010

How do you Run a Sprint?

− Track Progress− Daily Sprint Meeting− What work has been completed− What work remains

− Deliver a “potentially shippable” increment

− Demo the value delivered− Retrospective

Product Backlog

User Stories User Stories Tasks (hours)

Iteration Backlog

Running a Sprint

The team starts work on the

tasks…

Running a Sprint

2/1 2/4 2/72/1

02/1

32/1

62/1

92/2

22/2

52/2

8

0

20

40

60

80

100

Remaining CompletedCompleted work is reported daily

Product Backlog

User Stories User Stories Tasks (hours)

Iteration Backlog

Running a Sprint

2/1 2/4 2/72/1

02/1

32/1

62/1

92/2

22/2

52/2

8

0

20

40

60

80

100

Remaining Completed

Product Backlog

User Stories User Stories Tasks (hours)

Iteration Backlog

2/1 2/4 2/72/1

02/1

32/1

62/1

92/2

22/2

52/2

8

0

20

40

60

80

100

Remaining Completed

Running a Sprint

Each User Story has

been implemented

All work for the sprint is “done-

done”

Product Backlog

User Stories User Stories Tasks (hours)

Iteration Backlog

Product Backlog

User Stories User Stories Tasks (hours)

Iteration Backlog

Running a Sprint

The team holds a demo to show the value they have

delivered

And the team has developed a “potentially shippable” increment

Running a Sprint

The latest increment is shipped to customers

Product Backlog

User Stories User Stories Tasks (hours)

Iteration Backlog

Running a Sprint

The team holds a retrospective…

Stories delivered in the last sprint are

closed

Stories and tasks are cleared from the

backlog – the team delivered on its

commitment

Product Backlog

User Stories User Stories Tasks (hours)

Iteration Backlog

What worked? What didn’t work? What can the team

do to improve?

Running a Sprint

New Stories are added to the

Product Backlog

Product Backlog

User Stories User Stories Tasks (hours)

Iteration Backlog

Running a Sprint

The backlog is prioritized and

ready for the team to plan the next

sprint

Product Backlog

User Stories User Stories Tasks (hours)

Iteration Backlog

Running a Sprint

− Record completed work daily

− Track progress with reports and dashboards

− Retrospectives

Updating Tasks

Multiple interfaces for updating work

items

Updating Tasks

Team Explorer

Updating Tasks

Iteration Backlog workbook

Updating Tasks

Team Project portal

Updating Tasks

Updating Tasks

Updating Tasks

Team Web Access

Tracking Progress

Burndown chart tracks remaining and completed

work

Tracking Progress

Tracking Progress

Tracking ProgressDetailed sprint

progress is tracked on the project portal

The burndown shows the team on track…

And almost half of the tasks remain

openBut the team hasn’t closed any

of the three stories…

Tracking Progress

The Scrummaster opens an issue to track the problem

the portal has identified

Tracking Progress

The issue is opened and tracked in TFS

Tracking Progress

Test are passing…

But bugs are climbing steadily

The portal brings data together so it can be analyzed to ensure success on a

sprint

Tracking ProgressRich set of reports

track progress

Retrospective Capture retrospectives using the Team wiki on the

Project Portal

Sample documents are provided as a

guide

Agenda

− Scrum with TFS 2010 using MSF for Agile 5.0− Planning the Project

− How do you plan the project?− Project planning in TFS 2010

− Planning a Sprint− What is sprint planning?− Sprint planning in TFS 2010

− Running a Sprint− How do you run a sprint?− Running a sprint in TFS 2010

TFS Resources

1. http://blogs.msdn.com/aaronbjork2. http://blogs.msdn.com/bharry3. http://social.msdn.microsoft.com/Foru

ms/en-US/category/vsts4. http://msdn.microsoft.com/en-us/team

system/default.aspx

Microsoft Confidential68

Thank You

My Blog http://krishnakamisetty.blogspot.com/