Being Agile. Plan for change

Transcription

1 Being Agile Plan for change

2

3 When things go wrong This is more complex than we thought. We won t make the deadline.

4 When things go wrong We might deliver on time, but what we re delivering is not fit for purpose!

5 When things go wrong There s a better way, but we ll have to start from scratch...

6 I hate to be the bearer of bad news...

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

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

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

10 Agile

11 Agile Scrum Rapid Application Development Extreme Programming Kanban

12 Principles Adaptive rather than Prescriptive = Don t over-plan

13 Principles Iterative = Deliver early and often and get feedback

14 Principles People over Process = Trust and communication are the most important things in a team

15 Scrum

16 Scrum Small team of peers Regular, short meetings (the scrum ) Project broken into blocks ( sprint ) Each sprint has planning, delivery and retrospective

17 The Scrum Team Small (5-15ish), cross functional Everyone is a peer, no rigid hierarchy Self-organising WHY? This structure promotes free communication - everyone feels respected, taken account of, and can speak their mind

18 Project overview Project broken up into equal-sized sprints: Project planning Sprint 1 Sprint 2 Sprint N Project retrospective Project Deliverable WHY? The end of each sprint is a course correction point - if things are going wrong, the next sprint can be adjusted to address it

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

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

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

22 Project Sprint Sprint Sprint Scrum meetings

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

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

25 The Scrum Meeting As regular as possible As short as possible! Everyone speaks Keep it brief and informative

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

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

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 WHY? It s better to discover any problems or miscommunications early on, rather than at the end of the project when it s too late

29 Sprint retrospective How did we do in this sprint? Problems/insights Course correction?

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?

31 How does this help us?

32 A good scrum team... The Scrum Team is a small group of equals who trust each other

33 A good scrum team... communicates regularly, and it s not a chore The Scrum Meeting

34 A good scrum team... is not restrained by an inflexible plan Sprint Planning

35 A good scrum team... The Scrum Meeting is always checking how things are going Sprint Retrospective

36 A good scrum team... Project Planning Sprint Retrospective knows it can change direction Sprint Planning

37 A good scrum team... learns lessons for next time Project Retrospective

38 A good scrum team... is not afraid of change

39