Scrum & Visual Studio 2010<br />Scrum process targeting in .NET with Visual Studio & TFS 2010<br />
About Scott Koland<br />Senior Consultant @ Magenic<br />Specialize in:<br />WPF & Silverlight<br />Scrum<br />.NET / C#<b...
Agenda<br />Scrum Fundamentals<br />Scrum in Team Foundation Server 2010<br />Scrum with the MS VS Scrum 1.0 Process Templ...
Why Scrum?<br />What problem is Agile and Scrum solving?<br />Long development time<br />Software project high failure rat...
What kind of problem?<br />
Scrum Works<br />Higher success rates<br />Produces higher quality<br />Has high stakeholder satisfaction<br />Yields bett...
Scrum Process<br />24 hours<br />Daily Scrum<br />Meeting<br />Backlog tasks<br />expanded<br />by team<br />Sprint<br />S...
Scrum Roles<br />Product Owner<br />Customer Voice, Product Vision<br />ScrumMaster<br />Manager of the Process<br />The T...
Scrum Artifacts<br />Product Backlog<br />Sprint Backlog<br />Burndown Charts<br />Working Software<br />
Demo<br />Scrum project in Visual Studio 2010<br />
Quality<br />How do we validate what is built?<br />What does success look like?<br />
Done<br />Team defines done (Definition of Done)<br />Should be a specific list, e.g.<br />Code complete<br />Tests pass<b...
Bug Fixing Goals<br />Quickly fix and move on?<br />Ignore?<br />Or improve software.<br />
Fixing a Bug<br />Verify<br />write a failing unit test <br />Fix the bug<br />	unit test should pass<br />meets the team ...
Demo<br />Unit Testing and Bug Resolution<br />
Why Unit Tests help when fixing bugs?<br />Document developer intent<br />Verify existence (and resolution) of a bug<br />...
Planning<br />Planning is continuous in Scrum<br />Release Planning<br />Sprint Planning Meeting<br />Continually groom th...
Cone of Uncertainty<br />
Agile and the Cone of Uncertainty<br />initial concept<br />software release<br />T Shirt Sizes<br />Hours<br />Story Poin...
Planning & Estimation Demo<br />Planning and Task Boards from Urban Turtle<br />
Estimation<br />
Continuous Integration<br />Imperative to developing robust software quickly<br />Inspect and Adapt<br />Fail early<br />T...
Scrum Industry<br />Two companies<br />Scrum Alliance<br />Scrum.org (Ken Schwaber; aligned with Microsoft)<br />Scrum.org...
Professional Scrum Developer<br />From Microsoft & Scrum.org<br />5 day Training Program for Developers<br />Scrum trainin...
Questions?<br />Scott Koland<br />email: scottko@magenic.com<br />twitter: @scottkoland<br />blog: www.scottkoland.com/blo...
Resources<br />Scrum.org guide<br />http://www.scrum.org/scrumguides/<br />Scrum 1.0 Template for TFS<br />http://visualst...
Upcoming SlideShare
Loading in...5
×

Scrum process in visual studio 2010

2,795

Published on

This session will describe how the new Microsoft Visual Studio Scrum 1.0 process template for VS 2010 can be used to manage a Scrum project. The session will review the fundamentals of the Scrum framework and show how the Scrum template maps those items in Team Foundation Server. Other aspects of managing a successful Scrum project in VS will be reviewed, such as techniques for ensuring quality on a self-directed development team and how a Scrum team can effectively estimate and plan work items.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

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

