SLIDE 1
Being Agile Plan for change When things go wrong This is more - - PowerPoint PPT Presentation
Being Agile Plan for change When things go wrong This is more - - PowerPoint PPT Presentation
Being Agile Plan for change When things go wrong This is more complex than we thought. We wont make the deadline. When things go wrong We might deliver on time, but what were delivering is not fit for purpose! When things
SLIDE 2
SLIDE 3
When things go wrong
“This is more complex than we thought. We won’t make the deadline.”
SLIDE 4
When things go wrong
“We might deliver on time, but what we’re delivering is not fit for purpose!”
SLIDE 5
When things go wrong
“There’s a better way, but we’ll have to start from scratch...”
SLIDE 6
I hate to be the bearer of bad news...
SLIDE 7
Why are we doing nothing to fix it?
We don’t feel that we can change anything…. ...the requirements/timelines are “set in stone”
SLIDE 8
Why are we doing nothing to fix it?
We’d have to scrap everything and start again… ...and that’s going to cause panic
SLIDE 9
Why are we doing nothing to fix it?
Everything seems to be going great… ...we haven’t talked to the people who know otherwise
SLIDE 10
Agile
SLIDE 11
Agile
Scrum Rapid Application Development Extreme Programming Kanban
SLIDE 12
Principles
Adaptive rather than Prescriptive
= Don’t over-plan
SLIDE 13
Principles
Iterative
= Deliver “early and often” and get feedback
SLIDE 14
Principles
People over Process
= Trust and communication are the most important things in a team
SLIDE 15
Scrum
SLIDE 16
Scrum
Small team of peers Regular, short meetings (the “scrum”) Project broken into blocks (“sprint”) Each sprint has planning, delivery and retrospective
SLIDE 17
The Scrum Team
Small (5-15ish), cross functional Everyone is a peer, no rigid hierarchy Self-organising
This structure promotes free communication - everyone feels respected, taken account of, and can speak their mind
WHY?
SLIDE 18
Project overview
Project planning Sprint 1 Sprint 2 Sprint N Project retrospective
Project Deliverable
The end of each sprint is a “course correction point” - if things are going wrong, the next sprint can be adjusted to address it
WHY? Project broken up into equal-sized sprints:
SLIDE 19
Project Planning
Break down work into tasks, not take longer than a sprint The team estimates the size of each task Tasks are assigned a priority
SLIDE 20
The Backlog
A list of the tasks remaining in the project, with an associated priority The team will work on the highest priority item in the backlog at any given time Items may be reprioritised, added, removed during the project
SLIDE 21
The Sprint
Usually a few weeks long (1-4) Assign a “sprint goal” to be met at the end of the sprint Regular scrum meetings occur during the sprint Looks familiar….
Sprint planning Scrum meeting 1 Scrum meeting 2 Scrum meeting N Sprint retrospective
Sprint Deliverable
SLIDE 22
Project Sprint Sprint Sprint
Scrum meetings
SLIDE 23
Sprint Planning
Choose the work that will be done this sprint Pick highest priority tasks from the backlog Reprioritise, estimate, or re-estimate as required
SLIDE 24
How many tasks fit into a sprint?
Estimating process will give a size to each task First sprint: informed guess at how much the team can get through Adjust this - the “capacity” - as sprints continue Unfinished tasks can be moved into the next sprint
SLIDE 25
The Scrum Meeting
As regular as possible As short as possible! Everyone speaks Keep it brief and informative
SLIDE 26
Scrum meeting: individual update
What I achieved since last meeting What I plan to achieve for the next meeting Anything that’s blocking me from completing my task Important: Everyone should have their say. Longer discussions should be moved into a meeting dedicated to that topic
SLIDE 27
Project planning Sprint 1 Sprint 2 Sprint N Project retrospective
Project Deliverable
Sprint planning Scrum meeting 1 Scrum meeting 2 Scrum meeting N Sprint retrospective
Sprint Deliverable
SLIDE 28
Sprint deliverable
Deliver or present work to someone who is not in your team “Work” can be partially complete, or just a discussion Use the feedback to adjust the backlog, if necessary
It’s better to discover any problems or miscommunications early on, rather than at the end of the project when it’s too late
WHY?
SLIDE 29
Sprint retrospective
How did we do in this sprint? Problems/insights Course correction?
SLIDE 30
Project retrospective
How did we do overall? How well did our plans and estimates match up with what happened? How well did our process work? What can we learn for next time?
SLIDE 31
How does this help us?
SLIDE 32
A good scrum team...
… is a small group of equals who trust each other
The Scrum Team
SLIDE 33
A good scrum team...
… communicates regularly, and it’s not a chore
The Scrum Meeting
SLIDE 34
A good scrum team...
… is not restrained by an inflexible plan
Sprint Planning
SLIDE 35
A good scrum team...
… is always checking how things are going
Sprint Retrospective The Scrum Meeting
SLIDE 36
A good scrum team...
… knows it can change direction
Sprint Planning Sprint Retrospective Project Planning
SLIDE 37
A good scrum team...
… learns lessons for next time
Project Retrospective
SLIDE 38
A good scrum team...
… is not afraid of change
SLIDE 39