Your SlideShare is downloading. ×
0
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
Scrum process in visual studio 2010
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

Scrum process in visual studio 2010

2,761

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 …

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,761
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
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
  • 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 & 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 & 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 & Selecting Process TemplateAreas & Iterations (Release and Sprint planning some like to renumber Sprints after release; manual processSprints (All Sprints query)Details of Sprint 1Sprint goalRetrospectiveShow Product Backlog & 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 > 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
  • Transcript

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

    ×