This document summarizes a presentation by Gerard Beckerleg on using Scrum with Team Foundation Server (TFS) 2012. The presentation covers Agile and Scrum theory, walks through a sample project using manual Scrum processes, and demonstrates how to use TFS 2012 and its Scrum template. It discusses the history of Scrum at SSW, an overview of Scrum roles, artifacts, and events, and how to implement the core Scrum processes like sprint planning, daily standups, reviews, and retrospectives.
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
Gerard beckerleg scrum and tfs 2012
1. Scrum with TFS 2012
Gerard Beckerleg
Senior Software Architect
Live Backchannel: #NETUG
Delivering Awesome Web Applications
2. About me
Gerard Beckerleg from England
Senior Software Architect at SSW
Teacher at UTS (.NET and SharePoint)
Professional Scrum Developer
Experience in traditional waterfall development
Experience in Agile/Scrum development
Sydney Airport (Macquarie Airports)
National Australia Day Council
Toll
3. History of Scrum at SSW
1990 “rough” agile practices + waterfall projects
2000 Kent Beck book - Extreme Programming
SSW generally following the 12 principles of XP
2005 TFS released with agile template
2009 Scrum
2010 Microsoft release Scrum template
2011 Scrum updated
2011 Chief Architect Adam Cogan, ALM MVP of the year
4. Agenda Our Backlog
Part 1 Agile and Scrum theory
Part 2 Manual - Walkthrough project using Scrum
Part 3 Tools - Walkthrough using TFS 2012 and Scrum
Template v2.1
Delivering Awesome Web Applications
6. Agile Manifesto (agilemanifesto.org)
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
7. Visibility Ability to Change
Business Value
Agile
Plan driven development (Traditional)
@elegantcoder
30. 5
Balance
summary
3
3
Set up
staging server
3
Set up
production
server
31. To Do In Progress Done
5
Balance
summary
3
Set up
staging server
3
Set up
production
server
32. To Do In Progress Done
8
5 Partial view
Balance
summary 8
Master page
1
3 DNS
Set up
staging server Provision 4
server
3 1
Set up DNS
production
server Provision 4
server
33. Backlog Accuracy and Item Detail
Vague Understood Estimated PBIs Tasks
Other Next
Next Next This
Backlog Next
Release Sprint Sprint
Items Sprint
richard@accentient.com
34.
35. Step 4 - Day to day activities during
the Sprint
Daily Scrum
Development
Product Backlog Grooming
36. To Do In Progress Done
4
5 Partial view
Balance
summary 0
Master page
1
3 DNS
Set up
staging server Provision 0
server
3 1
Set up DNS
production
server Provision 4
server
39. Steps 5,6,7 - The Sprint Review
Gather feedback from Product Increment
But wait….is your Product Increment really done?
40.
41. Step 8 - The Sprint Retrospective
Inspect and adapt
3 Questions
What went well (reinforce good behaviour)
What didn’t go well
What can we improve for the next sprint
Output is actionable item(s) for Product Backlog
42. Part 3 Tools - Walkthrough using TFS
2012 and Scrum Template v2.1
Delivering Awesome Web Applications
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59. Summary
Part 1 Agile and Scrum theory
Part 2 Manual - Walkthrough project using Scrum
Part 3 Tools - Walkthrough using TFS 2012 and Scrum
Template v2.1
Delivering Awesome Web Applications
I’m passionate about Scrum and want to share how we are currently doing things at SSW
In February 2001, 17 software developers[6] met at the Snowbird, Utah resort, to discuss lightweight development methods. They published the Manifesto for Agile Software Development[1] to define the approach now known as agile software developmentKent BeckWard CunninghamMartin FowlerRobert C. MartinKen SchwaberJeff Sutherland
Delivering a product increment
Easy to learn difficult to masterRichard Hundhausen - P90X - cross-training (weight training, martial arts, yoga and calisthenics) and periodization, combined with a nutrition and dietary supplement plan
PO – Decides the whatScrum Master – Guides the processDevelopment Team – Builds what the PO decides
Product Backlog – Can be excel, is owned by the PO but groomed by the team
Sprint – period of time between 1 and 3 weeks
PBI are not tasks, talk in business language
FeaturesBugsTechnical workKnowledge acquisitionAcceptance Criteria – Yeah but questions
FeaturesBugsTechnical workKnowledge acquisitionAcceptance Criteria – Yeah but questions
FeaturesBugsTechnical workKnowledge acquisitionAcceptance Criteria – Yeah but questions
ComparativeRelative size
FeaturesBugsTechnical workKnowledge acquisitionAcceptance Criteria – Yeah but questions