Nuts and Bolts of Scrum Template (extended)

Nuts & Bolts of
Visual Studio Scrum v1.0 Template
Dog Food Conference III
Alexei V. Govorine
1
© 2010 Cardinal Solutions Group

Visual Studio 2010 ALM - Scrum
Backlog
• Why Agile?
• Scrum Overview
• Visual Studio Scrum v1.0 Template
• Q&A
2
Some of the slides were contributed by:
Richard Hundhausen, Aaron Bjork, Martin Hinshelwood, Paul Neumeyer, Ken Schwaber, Randy Pagels, Jeff Hunsaker, & others

About Alexei
ALM Consultant at Cardinal Solutions Group
http://www.CardinalSolutions.com
Microsoft Visual Studio ALM MVP
http://mvp.support.microsoft.com/profile/Alexei
Professional Scrum Developer Trainer
http://courses.scrum.org/about/alexei-govorine
Co-founder of COALMG
http://www.coalmg.org
3govorin.blogspot.com www.twitter.com/Leshka

• Over 200 professionals with
offices in 3 cities
• A Microsoft “Managed
Partner” since 2008; Gold
Certified since 1999
• VSTS Inner Circle Partner
• Help customers drive
business value from Microsoft
technologies
• Visual Studio ALM/TFS
• SharePoint 2010, MOSS 2007
• Microsoft Business
Intelligence (MSBI)
• Microsoft Online Services
• .NET Architecture/
Development
• Client Training
Who is Cardinal?
Fast Facts Our Focus
Company Overview
4

WHAT IS AGILE?
TIMEBOX ACTIVITY – 2 MIN
5
Please write down a few words or a
sentence on what Agile means to you.

* AGILE
Agile software development focuses on regularly delivering
business value. It embraces change while leveraging
feedback to produce high quality, desired results.
6
* Different for every company
Agile is a Movement
Represented by Methodologies &
Frameworks
Comprised of a set of
Development & Engineering
Practices

Why Agile? (Project Challenges)
7

The Forrester Wave™: Agile Development Management Tools, Q2 2010, Forrester Research, Inc., May 5, 2010.

Indeed.com™: Trend search on keywords: agile, scrum, lean, kanban, xp, iterative, cmmi, waterfall, rup. May 25, 2010.

Backlog
Why Agile?
• Scrum Overview
• Q&A
11

Scrum Overview
12
Scrum in the sports of “rugby union” and “rugby league”, is a way of restarting the game, either
after an accidental infringement or (in rugby league only) when the ball has gone out of play.

“Scrum is a framework for developing
complex products and systems. It is
grounded in empirical process control theory.
Scrum employs an iterative, incremental
approach to optimize predictability and
control risk.”
-Ken Schwaber
From the originator of Scrum
Used now by:
Microsoft, Sun, Sony Ericcson, Philips, Google, BBC, IBM, Motorola, Hewlett Packard, Oracle,
JPMorgan, CapitalOne, Alliance, Electronic Arts, DoubleClick, SalesForce.com, Nokia, Siemens,
Intel, Yahoo, Xerox, Cisco, SSW… and lots more.

• Scrum has become mainstream in the last half decade or so
• 50% of Agile software practitioners most closely follow
Scrum
• A further 24% follow some variation of Scrum (variations are
often referred to as “ScrumBut”)
Trends in the adoption of Scrum

• The project is split into Sprints
• At the end of each Sprint a working
iteration of the product is available
• Each Sprint includes parts of
planning, work and review
• 3 Roles, 6 Timeboxes and 4
Artefacts
Scrum on Slide
http://www.scrum.org/scrumguides

Roles in Scrum
Product Owner ScrumMaster Team
Stakeholders = everyone else
ScrumTeam

• Who is responsible for maximizing the value of
the work that the Scrum Team does
• Controls “What” is in the product
– Sets Vision for the product
– Sets Priorities
– Deals with Stakeholders
– Deals with clarification for the Team
Key Role – Product Owner

• Who is responsible for ensuring the process is
understood and followed
• The “Process”
– Host meetings
– Manage process
– Remove impediments
Key Role - ScrumMaster

• Which does the work
• Converts the “What” into “How”
– Cross-functional
– Engineering Practices
– Each iteration commit on functionality to build
– Plan the tasks
– Self organize to build the iteration
– The Product Owner and ScrumMaster cannot
assign a task to the Team or a particular Team
member
Key Role – Team

• The Sprint is timeboxed
• Meetings are timeboxed
• “Timeboxed” means the time runs out
– You can’t add time or extend
– You complete what you can
– You do better next time
Scrum uses Timeboxes

• Release Planning 8 hours
• Sprint 4 Weeks
• Sprint Planning 8 hours
• Daily Scrum 15 minutes
• Sprint Review 4 hours
• Sprint Retrospective 4 hours
Timeboxes of Scrum

• Sprint = Iteration
• The Sprint can be 1, 2, 3 or 4 weeks
– Beyond 4 weeks is a “smell”
– Beyond 6 weeks is a “stench”
• Keep the Sprint length consistent
• Project Risks has influence on Sprint length
• My experience: 2 weeks
Sprint Timeboxes of Scrum

What that looks like on a Calendar?
4h 2h 2h
Sprint of 2 weeks
doing the work +
Daily Scrums
Sprint Planning
Sprint Review
Sprint Retrospective

• Is a list of features for the Product
• Normally a mixture of User Stories & Bugs
• Each item is given
– An acceptance criteria
– An estimate by the Team
– A business value by the Product Owner
• Some User Stories may be large and need future
decomposition into smaller user stories
Key Artefact - Product Backlog

