stephen forte chief strategy officer telerik session code: wux310
TRANSCRIPT
Tech*ED Daily ScrumStephen ForteChief Strategy OfficerTelerikSession Code: WUX310
Session.About();Short Intro to Scrum
Assume you have at least heard of Scrum or Agile Tons of Q&A
Speaker.Bio.ToString();Chief Strategy Officer of TelerikCertified Scrum MasterActive in the Community:
International Conference Speaker for 12+ YearsRD, MVP and INETA Speaker Co-moderator & founder of NYC .NET Developers Group http://www.nycdotnetdev.comWrote a few books: SQL Server 2008 Developers Guide (MS Press)
MBA from the City University of New YorkPast:
CTO and co-Founder of Corzen, Inc. (TXV: WAN)CTO of Zagat Survey
Burndown
What is ScrumTech*Ed Daily ScrumQ&A (The fun part)
What is Scrum?
•Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time
•It allows the business to rapidly and repeatedly inspect actual working software
•Stresses communication
What is Scrum?
CharacteristicsSelf-organizing teamsProduct progresses in a series of month-long (or shorter) “sprints”Requirements are captured as items in a list of “product backlog”No specific engineering practices prescribed
Can use any methodology you like
Scrum
Sidebar: Scrum in the Real WorldCorzen’s Data Engine Development in 2006Sprint 1: infrastructureSprint 2: new engine (XML/reflection)
Business value: Enabled multiple sitesSprint 3: vertical independent engine
Business value: one data engine for all spideringSprint 4: distributed processing (Seti@Home style)
Business value: unlimited spidering via cheap VPSesSprint 5: management (WCF)
Business value: thousands of spiders, 1 admin
Product owner
Define the features of the productDecide on release date and contentBe responsible for the profitability of the product (ROI)Prioritize features according to market value Adjust features and priority every iteration, as needed Accept or reject work results
The ScrumMaster
Represents management to the projectResponsible for enacting Scrum values and practicesRemoves impediments Ensure that the team is fully functional and productiveEnable close cooperation across all roles and functionsShield the team from external interferences
The team
Typically 4-9 peopleCross-functional:
Programmers, testers, user experience designers, etc.
Members should be full-timeMay be exceptions (DBA)
Teams are self-organizingIdeally, no titles but rarely a possibility
Membership should change only between sprints
Product backlog
The requirementsA list of all desired work on the projectIdeally expressed such that each item has value to the users or customers of the product Prioritized by the product ownerReprioritized at the start of each sprintThis is the
product backlog
This is the product backlog
A sample product backlog
Backlog item EstimateAllow a guest to make a reservation 3
As a guest, I want to cancel a reservation. 5
As a guest, I want to change the dates of a reservation. 3
As a hotel employee, I can run RevPAR reports (revenue-per-available-room) 8
Improve exception handling 8
... 30
... 50
Sprints
Scrum projects make progress in a series of “sprints”
Analogous to Extreme Programming iterationsTypical duration is 2–4 weeks or a calendar month at mostA constant duration leads to a better rhythmProduct is designed, coded, and tested during the sprint
No changes during a sprint
Plan sprint durations around how long you can commit to keeping change out of the sprint
Change
Burndown
What is ScrumTech*Ed Daily ScrumQ&A (The fun part)
The daily scrum
ParametersDaily10-15 minutesStand-up
Not for problem solvingHelps avoid other unnecessary meetingsGreat way to manage remote teams
Prevents teams from wasting time
Everyone answers 3 Qs
This is not a status meeting
What did you do yesterday?What did you do yesterday?11
What will you do today?What will you do today?22
Is anything in your way?Is anything in your way?33
Sidebar: Scrum and Outsourcing
Daily Scrum best way to keep offshore team on targetIncreases the communicationReduces the red tapeUse IM, Skype
Burndown
What is ScrumTech*Ed Daily ScrumQ&A (The fun part)
Q&A
A Scrum reading listBooks I have read and recomend:
Agile Project Management with Scrum by Ken Schwaber
Agile Software Development with Scrum by Ken Schwaber and Mike Beedle
Scrum and The Enterprise by Ken Schwaber
Agile Estimating and Planning by Mike Cohn
User Stories Applied by Mike CohnOther books:
Agile and Iterative Development: A Manager’s Guide by Craig Larman
Agile Retrospectives by Esther Derby and Diana Larsen
Agile Software Development Ecosystems by Jim Highsmith
www.microsoft.com/teched
Sessions On-Demand & Community
http://microsoft.com/technet
Resources for IT Professionals
http://microsoft.com/msdn
Resources for Developers
www.microsoft.com/learning
Microsoft Certification & Training Resources
Resources
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it
should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.