The document discusses a "rugby" approach to product development where a team works together as a unit to deliver a product increment in short sprints, rather than taking a "relay race" approach where work is passed between specialized roles. It suggests that the rugby approach of cross-functional collaboration may better meet today's need for speed and flexibility.

1. 29-March-2012

2. ―The… ‗relay race‘ approach to product development…may
conflict with the goals of maximum speed and flexibility. Instead a
holistic or ‗rugby‘ approach—where a team tries to go the
distance as a unit, passing the ball back and forth—may better
serve today‘s competitive requirements.‖Hirotaka Takeuchi and Ikujiro Nonaka,
―The New New Product Development Game‖, Harvard Business Review,
January 1986.

3. Focus on delivering the highest business
value in the shortest time
Rapidly and repeatedly inspect actual
working software
Empower teams to self-organize to
determine the best way to deliver the
highest priority features

4. Process and toolsIndividuals and interactions
Comprehensive documentationWorking software
Contract negotiationCustomer collaboration
Following a planResponding to change

5. Cancel
Gift wrap
Return
Sprint
2-4 weeks
Return
Sprint goal
Sprint backlog Potentially shippabl
product increment
Product Backlog
CouponsGift wrap
Coupons
Cancel
24 hours

6.  Scrum projects make progress in a series of
―sprints‖
 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 sprintTeam does a little bit of everything and not all of one thing
No changes during a sprint. ―Terminate‖ a sprint if required

7. •Product owner
•ScrumMaster
•Team
Roles
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Ceremonies
•Product backlog
•Sprint backlog
•Burndown charts
Artifacts

8.  Estimation Techniques
◦ Size vs Time
◦ Planning Poker/T-Shirt
 Continuous Integration
◦ Frequent Check-ins
◦ Frequently tested code
◦ Frequent feedback on health of code
 Test Driven Development
◦ Compensate for lack of upfront design
◦ Automation of acceptance criteria
 Pair programming
◦ Compensate for lack of independent review
Constant Feedback!!!