This document introduces Agile project management. It outlines the key principles of the Agile manifesto which focus on individuals, working software, customer collaboration, and responding to change over rigid plans. The document compares the traditional Waterfall process to the iterative Agile process. In Agile, requirements are captured in a product backlog and prioritized in sprints. Teams work in short sprints to deliver working software and get feedback through reviews and retrospectives to continuously improve.

1. Introduction to Agile Written by @dancourse
Agile
Project Management Meeting

2. Introduction to Agile Written by @dancourse
An “amuse bouche”
a la Agile

3. Introduction to Agile Written by @dancourse
Dan Course
@dancourse
d.p.course@warwick.ac.uk
WMG E-learning Developer
Je m’appelle…

4. Introduction to Agile Written by @dancourse
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

5. Introduction to Agile Written by @dancourse
deliver
requirem
ents
plan
implement
Agile process
requirem
ents
plan
implement
deliver &
review
Waterfall process

6. Introduction to Agile Written by @dancourse
Requirements
v4.5.2-copy-final-
finalfinal
Signed off
Waterfall
Locked difficult
and annoying to
change

7. Introduction to Agile Written by @dancourse
Requirements
Sprint 1
Signed off
Agile Built to change every Sprint
Requirements
Please update me
Requirements
Sprint 2
Signed off
Requirements
Sprint 3
Signed off
Requir
Sprint
Signed of

8. Introduction to Agile Written by @dancourse
Agile process

9. Introduction to Agile Written by @dancourse
Product Backlog
• The Wishlist
• Any team member can
update, add, delete in it
• It’s a living document, never
“signed off”
• Not all of this will get done

10. Introduction to Agile Written by @dancourse
Sprint Backlog
• 1 Client representative picks
Highest Business
Value features
• The Team plan it out
• Iron any wrinkles, work out the
risks
• Estimate “time” (story points)
• Based on previous sprints,
only rack up what could be
done

11. Introduction to Agile Written by @dancourse
Sprint
• 2 / 4 weeks
• The team pick which Sprint
Backlog they want to work on
• They move it through the
Sprint Board
• They meet every morning for
5 mins standup
• Talk what’s Done, What’s
next and what’s blocked

12. Introduction to Agile Written by @dancourse
Deliver & Review
• End of sprint we stop
• Done is Done
• Demo what was Done to all team
• Review what was not Done with
all team
• Talk about what to improve
• Client can choose to release to
live or not
• Return un-finished tickets

13. Introduction to Agile Written by @dancourse
Sprint Backlog

14. Introduction to Agile Written by @dancourse
Agile process

15. Introduction to Agile Written by @dancourse
Agile process

16. Introduction to Agile
Want more?
• There’s a lot more to the process
• The chicken and the pig, user stories,
retrospectives, contracts, planning poker,
automation
• Plenty of Youtube videos, “Chet Wrong - Wrong way
to do Agile”
• IBM “Agile for Dummies”
Signposting

17. Introduction to Agile Written by @dancourse
Thanks & Questions
@dancourse

18. Introduction to Agile Written by @dancourse
Graphs

19. Introduction to Agile Written by @dancourse
Planning