Your SlideShare is downloading. ×
0
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Nuts and Bolts of Scrum Template (Dog Food III)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Nuts and Bolts of Scrum Template (Dog Food III)

3,854

Published on

TFS2010: Nuts and Bolts of Visual Studio Scrum v1.0 Template …

TFS2010: Nuts and Bolts of Visual Studio Scrum v1.0 Template
Visual Studio and Team Foundation Server (TFS) are the cornerstones of development on the Microsoft .NET platform. These tools represent some of the best opportunities for success and to experience a focused and smooth software development process. For TFS 2010 Microsoft heavily invested in Scrum and is moving some internal product teams onto the approach.
This session is not about Scrum in depth, (for that please visit scrum.org) but rather, we will cover the lifecycle of creating work items and how this fits into Scrum using Visual Studio ALM and Team Foundation Server. We will cover in detail:
* How to successfully gather requirements
* How to plan a project using TFS 2010 and Scrum
* How to work with a product backlog in TFS 2010
* The right way to plan a sprint with TFS 2010
* Tracking your progress
* The right way to use work items
* Leveraging built-in reporting and Project portals available on the SharePoint dashboard
* Reports targeted to the Product Owner / Project Manager
You will walk away knowing how to interpret and understand a project health and progress. Visual Studio ALM is designed to address many of the problems faced by teams using traditional approaches. It does
so by providing a set of integrated tools to help teams improve their software development activities and to help management better support the software development processes.

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,854
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
245
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com DOG FOOD CONFERENCE III: Nuts & Bolts of Visual Studio Scrum v1.0 Template
  • 2. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Backlog • Introductions • State of Agile • Scrum Overview • Visual Studio Scrum v1.0 Template • Putting It To Work • Q&A PLEASE ASK QUESTIONS & BE INTERACTIVE! Some of the slides were contributed by: Richard Hundhausen, Aaron Bjork, Martin Hinshelwood, Paul Neumeyer, Ken Schwaber, Randy Pagels, Jeff Hunsaker, & others
  • 3. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com 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 govorin.blogspot.com www.twitter.com/Leshka About Harley • 10 years old Black Labrador Retriever
  • 4. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com About Cardinal Fast Facts: • Over 200 professionals with offices in 4 cities • Microsoft “Managed Partner”; Gold Certified since 1999 • VSTS Inner Circle Partner • MVPs; Virtual TSPs Our Focus: • Visual Studio ALM/TFS • SharePoint 2007 & 2010 • Microsoft Online Services • Microsoft Business Intelligence • .NET Architecture/ Development • Client Training
  • 5. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Objectives • Provide a level set on Agile and Scrum • Describe what you get with the Visual Studio Scrum Process Template • Demonstrate how you can start using Scrum through Visual Studio What we want you to walk away with…
  • 6. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com What is Agile? Time-box Activity… 2min
  • 7. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com * AGILE Agile software development focuses on regularly delivering business value. It embraces change while leveraging feedback to produce high quality, desired results. * Different for every company • Agile is a Movement • Represented by Methodologies & Frameworks • Comprised of a set of Development & Engineering Practices
  • 8. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Why Agile? Typical Project Challenges
  • 9. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com State of Agile
  • 10. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Backlog  Introductions  State of Agile • Scrum Overview • Visual Studio Scrum v1.0 Template • Putting It To Work • Q&A
  • 11. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com • 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 a Slide http://www.scrum.org/scrumguides
  • 12. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Roles in Scrum Product Owner ScrumMaster Team Stakeholders, everyone else ScrumTeam
  • 13. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Timeboxes of Scrum doing the work + Daily Scrums Sprint Planning Sprint Review Sprint Retrospective Release Planning 8 hours Sprint 4 weeks Sprint Planning 8 hours Daily Scrum 15 minutes Sprint Review 4 hours Sprint Retrospective 4 hours
  • 14. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com • 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 Artifact - Product Backlog
  • 15. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com • 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
  • 16. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Key Artifact - Release Burndown Chart Measures work remaining across the time of a release plan
  • 17. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Key Artifact - Sprint Burndown Chart Measures work remaining across the time of a Sprint
  • 18. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Backlog  Introductions  State of Agile  Scrum Overview • Visual Studio Scrum v1.0 Template • Putting It To Work • Q&A
  • 19. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Visual Studio 2010 Scrum v1.0 Template
  • 20. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Visual Studio 2010 • No longer just a developer IDE • TFS added server-side capability to manage the entire software lifecycle • No need to license separate tools from HP/Mercury, IBM/Rational, Rally, etc… • Already own with MSDN subscription?
  • 21. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Microsoft Visual Studio Scrum 1.0 Template • A Process Template introduced shortly after Visual Studio 2010 launched • 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 © 2010 Cardinal Solutions Group What is it?
  • 22. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com What’s in the Process Template? * Nearly identical to that found in the MSF for Agile Software Development 5.0 template Work Items and Processes Team Queries Reports • Sprint • Product Backlog Item • Task • Impediment • Bug • Test Case* • Shared Steps* • All Sprints • Product Backlog • Blocked Tasks • Open Impediments • Sprint Backlog • Test Cases • Unfinished Work • Work in Progress • Release Burndown • Spring Burndown • Velocity • Build Success over Time* • Build Summary* • Test Case Readiness* • Test Plan Progress*
  • 23. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Queries • Product queries • All Sprints • Product Backlog • Current Sprint queries • Blocked Tasks • Open Impediments • Sprint Backlog • Test Cases • Unfinished Work • Work in Progress
  • 24. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Sprint Work Item Type • Provides a way for your team to capture additional metadata about the Sprint – Start date, finish date, goal, and retrospective
  • 25. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Product Backlog Item Work Item Type • Represents a product requirement
  • 26. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com PBI States
  • 27. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Task Work Item Type • Represents the detailed work the team must do in order to achieve their Sprint Goal
  • 28. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Task States
  • 29. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Impediment Work Item Type • Represents an issue or problem that prevents the team from completing its tasks efficiently
  • 30. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Test Case Work Item Type • Used to define both manual and automated tests
  • 31. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Bug Work Item Type • Represents a defect in the product • PBI
  • 32. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Reports • Scrum reports • Release Burndown • Sprint Burndown • Velocity • Engineering reports • Build Summary • Builds Success Over Time • Test Case Readiness • Test Plan Progress
  • 33. Visual Studio 2010 ALM - Scrum • 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 © 2010 Cardinal Solutions Group Visual Studio Scrum Activities
  • 34. Visual Studio 2010 ALM - Scrum 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 * © 2010 Cardinal Solutions Group
  • 35. Visual Studio 2010 ALM - Scrum Backlog  Introductions  State of Agile  Scrum Overview  Visual Studio Scrum v1.0 Template • Putting It To Work • Q&A
  • 36. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Putting It to Work Scrum Activities and Demo Demo • Establishing a Product Backlog • Managing a Sprints • Creating and linking Task • Managing Tests and Bugs • Reporting
  • 37. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com
  • 38. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com 41
  • 39. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com 42
  • 40. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Retrospective  Provide a level set on Agile and Scrum  Describe what you get with the Visual Studio Scrum Process Template  Demonstrate how you can implement Scrum through Visual Studio How did we do?
  • 41. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Agenda Thank You • @Leshka • AGovorine@CardinalSolutions.com • http://govorin.blogspot.com • 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
  • 42. Copyright 2010 Cardinal Solutions Group www.cardinalsolutions.com Visual Studio ALM Goals • Approachable and intuitive products • Tight integration across tools, process and roles • Single integrated server for collaboration • Real-time reporting from data warehouse • Audit trail for compliance • Improve predictability and reduce risk Increase Project Transparency Facilitate Team Collaboration • Lightweight, customizable process • Integrated quality tools for each role • Reduce defects and security vulnerabilities Improve Software Quality

×