Managing Projects Using Microsoft Visual Studio Scrum 1.0 ...accentient.com/files/VisualStudioScrumPart2.pdfRichard Hundhausen •President of Accentient •Author of software development

Managing Projects

Using Microsoft

Visual Studio Scrum 1.0

Part 2

Accentient

• A leader in Visual Studio ALM knowledge

• Has helped hundreds of clients understand,

implement and leverage Visual Studio ALM tools

• Has a close working relationship with Microsoft

• Consultants are Microsoft MVPs, Microsoft Regional

Directors, Certified Professional Scrum Developers,

and Microsoft Certified Trainers

www.accentient.com

Richard Hundhausen

• President of Accentient

• Author of software development books

• Microsoft Regional Director

• Microsoft MVP (Visual Studio ALM)

• Professional Scrum Developer

• [email protected]

Agenda

• Visual Studio Scrum 1.0 (Review)

• Activities

– New Team Project Collection (Review)

– New Team Project

– New Sprint

– Daily

– Completing a Sprint

• Demos

• Questions

Review: 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

New Team Project Collection Activities

• Create the new Team Project Collection

• Configure SharePoint, reporting, and Lab

Management settings

• Configure Team Foundation Build

• Configure security permissions

• Upload Visual Studio Scrum process template

• These were completed in Part 1 of the webcast

New Team Project Activities

• Plan and create the team project

• Configure security, SharePoint, process guidance, and version

control settings

• Configure the work item area and iteration hierarchy

• Edit the applicable Sprint work items

• Migrate existing work items to establish the Product Backlog

• Verify the Product Backlog by executing the query

• Create other queries as needed by the team (i.e. “All Bugs”)

• Establish Definition of Done

New Sprint Activities

• Ensure that the release and Sprint nodes exist

• Modify the Current Sprint queries

• Verify the Product Backlog by executing the query

• Ensure there is a corresponding Sprint work item

• Review the Release Burndown and Velocity reports

• Edit the applicable PBI work items, setting their Iteration to

the current Sprint and state to Committed

• Create and link initial task work items to the PBI and Bug

work items you committed to delivering

• Verify the Sprint Backlog by executing the query

Daily Activities

• Create and link task work items as needed

• Take on new tasks from the Sprint Backlog by assigning the

task to yourself and setting state to In Progress

• Associate a single task with any code check-ins

• Update remaining work estimates on in-progress tasks

• Complete your work according to acceptance criteria and your

team’s definition of done

• When you complete a task, set the state to Done and

Remaining Work to 0

• Update the Product Backlog by creating and editing PBI and

Bug work items as needed (grooming)

• Create and manage impediment work items as needed

• Review the Sprint Burndown report to monitor progress

End of Sprint Activities

• Label code and other artifacts in version control

• Set the State of the PBI and/or Bug work items to Done when

the Product Owner accepts it

• Set the State of the PBI/Bug and linked work items

appropriately for unfinished/unaccepted work

• Update the Product Backlog by creating and editing PBI and

Bug work items as needed

• Capture the Sprint retrospective feedback on the Sprint work

item

• Branch as needed (i.e. to support hotfixing)

• Team Web Access add-on that provides a task board and a

planning board

• Index card metaphor with drag-and-drop functionality

• Built-in support for Microsoft Visual Studio Scrum 1.0 Process

Template out of the box

• Urban Turtle will make sense and correspond to everything

you’ve learned in a book on Scrum (or a class on Scrum)

http://UrbanTurtle.com

Use discount code ACCENTIENT for 15% off

Urban Turtle Replacement for Excel-based

planning workbooks

Professional Scrum Developer Program

• An innovate program for

developers from Microsoft

and the founders of Scrum

• Learn how to use modern engineering practices to

develop an increment of complete, potentially

shippable functionality using Visual Studio 2010,

ALM, and the Scrum framework

Training, Assessment, Certification

Bookmarks

• Microsoft Visual Studio Scrum 1.0 Download

– http://bit.ly/adXzj3

• Microsoft Visual Studio Scrum 1.0 Guidance

– http://bit.ly/clAIrd

• Visual Studio Process Templates and Tools

– http://bit.ly/chyBhE

• Professional Scrum Developer Program

– http://bit.ly/dppXd0

• Urban Turtle

– http://urbanturtle.com

Visual Studio ALM Blog Aggregator

http://community.accentient.com

150

Feeds

Search

Contact Us

• We can help with training and consulting on all

subjects relating to Visual Studio, ALM, and Scrum

• Michael McCully – Sales Manager

– [email protected]

– (208) 954-7113

• Richard Hundhausen – President

– [email protected]

– (208) 283-6674