Transcript Resources www.microsoft.com/teched www.microsoft.com/learning Sessions On-Demand & Community Microsoft Certification & Training Resources http://microsoft.com/technet http://microsoft.com/msdn Resources for IT Professionals Resources for Developers www.microsoft.com/learning Microsoft Certification and Training Resources.

Resources
www.microsoft.com/teched
www.microsoft.com/learning
Sessions On-Demand & Community
Microsoft Certification & Training Resources
http://microsoft.com/technet
http://microsoft.com/msdn
Resources for IT Professionals
Resources for Developers
www.microsoft.com/learning
Microsoft Certification and Training Resources
Daily Scrum
What did I do yesterday?
Attend Lakers Game
What will you do today?
Find a Lakers Girl
What do I need from the scrumaster?
Laker Girl’s phone number
Joel Semeniuk
Stephen Forte
DPR206
Session.About();
Short Intro to Scrum
Assume you have at least heard of Scrum or Agile
Tons of Q&A
From s in dat.Speaker select s.Bio;
Chief Strategy Officer of Telerik
Certified Scrum Master (slides based on cert. class)
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
Author of 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
Burndown
What is Scrum
Tech·Ed Daily Scrum
Q&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
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 like
Scrum
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 admin
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 results
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 interferences
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 sprints
Customer/User Education
Low Bandwidth Business Users
Video conf
Evening sessions
Joel’s Insurance App
It is PET insurance
Not REAL insurance
He is Canadian you know…
Product Backlog
This is the
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
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
As a hotel employee, I can run RevPAR
reports (revenue-per-available-room)
3
8
Improve exception handling
8
...
30
...
50
Fill out your eval or we will send him
after you
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 sprint
No Changes During a Sprint
Change
Plan sprint durations around how long you can
commit to keeping change out of the sprint
Burndown
What is Scrum
Tech·Ed Daily Scrum
Q&A (the fun part)
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 time
Everyone Answers 3 Qs
What did you do yesterday?
What will you do today?
Is anything in your way?
This is not a status meeting
1
2
3
Sidebar: Scrum and Outsourcing
Daily Scrum best way to keep offshore team
on target
Increases the communication
Reduces the red tape
Use IM, Skype
Burndown
What is Scrum
Tech·Ed Daily Scrum
Q&A (the fun part)
A Scrum Reading List
Books I have read and recommend:
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 Cohn
Scaling Agile
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 Highsmith
Track Resources
Visit the DPR TLC for a chance to win a copy of
Visual Studio Team Suite. Daily drawing occurs
every day in the TLC at 4:15pm. Stop by for a
raffle ticket
http://www.microsoft.com/visualstudio
http://www.microsoft.com/visualstudio/enus/products/teamsystem/default.mspx
Please visit us in the TLC blue area
Complete an
evaluation on
CommNet and
enter to win!
© 2009 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.