Embed Size (px)
Citation preview
Implementing Scrum Using Team Foundation Server 2012David StarrChief Software CraftsmanScrum.org
David [email protected]@elegantcoder
Chief Craftsman, Scrum.orgElegantCode.com FounderMicrosoft ALM MVP
Find Me Later At DEV-TLC: Application Lifecycle Management (ALM)
Our Backlog
Why Scrum?ScrumdamentalsVisual Studio Scrum 2.0The Product BacklogThe SprintGetting to “Done”
Module 1
Why Scrum?
You might care about Scrum if…
These Things Are Taking Longer
Changing our products
Planning new features
Implementing new features
Releasing our products
Changing our minds
These Things Are Declining
Quality
Value of work done
Trust and Morale
Customer relationships
New Feature ROI
Time
Planning Analysis Develop Test Integrate DeployValidate
Analysis
Develop
Test
Integrate Dep
loy
Validate
Planning
Analysis
Develop
Test
Integrate Dep
loy
Validate
Analysis
Develop
Test
Integrate Dep
loy
Validate
Analysis
Develop
Test
Integrate Dep
loy
Validate
Analysis
Develop
Test
Integrate Dep
loy
Validate
Visibility Ability to Change
Business Value Risk
Talking to Management
Software in 30 DaysBy Ken Schwaber andJeff Sutherland
• ISBN 978-1-118-20666-9• Available now
Module 2
Scrumdamentals
Scrum is …
A framework for Agile softwaredevelopment
A set of rules (defined in the Scrum Guide)
Easy to learn
Difficult to master
http://scrum.org
Elements of Scrum
Roles
• Product Owner
• Development Team
• Scrum Master
Artifacts
• Increment• Product
Backlog• Sprint
Backlog
Events
• Sprint• Sprint
Planning• Daily Scrum• Sprint
Review• Retrospectiv
e
Sprint PlanningScrum Master
SprintBacklog
Dev Team
Daily Scrum
Sprint Retrospective
Product Owner
IncrementProduct Backlog
Sprint
Sprint Review
Module 3
Visual Studio Scrum 2.0
Visual Studio Scrum 2.0
The TFS Process Template for Scrum
Collaboratively developed between Scrum.org and Microsoft
Models the most common implementation model of Scrum
Scrum continues to evolve as does TFS
Visual Studio Scrum 2.0
Work Item Types Queries ReportsProduct Backlog Item Product Backlog Backlog Overview *
TaskFeedback Requests * Release Burndown
Code Review Request * Current Sprint Sprint BurndownCode Review Response * Blocked Tasks Velocity
Feedback Request * Open Impediments
Build Success Over Time
Feedback Response * Sprint Backlog Build SummaryImpediment Test Cases Test Case ReadinessTest Case Unfinished Work Test Plan ProgressShared Steps Work in ProgressSprint
Reports
Scrum reportsBacklog OverviewRelease Burndown Sprint Burndown Velocity
Engineering reportsBuilds Success Over Time Build Summary Test Case Readiness Test Plan Progress
Team Web Access
Completely rewrittenRich UI actions, drag and dropBacklog and Task Board
Real-time chartsVelocity and Sprint burndownSet the Start and End dates
Forecast Tool
Teams
A Team is a new concept in TFS 11
Rich metadataNameDescriptionPhoto
Team Alerts
Vast improvement over individual subscriptionAlerts can be createdfor groups or teamsMany templates tochoose from
Note: to use alerts TFS mustpoint to an SMTP server
Module 4
The Product Backlog
Vague Estimated PBIs
NextNext
Sprint
NextSprint
Tasks
ThisSprint
Understood
NextRelease
OtherBacklog
Items
Backlog Accuracy and Item Detail
Grooming the Product Backlog
Development Team helps the Product Owner prepare the Product Backlog to be actionable
An ongoing activity
Emerging details of PBIsValueEffort estimatesAcceptance criteriaOrder
Module 5
The Sprint
Sprint
SprintPlannin
g
SprintReview
SprintRetro
Daily Scrums
Cone of Uncertainty
This is when projects are typically funded.
Cone of Uncertainty in Scrum
Commitment vs. Forecast
Sprint Backlog
A Common Expression of a Sprint Backlog
Product Backlog
Velocity
1 2 3 4 5 6 7 8 90
5
10
15
20
25
30
Sprint
Featu
re P
oin
ts
Top 3 Avg23
Best Case
Middle 3 Avg 19Likely Case
Bottom 3 Avg 14 Worst Case
Planning Ahead with Scrum
Best Case:3 Sprints X 23 points = 69 points
Most Likely Case:3 Sprints X 19 points = 57points
Worst Case: 3 Sprints X 14 points = 42 points
Product Backlog
Estimate : 13
Estimate : 20
Estimate : 1
Estimate : 3
Estimate : 5
Estimate : 8
Estimate : 3
Estimate : 20
Estimate: 2
Estimate : 100
Estimate : 13
Top 3 Avg - 23Best Case
Middle 3 Avg - 19
Likely Case
Bottom 3 Avg -14
Worst Case
Module 6
Getting to "Done"
Done and Undone
Each Increment must be Done
Definition of Done (DoD)A simple, auditable checklist owned by the teamIt can be influenced by organizational standards and specific requirements of the product or release
Software Development Feedback Cycles
Operational Acceptance (Production)
User Acceptance Testing
System, Performance, Other -ility Testing
Integration Testing
Continuous Integration *
Check-In *
Developer Tests Pass
Compile and Link
IntelliSense
Cost of
Error
Defining Done for the PlumberManufacturer Instructions
Client Criteria
Code or Law
Personal Craftsmanship
Done
Done and Undone
By Ken Schwaber and David Starr
On MSDN
http://bit.ly/NyUyOW
Thank YouDavid Starr
@elegantcoder
Scrum.org | Elegantcode.comFind Me Later At DEV-TLC: Application Lifecycle Management (ALM)
Related Content
Breakout Sessions
FDN02 Application Lifecycle Management (ALM): It’s a Team Sport
DEV321 Continuous Feedback in Agile Teams
DEV344 Developer Collaboration with Visual Studio 2012
DEV346 All Aboard the Team Foundation Server Express
DEV212 Implementing Scrum Using Team Foundation Server 2012
DEV316 Application Lifecycle Management Tools for C++ in Visual Studio 2012
AAP309 Making Agile Estimation Work
DEV263 Dev-Ops Best Practices On The Microsoft Stack
DEV214 Introducing the New Visual Studio 2012 Unit Testing Experience
DEV337 Software Testing with Microsoft Test Manager 2012 and Lab Management
DEV370 Automating Server-Based Build, QA and Test with Visual Studio 2012
Related Content
Breakout Sessions
DEV362 From Development to Production: Optimizing For Continuous Delivery
DEV310 Continuous Delivery of Windows Azure Cloud Apps
DEV318 Working on an Agile Team with Visual Studio 2012
DEV390 IntelliTrace, What Is It and How Can I Use It To My Benefits
DEV217 Deep Dive Into Team Foundation Server 2012 Agile Management Tools
DEV345 The Accidental Team Foundation Server Admin
AAP401 Real World Developer Testing with Visual Studio 2012
DEV340 Taking ALM to the Cloud with the Team Foundation Service
DEV317 Going Beyond F11: Debug Better and Faster with Visual Studio 2012
DEV312 Create Robust, Maintainable Coded UI Tests with Visual Studio 2012
DEV411 Testing Un-Testable Code with Fake in Visual Studio 2012
Related Content
Breakout Sessions
DEV324 A Modern Architecture Review: Using the New Code Review Tools
DEV412 Identify & Fix Performance Problems with Visual Studio 2012 Ultimate
Hands-on Labs (session codes and titles)
DEV11-HOL
Agile Project Management in Team Foundation Server 2012
DEV12-HOL
Build the Right Software and Collaborate Effectively Using Storyboarding and Feedback Tools in Visual Studio 2012
DEV13-HOL
Using IntelliTrace with Production Systems to Quickly Diagnose and Fix Issues
DEV16-HOL
Learn How Microsoft Test Manager 2012 Will Embrace an Exploratory Testing Approach
DEV17-HOL
Explore the New Unit Testing and Code Clone Capabilities of Visual Studio 2012
DEV19-HOL
Discover How the New Features of Team Foundation Server 2012 Can Improve Collaboration in Your Development Team
Resources
Connect. Share. Discuss.
http://europe.msteched.com
Learning
Microsoft Certification & Training Resources
www.microsoft.com/learning
TechNet
Resources for IT Professionals
http://microsoft.com/technet
Resources for Developers
http://microsoft.com/msdn
Evaluations
http://europe.msteched.com/sessions
Submit your evals online
