This document provides an introduction to Agile project management and Scrum methodology. It defines Agile management as an incremental and flexible method for managing development projects. The document discusses common misconceptions about Agile and outlines the Agile Manifesto. It then focuses on Scrum as one Agile methodology, describing the roles of Product Owner, Scrum Master, and Development Team, as well as key Scrum practices like sprints, daily stand-ups, retrospectives, and burndown charts. Resources for learning more about Scrum and Agile are provided.

1. AGILE PROJECT
MANAGEMENT
an introduc+on to Scrum and other
“Agile” methodologies

2. 2
WHAT ON EARTH IS
AGILE MANAGEMENT?

3. 3

4. 4
“AGILE MANAGEMENT IS AN
INCREMENTAL METHOD OF MANAGING
DEVELOPMENT PROJECTS IN A HIGHLY
FLEXIBLE AND INTERACTIVE MANNER”

5. MISCONCEPTIONS
“An excuse to throw planning and
documentation out the window…”
“Agile is a silver bullet for all
development project challenges.”
“Once an organisation adopts Agile practices,
they must use these for all projects
undertaken.”
“Agile development is faster and
cheaper than Waterfall.”

6. - THE AGILE MANIFESTO -
Individuals and interactions over Processes and tools
Working software over Comprehensive documentation
Customer collaboration over Contract negotiation
Responding to change over Following a plan

7. SO, WHAT IS THIS SCRUM THING
7
AND HOW DOES IT FIT IN?

8. Scrum
Kanban
Extreme Programming
Feature Driven Development
Lean Software Development

9. - Michael James (Scrum Reference Card)

11. - Michael James (Scrum Reference Card)

13. 13
Burndown Chart

14. 14
Product Owner
๏ Ensures the team delivers value to the business
๏ Writes and prioritises (with guidance from the team)
backlog items, usually in the form of user stories.
๏ The Product Owner champions the project. They may be
an internal member of the team, or a member of the
client’s team.

15. 15
Scrum Master
๏ A facilitator role, accountable for removing/solving any
issues that prevent the team from delivering the product.
๏ Ensures the Scrum process is used as intended by
chairing Scrum meeting.
๏ Has no managerial authority over the Scrum team.

16. 16
Development Team
๏ Responsible for delivering project increments at the end
of each sprint.
๏ Negotiates Sprint commitments with Product Owner &
Scrum Master.
๏ Most successful with long-term membership.

17. 17
Retrospectives
๏ Gives the team an opportunity to improve.
๏ Undertaken in a trusting, blame-free environment.
๏ The group learn as a team, and carry their experience on
to the next project.

18. 18
Resources
๏ http://scrumreferencecard.com/
๏ http://www.trello.com/
๏ http://www.plans-for-retrospectives.com/
๏ https://www.atlassian.com/software/jira

19. 19
QUESTIONS?