1. Agile Project Management
January 2009
An introduction to
SCRUM
Agile Project Management
Mark Crowther – Empirical Pragmatic Tester

2. About this slide pack.
This slide pack provides a brief overview of the SCRUM Agile Project Management Methodology.
Contact Mark Crowther to learn how Testing within a SCRUM driven project can be effectively achieved and how it can be utilised to help make your Agile projects more successful.
Copyright notice
This document is copyright of Mark Crowther - © Mark Crowther The content and trademarks are the property of and copyright of their respective owners. All rights reserved.
You may not, except with the express written permission of Mark Crowther make derivative works or commercially exploit the content or the publication. Nor may you transmit it or store it in any website or other form of electronic retrieval system except as permitted by this copyright notice.
Any redistribution or reproduction of part or all of the content or publication in any form is prohibited other than the following:
you may print or download the complete document or extracts of the content to a local hard disk and you may transmit it to an individual third party for personal and non-commercial use only; but only if you acknowledge Mark Crowther as the source of the publication and provide this copyright notice intact.
For more information contact Mark Crowther.

3. Agile Project Management Methodology
An introduction to SCRUM
SCRUM is an
Agile Project Management Methodology
Characteristics of an ‘Agile’ methodology are:
ADAPTIVE, not PREDICTIVE
LIGHTWEIGHT, not HEAVYWEIGHT
DESCRIPTIVE, not PRESCRIPTIVE

4. An introduction to SCRUM
SCRUM has the following ELEMENTS:
A project team called a SCRUM Team
A Product Backlog of all known Requirements
A Sprint Backlog of requirements being worked on
A period of work referred to as a Sprint
Daily Stand-up Meetings with the SCRUM Team
A Burndown Chart to track progress of the Sprint
An Incremental Delivery at the end of each sprint

5. An introduction to SCRUM
A Model of SCRUM
Sprint
Daily
SCRUM
Incremental Delivery
Burndown Chart
2 - 4 Weeks
Sprint Backlog
Product Backlog

6. An introduction to SCRUM
The SCRUM Team
Is all the people who will COMMITTED to the delivery of the backlogs
One role is ‘SCRUM Master’ who is in practice the PM
Is staffed by PMs, BAs, Developers, Testers, Support – i.e. ALL the typical project staff

7. An introduction to SCRUM
Product Backlog
Contains all the currently known requirements for a product
Is managed by the Product Owner and can change as needed

8. An introduction to SCRUM
Sprint Backlog
Contains the set of prioritised Product Backlog items that are currently being worked on
Are not to be changed during the Sprint

9. An introduction to SCRUM
Sprint
Is a fixed period of development and testing
Results in an incremental delivery of usable product
Usually lasts 2 to 4 weeks

10. An introduction to SCRUM
Daily SCRUM Meeting
Brief ‘Stand-up’ meeting each morning with SCRUM Team only
What value did you add yesterday?
What value will you add today?
What will stop you making progress?

11. An introduction to SCRUM
Burndown Chart
Charts delivery of the Sprint Backlog against Sprint Duration.
Simple, at-a-glance view of progress showing velocity and traction
Easy to keep updated

12. An introduction to SCRUM
Incremental Delivery
Output of the Sprint
Working functionality that can be deployed
Delivered every 2 to 4 weeks, tested and working

13. An introduction to SCRUM
What SCRUM isn’t
It isn’t a Development Methodology, SCRUM doesn’t say how to write or manage the writing of code.
It isn’t suitable for every project and every organisation.
It isn’t a way to drop sound Project Management, Development, Testing Practice, etc.

14. Mark Crowther – Empirical Pragmatic Tester