No notes for slide
  • This presentation will introduce some Scrum basics and show how Scrum can be used in TFS and Visual Studio 2010.Scrum is about Roles, Timeboxes, and Artifacts.
  • Historically long time lag; Inflexible, unrealisticLittle or no feedback between analyst and developerEach phase must be 100% complete before moving on to the nextCan’t see the details from that heightResults in the paralysis of analysisIf we built similar systems with the same technologies over and over, it would probably work.If all conditions are ideal, it just might work.Any methodology requiring perfection to succeed is flawed.
  • Ralph Stacey’s Agreement &amp; Certainty MatrixSimple – Easily knowable. Car key.Complicated – not simple, but still knowable. (Pre computer) Car operation.Complex – not fully knowable, but reasonable to predict (Car traffic).Chaotic – neither knowable nor predictableBaking a cake. Easy to generate success once the basics are understood. Few techniques to master; once mastered, high likelihood of success.Complicated – Not simple, but still knowable. Have many parts. Launching a rocket to the moon. No easy straightforward recipe; success requires many people &amp; teamwork, unanticipated results are common.Complex – Not fully knowable, but reasonable. Unable to fully predict.Raising a child. Car traffic.Chaotic – neither knowable nor predicable.
  • Empirical process
  • Scrum is a framework within the Agile software development methodologies.Empirical process; designed for complex projectsEmphasizes Self Managed teamsIterative, Time Boxed
  • Map to TFS p 86.
  • Overview Demo (20 - 30 minutes)Adding Project &amp; Selecting Process TemplateAreas &amp; Iterations (Release and Sprint planning some like to renumber Sprints after release; manual processSprints (All Sprints query)Details of Sprint 1Sprint goalRetrospectiveShow Product Backlog &amp; PBI’s Area for estimation.Work Items / Tasks / Linked items etc.Bug (handled later)Sprint BurndownRelease BurndownVelocity- Must alter each “Current Sprint” query
  • Okay, great, we have self directed, cross functional software teams creating our products. But how do we go about ensuring quality in such a team organization?How can we ensure quality in a software project?
  • Checklist Manifestop. 100
  • So what are my goals when finding and fixing a bug? Many times in software development, our goal is to resolve the defect and implement a fix as quickly as possible. While this is a good goal, a better goal is to establish a mechanism in our codebase that verifies the existence of the bug, and documents the intent of the developer who is fixing the bug.
  • In Visual Studio projects that utilize unit testing, it is recommended to follow this process to resolve a bug.
  • (15 minutes Prep: open ShoppingCart; ShoppingCartTest; bug; task)Look at bugGet LatestRun unit testsFailing unit testRerun tests – fail (Red)Fix codeRerun tests – pass (Green)RefactorLink taskCheck in I’ve been assigned this bug. I’ll open the bug.I’ll get the latest codebase and run the unit tests. (all tests pass)I’ll then reproduce the bug (the issue is reproducible)Now, I need to inspect the code and determine what component is failing. I’ve worked on this code frequently, so I already know this is in the Shopping Cart’s AddItem method.Now, I’ll write my failing unit test and run tests. Notice how the one fails.And now I’ll fix my defect. All of my tests pass, now I’ll rerun the app and verify the defect is resolved.Now, here is where I would check in the code and close out the bug.
  • In conclusion, I will leave you with a few aspects of why unit tests can be important when resolving defects. While this was a simple example, you could see how having many documented bugs will reduce the introduction of new bugs to the codebase as they help document the developers intent.Also, verifying the existence of a bug and documenting it with a unit test ensures that steps have been taken to reduce the likelihood that it will crop up again in the future.Thank you.
  • Sprint Planning Meeting – What, then How10% of a Sprint should be spent grooming the product backlog.
  • Boehm, B (1981). Software Engineering Economics, Prentice-Hall.McConnell, S (2006). Software Estimation: Demystifying the Black Art, Microsoft Press.- At Initial Concept, we are unlikely to accurately estimate an item. 16x more likely to vary, from low to highAs project progresses, we must work to reduce the cone. It doesn’t reduce itself
  • EstimationPlanning PokerPlanning BoardUrban Turtle ToolShow different views of same data in Planning BoardTask BoardPlanning is a continuous process with Scrum. From the initial release plan to each Sprint Planning Meeting and into daily work, planning is continuous because the direction is changing due to inspection and adaptation.One aspect that goes hand in hand with planning is estimating. Estimating is one of the most challenging aspects of software development to do well. Scrum has some excellent planning techniques to allow for effective planning, and allow for continuous improvement in planning software development.
  • Why do I care?
  • Right click Builds &gt; New Build Definition ...Trigger = CIBuild Controller; new in 2010 (manages Build Agents)(can Queue builds against specific Build Agents)(can also use TFS Admin Console)Required output folder on \\\\server\\shareRequires solution to buildCan configure auto unit test execution
  • Scrum process in visual studio 2010

    1. 1. Scrum & Visual Studio 2010<br />Scrum process targeting in .NET with Visual Studio & TFS 2010<br />
    2. 2. About Scott Koland<br />Senior Consultant @ Magenic<br />Specialize in:<br />WPF & Silverlight<br />Scrum<br />.NET / C#<br />email: scottko@magenic.com<br />twitter: @scottkoland<br />blog: www.scottkoland.com/blog<br />
    3. 3. Agenda<br />Scrum Fundamentals<br />Scrum in Team Foundation Server 2010<br />Scrum with the MS VS Scrum 1.0 Process Template<br />Ensuring Quality<br />Unit Testing<br />Planning & Estimating<br />
    4. 4. Why Scrum?<br />What problem is Agile and Scrum solving?<br />Long development time<br />Software project high failure rate<br />Poor quality<br />Unmet customer needs<br />Unsatisfactory working environments (iterative death marches)<br />Lack of timely feedback<br />
    5. 5. What kind of problem?<br />
    6. 6. Scrum Works<br />Higher success rates<br />Produces higher quality<br />Has high stakeholder satisfaction<br />Yields better ROI<br />Delivers systems to market sooner<br />76% of organizations reporting in 2009 have one or more agile project underway*<br />*Dr. Dobb’s Journal’s July 2009 State of the IT Union Survey - www.ambysoft.com/surveys/stateOfITUnion200907.html<br />
    7. 7. Scrum Process<br />24 hours<br />Daily Scrum<br />Meeting<br />Backlog tasks<br />expanded<br />by team<br />Sprint<br />Sprint Backlog<br />Potentially Shippable<br />Product Increment<br />Product Backlog<br />As prioritized by Product Owner<br />Vision<br />
    8. 8. Scrum Roles<br />Product Owner<br />Customer Voice, Product Vision<br />ScrumMaster<br />Manager of the Process<br />The Team<br />Anyone who commits to doing work<br />Everyone is a Developer<br />
    9. 9. Scrum Artifacts<br />Product Backlog<br />Sprint Backlog<br />Burndown Charts<br />Working Software<br />
    10. 10. Demo<br />Scrum project in Visual Studio 2010<br />
    11. 11. Quality<br />How do we validate what is built?<br />What does success look like?<br />
    12. 12. Done<br />Team defines done (Definition of Done)<br />Should be a specific list, e.g.<br />Code complete<br />Tests pass<br />Everything checked-in<br />Acceptance criteria from Product owner met<br />Potentially Shippable<br />Fit for Purpose<br />
    13. 13. Bug Fixing Goals<br />Quickly fix and move on?<br />Ignore?<br />Or improve software.<br />
    14. 14. Fixing a Bug<br />Verify<br />write a failing unit test <br />Fix the bug<br /> unit test should pass<br />meets the team definition of done<br />Verify<br />rerun all tests <br />refactor and re-verify as necessary<br />Check In code<br />Close Task & Bug work items<br />Red<br />Green<br />Refactor<br />
    15. 15. Demo<br />Unit Testing and Bug Resolution<br />
    16. 16. Why Unit Tests help when fixing bugs?<br />Document developer intent<br />Verify existence (and resolution) of a bug<br />Reduce bugs<br />
    17. 17. Planning<br />Planning is continuous in Scrum<br />Release Planning<br />Sprint Planning Meeting<br />Continually groom the Product Backlog<br />Estimation is difficult in software<br />
    18. 18. Cone of Uncertainty<br />
    19. 19. Agile and the Cone of Uncertainty<br />initial concept<br />software release<br />T Shirt Sizes<br />Hours<br />Story Points<br />e.g.<br />Small = 2<br />Medium = 5<br />Large = 12<br />Extra Large = 25<br />XX Large = 60<br />< 16 hours<br />Modified Fibonacci – Planning Poker<br />0, 1/2, 1, 2, 3, 5, 8, 13, 20, 40, 100<br />time<br />certainty<br />Source: http://agile101.net/2009/08/18/agile-estimation-and-the-cone-of-uncertainty/<br />
    20. 20. Planning & Estimation Demo<br />Planning and Task Boards from Urban Turtle<br />
    21. 21. Estimation<br />
    22. 22. Continuous Integration<br />Imperative to developing robust software quickly<br />Inspect and Adapt<br />Fail early<br />Team Foundation Build 2010<br />
    23. 23. Scrum Industry<br />Two companies<br />Scrum Alliance<br />Scrum.org (Ken Schwaber; aligned with Microsoft)<br />Scrum.org saw need for Scrum Developer Training beyond Certified ScrumMaster.<br />http://www.scrum.org/originsofscrumorg<br />
    24. 24. Professional Scrum Developer<br />From Microsoft & Scrum.org<br />5 day Training Program for Developers<br />Scrum training with Visual Studio & TFS<br />
    25. 25. Questions?<br />Scott Koland<br />email: scottko@magenic.com<br />twitter: @scottkoland<br />blog: www.scottkoland.com/blog<br />
    26. 26. Resources<br />Scrum.org guide<br />http://www.scrum.org/scrumguides/<br />Scrum 1.0 Template for TFS<br />http://visualstudiogallery.msdn.microsoft.com/en-us/59ac03e3-df99-4776-be39-1917cbfc5d8e<br />VS 2010 RTM VM with TFS 2010 and Labs<br />Blog: http://blogs.msdn.com/b/briankel/archive/2010/06/25/now-available-visual-studio-2010-rtm-virtual-machine-with-sample-data-and-hands-on-labs.aspx<br />Labs: http://download.microsoft.com/download/9/E/2/9E2CCC64-CF5A-4E47-9DC8-C6CEA9344740/VisualStudio2010RTM-ALM-Labs.zip<br />VM: http://www.microsoft.com/downloads/details.aspx?FamilyID=592e874d-8fcd-4665-8e55-7da0d44b0dee&displaylang=en<br />Estimation & Cone of uncertainty<br />http://abdulmoniem.wordpress.com/2010/04/19/software-estimation-chapter-4-review-where-does-estimation-error-come-from/<br />Complexity<br />http://www.noop.nl/2008/08/simple-vs-complicated-vs-complex-vs-chaotic.html<br />http://www.agileevolution.com/blog/2010/10/5/scrum-and-complexity-theory.html<br />http://deepfreeze9.blogspot.com/2007/09/software-complex-vs-complicated.html<br />http://www.lostgarden.com/2006/04/managing-game-design-risk-part-i.html<br />

    ×