• A list of the Product Backlog Items and Sprint
tasks for each
– Each task will have an estimate of hours
remaining to complete
– The aim is to meet the Team’s “done” criteria
– Decomposition of Product Backlog into Tasks
for the sprint
Key Artefact – Sprint Backlog

Key Artefact - Release Burndown Chart
• A Release/Product Burndown measures work remaining
across the time of a release plan

Key Artefact - Sprint Burndown Chart
• A Sprint Burndown measures work remaining across the
time of a Sprint

Backlog
Why Agile?
Scrum Overview
• Q&A
28

VISUAL STUDIO SCRUM V1.0
TFS PROCESS TEMPLATE
29

Visual Studio 2010

Microsoft Visual Studio Scrum 1.0
• A process template introduced shortly after
Visual Studio 2010 launched
– This demonstrates how popular Scrum is and
also Microsoft’s commitment to supporting Scrum
• Maps directly to the Scrum concepts
– Sprint vs. Iteration, PBI vs. User Story,
Impediment vs. Issue
• Available as free download from Microsoft:
– http://shrinkster.com/1exg

Visual Studio Scrum 1.0 Artifacts
Work Item Types Team Queries Reports
Sprint All Sprints Release Burndown
Product Backlog Item Product Backlog Sprint Burndown
Task Blocked Tasks Velocity
Impediment Open Impediments Build Success Over Time *
Bug Sprint Backlog Build Summary *
Test Case * Test Cases Test Case Readiness *
Shared Steps * Unfinished Work Test Plan Progress *
Work in Progress
* Nearly identical to that found in the MSF for Agile Software Development 5.0 template

Areas and Iterations
• Areas represent the components or related
features of the product (the where)
• Iterations represent the releases and Sprints
(the when)
• By default, only Project
Administrators may make
changes to areas and iterations
• Tip: avoid making your area
hierarchy too complex

Sprint Work Item Type
• Provides a way for your team to capture
additional metadata about the Sprint
– Start date, finish date, goal, and retrospective

Product Backlog Item Work Item Type
• Represents a product requirement

PBI State

Task Work Item Type
• Represents the detailed work the team must do
in order to achieve their Sprint Goal

Task State

Impediment Work Item Type
• Represents an issue or problem that prevents
the team from completing its tasks efficiently

Impediment State

Test Case Work Item Type
• Used to define both manual and automated tests

Test Case State

Bug Work Item Type
• Represents a defect in the product
• PBI

Bug State

Queries
• Product queries
– All Sprints
– Product Backlog
• Current Sprint queries
– Blocked Tasks
– Open Impediments
– Sprint Backlog
– Test Cases
– Unfinished Work
– Work in Progress

Reports
• Scrum reports
– Release Burndown
– Sprint Burndown
– Velocity
• Engineering reports
– Build Summary
– Builds Success Over Time
– Test Case Readiness
– Test Plan Progress

Visual Studio Scrum Activities
• Scrum team projects have many standard and
repetitive activities
– Setting up a new Team Project Collection
– Setting up a new Team Project
– Setting up Sprints
– Building Product Backlog
– Managing Acceptance Criterias
– Planning a Sprint
– Daily activities
– Tracking a Sprint Progress
– Completing a Sprint

Mapping Scrum to Visual Studio 2010
Scrum Concept Visual Studio Scrum 1.0
Team Team Foundation Server security groups
Definition of Done Wiki entry or document on the portal
Product Team Project
Product Backlog Product Backlog team query
Product Backlog Item Product Backlog Item work item
Acceptance Criteria
Acceptance Criteria field and (optionally) associated Test Case work
items
Release Iteration Path (high level)
Release Goal Wiki entry or document on the portal
Release Capacity Wiki entry or document on the portal
Sprint Iteration Path (low level) and associated Sprint work item
Sprint Dates Start Date and Finish Date fields
Sprint Goal Sprint Goal field
Sprint Capacity Wiki entry or document on the portal
Sprint Backlog Sprint Backlog team query
Task Task work item
Burndown and Velocity Release Burndown, Sprint Burndown, and Velocity reports
Impediment Impediment work item
Bug Bug work item
Retrospective Retrospective field in the Sprint work item
* without customization
*

This demonstration will cover:
DEMO
• *Install and Configure
• *Template Customization
• *Areas and Iterations
• Managing Sprint work items
• Creating a Product Backlog Item
• Creating and linking a Task
• Creating and linking a Test Case
• Creating and linking a Bug
• Managing Impediments
Visual Studio Scrum 1.0

50

51

52

Burndown
Why Agile?
Scrum Overview
Visual Studio Scrum v1.0 Template
• Q&A
53

Retrospective … (Q&A)
Resources
• Scrum.org
(http://www.scrum.org)
• Microsoft
(http://msdn.microsoft.com/en-us/vstudio/aa718795.aspx)
• PSD Class
(http://courses.scrum.org/about/alexei-govorine)
• About Cardinal
(http://www.cardinalsolutions.com/training/)
54

Thank You
Contact Alexei:
• @Leshka
• AGovorine@CardinalSolutions.com
• http://govorin.blogspot.com
55

Nuts and Bolts of Scrum Template (extended)

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (20)

Semelhante a Nuts and Bolts of Scrum Template (extended)

Semelhante a Nuts and Bolts of Scrum Template (extended) (20)

Nuts and Bolts of Scrum Template (extended)

Notas do Editor