Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Nuts and Bolts of Scrum Template (extended)

4.650 visualizaciones

Publicado el

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.

  • Sé el primero en comentar

Nuts and Bolts of Scrum Template (extended)

  1. 1. Nuts & Bolts of Visual Studio Scrum v1.0 Template Dog Food Conference III Alexei V. Govorine 1 © 2010 Cardinal Solutions Group
  2. 2. Visual Studio 2010 ALM - Scrum Backlog • Why Agile? • Scrum Overview • Visual Studio Scrum v1.0 Template • Q&A © 2010 Cardinal Solutions Group 2 Some of the slides were contributed by: Richard Hundhausen, Aaron Bjork, Martin Hinshelwood, Paul Neumeyer, Ken Schwaber, Randy Pagels, Jeff Hunsaker, & others
  3. 3. Visual Studio 2010 ALM - Scrum 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 © 2010 Cardinal Solutions Group 3govorin.blogspot.com www.twitter.com/Leshka
  4. 4. Visual Studio 2010 ALM - Scrum • 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 © 2010 Cardinal Solutions Group
  5. 5. Visual Studio 2010 ALM - Scrum WHAT IS AGILE? TIMEBOX ACTIVITY – 2 MIN © 2006 Cardinal Solutions Group 5 Please write down a few words or a sentence on what Agile means to you.
  6. 6. Visual Studio 2010 ALM - Scrum * AGILE Agile software development focuses on regularly delivering business value. It embraces change while leveraging feedback to produce high quality, desired results. © 2009 Cardinal Solutions Group 6 * Different for every company Agile is a Movement Represented by Methodologies & Frameworks Comprised of a set of Development & Engineering Practices
  7. 7. Visual Studio 2010 ALM - Scrum Why Agile? (Project Challenges) 7 © 2010 Cardinal Solutions Group
  8. 8. Visual Studio 2010 ALM - Scrum The Forrester Wave™: Agile Development Management Tools, Q2 2010, Forrester Research, Inc., May 5, 2010. © 2010 Cardinal Solutions Group
  9. 9. Visual Studio 2010 ALM - Scrum The Forrester Wave™: Agile Development Management Tools, Q2 2010, Forrester Research, Inc., May 5, 2010. © 2010 Cardinal Solutions Group
  10. 10. Visual Studio 2010 ALM - Scrum Indeed.com™: Trend search on keywords: agile, scrum, lean, kanban, xp, iterative, cmmi, waterfall, rup. May 25, 2010. © 2010 Cardinal Solutions Group
  11. 11. Visual Studio 2010 ALM - Scrum Backlog Why Agile? • Scrum Overview • Visual Studio Scrum v1.0 Template • Q&A © 2010 Cardinal Solutions Group 11
  12. 12. Visual Studio 2010 ALM - Scrum Scrum Overview © 2010 Cardinal Solutions Group 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.
  13. 13. Visual Studio 2010 ALM - Scrum “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. © 2010 Cardinal Solutions Group
  14. 14. Visual Studio 2010 ALM - Scrum • 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 © 2010 Cardinal Solutions Group
  15. 15. Visual Studio 2010 ALM - 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 © 2010 Cardinal Solutions Group
  16. 16. Visual Studio 2010 ALM - Scrum Roles in Scrum Product Owner ScrumMaster Team Stakeholders = everyone else ScrumTeam © 2010 Cardinal Solutions Group
  17. 17. Visual Studio 2010 ALM - Scrum • 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 © 2010 Cardinal Solutions Group
  18. 18. Visual Studio 2010 ALM - Scrum • Who is responsible for ensuring the process is understood and followed • The “Process” – Host meetings – Manage process – Remove impediments Key Role - ScrumMaster © 2010 Cardinal Solutions Group
  19. 19. Visual Studio 2010 ALM - Scrum • 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 © 2010 Cardinal Solutions Group
  20. 20. Visual Studio 2010 ALM - Scrum • 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 © 2010 Cardinal Solutions Group
  21. 21. Visual Studio 2010 ALM - Scrum • 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 © 2010 Cardinal Solutions Group
  22. 22. Visual Studio 2010 ALM - 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 © 2010 Cardinal Solutions Group
  23. 23. Visual Studio 2010 ALM - 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 © 2010 Cardinal Solutions Group
  24. 24. Visual Studio 2010 ALM - Scrum • 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 © 2010 Cardinal Solutions Group
  25. 25. Visual Studio 2010 ALM - Scrum • 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 © 2010 Cardinal Solutions Group
  26. 26. Visual Studio 2010 ALM - Scrum Key Artefact - Release Burndown Chart • A Release/Product Burndown measures work remaining across the time of a release plan © 2010 Cardinal Solutions Group
  27. 27. Visual Studio 2010 ALM - Scrum Key Artefact - Sprint Burndown Chart • A Sprint Burndown measures work remaining across the time of a Sprint
  28. 28. Visual Studio 2010 ALM - Scrum Backlog Why Agile? Scrum Overview • Visual Studio Scrum v1.0 Template • Q&A © 2010 Cardinal Solutions Group 28
  29. 29. Visual Studio 2010 ALM - Scrum VISUAL STUDIO SCRUM V1.0 TFS PROCESS TEMPLATE © 2010 Cardinal Solutions Group 29
  30. 30. Visual Studio 2010 ALM - Scrum Visual Studio 2010 © 2010 Cardinal Solutions Group
  31. 31. Visual Studio 2010 ALM - Scrum 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 © 2010 Cardinal Solutions Group
  32. 32. Visual Studio 2010 ALM - Scrum 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 © 2010 Cardinal Solutions Group
  33. 33. Visual Studio 2010 ALM - Scrum 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 © 2010 Cardinal Solutions Group
  34. 34. Visual Studio 2010 ALM - Scrum Sprint Work Item Type • Provides a way for your team to capture additional metadata about the Sprint – Start date, finish date, goal, and retrospective © 2010 Cardinal Solutions Group
  35. 35. Visual Studio 2010 ALM - Scrum Product Backlog Item Work Item Type • Represents a product requirement © 2010 Cardinal Solutions Group
  36. 36. Visual Studio 2010 ALM - Scrum PBI State © 2010 Cardinal Solutions Group
  37. 37. Visual Studio 2010 ALM - Scrum Task Work Item Type • Represents the detailed work the team must do in order to achieve their Sprint Goal © 2010 Cardinal Solutions Group
  38. 38. Visual Studio 2010 ALM - Scrum Task State © 2010 Cardinal Solutions Group
  39. 39. Visual Studio 2010 ALM - Scrum Impediment Work Item Type • Represents an issue or problem that prevents the team from completing its tasks efficiently © 2010 Cardinal Solutions Group
  40. 40. Visual Studio 2010 ALM - Scrum Impediment State © 2010 Cardinal Solutions Group
  41. 41. Visual Studio 2010 ALM - Scrum Test Case Work Item Type • Used to define both manual and automated tests © 2010 Cardinal Solutions Group
  42. 42. Visual Studio 2010 ALM - Scrum Test Case State © 2010 Cardinal Solutions Group
  43. 43. Visual Studio 2010 ALM - Scrum Bug Work Item Type • Represents a defect in the product • PBI © 2010 Cardinal Solutions Group
  44. 44. Visual Studio 2010 ALM - Scrum Bug State © 2010 Cardinal Solutions Group
  45. 45. Visual Studio 2010 ALM - Scrum Queries • Product queries – All Sprints – Product Backlog • Current Sprint queries – Blocked Tasks – Open Impediments – Sprint Backlog – Test Cases – Unfinished Work – Work in Progress © 2010 Cardinal Solutions Group
  46. 46. Visual Studio 2010 ALM - Scrum Reports • Scrum reports – Release Burndown – Sprint Burndown – Velocity • Engineering reports – Build Summary – Builds Success Over Time – Test Case Readiness – Test Plan Progress © 2010 Cardinal Solutions Group
  47. 47. Visual Studio 2010 ALM - Scrum 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 © 2010 Cardinal Solutions Group
  48. 48. 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
  49. 49. Visual Studio 2010 ALM - Scrum 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 © 2010 Cardinal Solutions Group
  50. 50. Visual Studio 2010 ALM - Scrum © 2010 Cardinal Solutions Group 50
  51. 51. Visual Studio 2010 ALM - Scrum © 2010 Cardinal Solutions Group 51
  52. 52. Visual Studio 2010 ALM - Scrum © 2010 Cardinal Solutions Group 52
  53. 53. Visual Studio 2010 ALM - Scrum Burndown Why Agile? Scrum Overview Visual Studio Scrum v1.0 Template • Q&A © 2010 Cardinal Solutions Group 53
  54. 54. Visual Studio 2010 ALM - Scrum 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/) © 2010 Cardinal Solutions Group 54
  55. 55. Visual Studio 2010 ALM - Scrum Thank You Contact Alexei: • @Leshka • AGovorine@CardinalSolutions.com • http://govorin.blogspot.com © 2010 Cardinal Solutions Group 55

×