Daily Scrum Stephen Forte Chief Strategy Officer Telerik Session Code WUX310 SessionAbout Short Intro to Scrum Assume you have at least heard of Scrum or Agile Tons of QampA SpeakerBioToString ID: 502406
Download Presentation The PPT/PDF document "Tech*ED" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1Slide2
Tech*ED Daily Scrum
Stephen Forte
Chief Strategy Officer
Telerik
Session Code: WUX310 Slide3
Session.About
();
Short Intro to Scrum
Assume you have at least heard of Scrum or Agile
Tons of Q&ASlide4
Speaker.Bio.ToString
();
Chief Strategy Officer of Telerik
Certified Scrum Master
Active in the Community:
International Conference Speaker for 12+ Years
RD, MVP and INETA Speaker
Co-moderator & founder of NYC .NET
Developers Group
http://www.nycdotnetdev.com
Wrote a few books: SQL Server 2008 Developers Guide (MS Press)
MBA from the City University of New York
Past:
CTO and co-Founder of
Corzen
, Inc. (TXV: WAN)
CTO of
Zagat
Survey Slide5Slide6
Burndown
What is Scrum
Tech*Ed Daily Scrum
Q&A (The fun part)Slide7
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?Slide8
Characteristics
Self-organizing teams
Product 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 likeSlide9
ScrumSlide10
Sidebar: Scrum in the Real World
Corzen’s Data Engine Development in 2006
Sprint 1: infrastructure
Sprint 2: new engine (XML/reflection)
Business value: Enabled multiple sites
Sprint 3: vertical independent engine
Business value: one data engine for all spidering
Sprint 4: distributed processing (Seti@Home
style)
Business value: unlimited spidering via cheap
VPSes
Sprint 5: management (WCF)
Business value: thousands of spiders, 1 adminSlide11
Product owner
Define the features of the product
Decide on release date and content
Be 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 resultsSlide12
The ScrumMaster
Represents management to the project
Responsible for enacting Scrum values and practices
Removes impediments
Ensure that the team is fully functional and productive
Enable close cooperation across all roles and functions
Shield the team from external interferencesSlide13
The team
Typically 4-9 people
Cross-functional:
Programmers, testers, user experience designers, etc.
Members should be full-time
May be exceptions (DBA)
Teams are self-organizing
Ideally, no titles but rarely a possibility
Membership should change only between sprintsSlide14
Product backlog
The requirements
A list of all desired work on the project
Ideally expressed such that each item has value to the users or customers of the product
Prioritized by the product owner
Reprioritized at the start of each sprint
This is the product backlogSlide15
A sample product backlog
Backlog item
Estimate
Allow 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
...
50Slide16
Sprints
Scrum projects make progress in a series of “sprints”
Analogous to Extreme Programming iterations
Typical duration is 2–4 weeks or a calendar month at most
A constant duration leads to a better rhythm
Product is designed, coded, and tested during the sprintSlide17
No changes during a sprint
Plan sprint durations around how long you can commit to keeping change out of the sprint
ChangeSlide18
Burndown
What is Scrum
Tech*Ed Daily Scrum
Q&A (The fun part)Slide19
The daily scrum
Parameters
Daily
10-15 minutes
Stand-up
Not for problem solving
Helps avoid other unnecessary meetings
Great way to manage remote teams
Prevents teams from wasting timeSlide20
Everyone answers 3 Qs
This is not a status meeting
What did you do yesterday?
1
What will you do today?
2
Is anything in your way?
3Slide21
Sidebar: Scrum and Outsourcing
Daily Scrum best way to keep offshore team on target
Increases the communication
Reduces the red tape
Use IM, SkypeSlide22
Burndown
What is Scrum
Tech*Ed Daily Scrum
Q&A (The fun part)Slide23
Q&ASlide24
A Scrum reading list
Books 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 SchwaberAgile Estimating and Planning by Mike CohnUser Stories Applied by Mike Cohn
Other 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
HighsmithSlide25
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
Required Slide
Speakers,
TechEd 2009 is not producing
a DVD. Please announce that
attendees can
access session
recordings at TechEd Online. Slide26
©
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.