This is a talk to introduce agile ways of working involves & why its effective. There's an overview of waterfall, agile, Scrum, Kanban boards, retros & impact mapping

1. Agile ways of working
Ryan Hewitt - Lead BA (DWP Digital)
Agile

2. About me
● Currently working on Universal Jobmatch!
● 10 years BA experience (BBC Olympics,
Ernst & Young, Infosys)
● Agile & Waterfall IT projects
● 9 certifications (Agile Product Owner, Scrum
Master, PRINCE2, ITIL)

3. Traditional approach
WATERFALL DEVELOPMENT:
+ Lots of control
+ Know what you’re doing &
what users want
Requirements
Design
Development
Testing
Release

4. Waterfall limitations
LIMITATIONS:
+ Cost of change
+ Value delivered right at the
end
+ Leave testing to the end
Requirements
Design
Development
Testing
Release
Changes
User
feedback
Takes too
long
Skipped

5. Agile
+ It’s a set of values not a process
+ Based on a Manifesto

6. Agile Manifesto
+ Collaboration
+ Rapid development
+ User feedback
+ Embracing change

7. Agile methodologies
By: Haresh Karkar
+ Scrum & Kanban most
popular
+ Scrum process helps
adopt Agile principles

8. Scrum team
+ Small IT team
+ Cross-functional
+ Self-organising
+ Co-located
e.g. BBC Sport app team, Tesco recommendations
team, Digi debt team

9. Scrum backlog
Vision > split into smaller user stories
Prioritised
backlog
Stories at the top:
+ Requirements
+ Detailed designs
+ Get feedback from devs & testers
+ Get them signed-off & ready for
development

10. Scrum
Sprint (2 weeks)
+ Build
+ Test
+ Demo
+ Release
+ Feedback
Next Sprint:
+ More functionality
+ Another
demo/release

11. Scrum summary
Scrum = 2 - 4 weeks
Waterfall = several months/years
+ Lots of feedback
+ Less risky
+ Delivering value ‘early & often’
Requirements
Design
Development
Testing
Release

12. 3 things to use - Kanban board
Display work for next 2
weeks:
+ Make team’s work
visible
+ Daily standup:
● What are you
working on today?
● What did you work
on yesterday?
● Any blockers?
+ Avatars for
ownership/wip limits

13. 3 things to use - Kanban board
+ Decorating a
house
+ Journalist’s at
the BBC
+ BA
Management
team

14. 3 things to use - retrospectives
+ 1 hour meeting
+ Inspect the process and
try to improve:
● What made you
mad?
● What made you
glad?
● What made you
sad?
+ Actions (WHO-WHAT-
WHEN)

15. 3 things to use - retrospectives
+ Allow the team to improve &
optimise
+ Hundreds of ways to have them
(e.g. 7 deadly sins, Pokemon
retro, sailboat retro)
+ http://retrospectivewiki.org/index.
php?title=Agile_Retrospective_Re
source_Wiki

16. 3 things to use - impact mapping
+ Way to brainstorm &
identify deliverables
+ Have a brilliant idea -
quickly identify what to
build
+ Start with a goal

17. Why are we doing this?
Impact mapping - goal

18. ● Whose behaviour do we want to impact?
● Who can produce the desired effect?
● Who can obstruct it?
● Who are the consumers or users of our product?
● Who will be impacted by it?
Impact mapping - actor

19. How should our actors' behaviour change?
How can they help us to achieve the goal?
How can they obstruct or prevent us from succeeding?
Impact mapping - impact

20. What can we do, as an organisation or a delivery team,
to support the required impacts?
Impact mapping - deliverables

21. Impact mapping
+ Deliverables traced
back to the goal
+ Brainstorm lots of
deliverables
+ Collaborative

22. “New billionaire owner of Stockport County FC, he
has set the board of directors the goal of winning the
Premier League by 2025”
Activity
GOAL
ACTOR IMPACT DELIVERABLE
Youth squad
Owner
Increase
funds
Interfere less
Behaviour
you want
Things that will make it
happen?
Take out a loan
Sell their other business?
Things that will make it
happen?
Behaviour
you want

23. Further reading
+ Agile 101: http://agile101.net/2009/09/08/the-difference-between-waterfall-
iterative-waterfall-scrum-and-lean-in-pictures/
+ Kanban board: https://trello.com/b/C4Awm5lK/kanban-board
+ Impact mapping:
+ rthewitt01 & ryan.hewitt1@dwp.gsi.gov.uk