The document provides an overview of Agile methodology. It defines Agile as an incremental and iterative approach to project development that values individuals, collaboration, adaptability and working software. The key aspects of Agile include short iterations, frequent delivery of working software, adaptive planning, self-organizing teams, daily stand-ups and retrospectives. Benefits of Agile include improved visibility, productivity and ability to manage changing priorities. The document recommends starting with Agile by identifying issues to solve, creating a visual board and improving through small steps and continuous learning.

1. Hello!
I’m Andy Birds
@AndyBirds
Google Deep Dream Generator is a platform where you can transform photos using a powerful AI algorithms
http://deepdreamgenerator.com/

2. Agile
Overview

3. Goal
Give you a overview and basic
understanding of what Agile is

4. The Penny Game

5. What is Agile?

6. Project Success Rate
6Source: Standish Group 2015 Chaos Report
SUCCESSFUL
29%
CHALLENGED
52%
FAILED
19%

7. Source: https://www.infoq.com/articles/standish-chaos-2015

8. Traditional methodologies are
most successful when:
• Requirements are stable
• External environment is stable
• Technology is well known and mature
• ‘We have done this earlier’
• ‘We are not taking on anything new or unknown’
• Doesn't involve changes to people or processes

9. Today, projects
with these
characteristics
are few and far
between

10. Origins of Agile
• Rigidity of traditional methods, thereby failing to accommodate change
• High risk in the “big bang” approach
• The myth that a well defined process is more valuable than the people
who use it

11. Agile Values
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.

13. Agile Principles
1. Customer satisfaction
2. Harnessing change
3. Faster development timelines
4. Collaboration
5. Building projects around motivated individuals
6. Face-to-face communication
7. Working software as the key benchmark for success
8. Sustainable development
9. Technical excellence
10. Simplicity
11. Self-organizing teams
12. Self-reflecting teams
Source: http://agilemanifesto.org/principles.html

14. What is the difference between Agile and Scrum?
Agile Scrum

15. Agile
Scrum
Kanban
LeSS
DSDM
DAD
SAFe
XPFDD
CrystalNexus
Lean
Scrumban
AUPAPM
PRINCE2
Agile
Agile
Modeling

16. Project Lifecycles
Waterfall
(Sequential)
Agile - Scrum
(Incremental)
`
Lean Start-up
(Adaptive) `
Agile – Kanban
(Iterative)
`
Build
Release
Feedback

17. Credit: Jeff Patton
AGILE IS INCREMENTAL

18. Credit: Jeff Patton
AND INTERATIVE

19. BREAK THE WHOLE
DOWN AND PRIORITISE

20. WAYS OF WORKING
Potentially
Shippable
Increment
Epic
User Story
Epic
User Story
Epic
User Story
Product Backlog
Product
Owner
Retrospective
Inspect
&
Adapt
Demo
Board
Daily Stand-up
Planning
Analyse
Design
Build
Deploy
Test &
Review
Delivery
Delivery
Manager
Squad
Showcase
Story Kick-off
Desk Check
Inception
Priority
Discovery

21. SHORT ITERATIONS

22. AGILE TRIANGLE
Value
(Releasable Product
Understood or perceived value)
Quality
(Reliable, Maintainable, Adaptable
Product)
Constraints
Scope
Time £

23. Focus on delivering value
up-front in small incremental
steps, which reduces risk
AgileWaterfall
Time
Key
Value delivered
Risk
Time

24. Fast
Feedback
Loops

25. Project kick-off(Inception)
Release
planning
Iteration
planning
Daily
stand-up
Review /
demo
Retrospective
User
Stories
Task cards
Kanban board
Burn
chart
Planningpoker
Pairing
Unit tests
Continuous
Integration /
Delivery
Refining thebacklog
Definition of
Done
Hypothesis
Driven
Development
Ceremonies Techniques
Practices
Co-location
TDD (Test Driven
Development)
Showcase

26. Mindset

27. Agility is an
attitude, not
just a skillset

28. Mindset
Manifesto
Principles
Methodologies
Agile is a mindset
described by 4 Values,
defined by 12 Principles
and delivered using various methods
and an unlimited number tools and techniques.
Practices

29. Ability to manage changing priorities (87%)
Increased team productivity (85%)
Improved project visibility (84%)
Source: Version One 10th Annual State of Agile Survey 2016
Top 3 Benefits

30. Where to start?
Identify the issue you want to solve
Create a visual representation of the work (Kanban)
Improve in small steps
Use retrospectives as a platform to continuously improve
Process is not in stone. Process serves you. You don’t serve process.
3

31. Makes it visual
Information Radiators – Kanban

32. Kanban

33. Daily Stand-up
Time-boxed to 15mins
Same time and place each day
Each team member updates the team with:
• What have I done since the last stand-up?
• What will I do before the next stand-up?
• What blockers are preventing me from continuing?

34. Retrospectives
What went well?
What didn’t go so well?
Actions

35. Start tomorrow.
Trial & error.
Inspect & adapt.
Use a visual board, Retrospectives & Daily Stand-ups

36. Suggested reading
1) Scrum: The Art of Doing Twice the Work in Half the Time Hardcover by Jeff Sutherland
2) The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win by Gene Kim
3) The Lean Startup, Eric Ries
4) Agile Software Development Ecosystems by Jim Highsmith
5) Lean Enterprise: How High Performance Organizations Innovate at Scale by Jez Humble and
Joanne Molesky
6) Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment
Automation by Jez Humble and David Farley

37. Online content
ThoughtWorks Insights – http://www.thoughtworks.com/insights
Scrum Alliance - https://www.scrumalliance.org/
Martin Fowler - http://martinfowler.com/
Mike Cohn - https://www.mountaingoatsoftware.com/
Jeff Patton - http://www.agileproductdesign.com/index.html
Jeff Sutherland - http://www.scruminc.com/category/blog/
Ron Jeffries - http://xprogramming.com/index.php
Ken Schwaber - http://kenschwaber.wordpress.com/
Roman Pichler - http://www.romanpichler.com/blog/
Spotify Engineering Culture Video:
Part 1 - https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/
Part 2 - https://labs.spotify.com/2014/09/20/spotify-engineering-culture-part-2/
Audible - Scrum: The Art of Doing Twice the Work in Half the Time Hardcover
by Jeff Sutherland

38. Thanks!Any questions or comments?
You can find me at:
abirds@thoughtworks.com
@AndyBirds