Agile in a Nutshell

No more We are uncovering better ways Individuals and interactions over processes and tools
HIPPO of developing software by doing Working software over comprehensive documentation
decisions it and helping others do it.
Customer collaboration over contract negotiation
Through this work we have come Responding to change over following a plan
with a spice of Lean UX to value: 2001 - Agile Manifesto

Version 2.5
Why Agile Ways of Working To Be Agile
Waterfall Approach Fail Fast 2
Agile Approach Less visible
- more powerful Move
What we don't Succeed Sooner T-shaped People towards
The unknown Mindset
know we don't learning
know Learn organisation
Development Values Requires
Graphic Design structural
What we know and cultural
Principles
we don't know Interaction Design Measure Build change

50%
Architecture Practices
What we know Can be
in the beginning Business Analysis adopted
in command
Tools and and control
Experts doing all their of knowledge Processes
Waterfall work, then handing over, gets lost More visible
- less powerful
- or “Faith Driven Development”
never looking back.
When problems arise in handoffs
X-functional Team effectively
Cynefin
it is too late to rethink.
solving problems together.
Goal Delivers
in one Big Bang.
Complex Complicated
Teamwork to find Value Modern Agile

Scrum is here
Analyzing and
planning without
Incremental & Probe Sense
testing and Usable Iterative Development Sense Analyze
Cost

an

changing the plan,

Respond Respond
Pl

usually gives late

Make People 1 2 3
Emergent Good Practices
sk surprises, and
Ri deliveries not
Awesome GUI
Sellable Feasible DISORDER
meeting business
goals nor user Experiment & Deliver Value Client Chaos Obvious
All difficult decisions needs. Learn Rapidly Continuously Act Sense
in the beginning. Time Server
Sense Categorise
Make Safety DB schema Respond Respond
Agile Valuable
a Prerequisite Novel Best Practises
- or “Incremental Development”
Product The Scrum Team Scrum Board Sprints
Goal
is usually met earlier Backlog The awesome X-functional Team, Prio To do Doing Done
Agile Heartbeat - Cadence
than planned. Co-located, with mandate Week 1 Week 2
to make decisions on business-
Delivers & user value and tech solutions. Daily Standups 15 min Iterative Design over Experimentation over
Cost

sk
Ri value in incremental They have the competences Big Design up Front Elaborative Planning
Backlog Refinement to find Value
sk deliveries with
Ri needed to build and ship it. Sprint Planning Review
iterative improve-
sk Sprint Backlog
Ri ments when finding Sprint Goal Retrospective
sk out what's needed. PO owns Tester User Story
Ri UX
the PB and Task Working Agreement
Decisions are made
continuously and validated. Time product DoD
Customer Feedback Collaborative work
vision. Product over Intuition over One Hero
Infographic Poster by: Owner
mia.kolmodin@dandypeople.com Discovery Delivery Agile Onion by AWA, Simon Powers
Free download:
Agile Coach Cynefin by Dave Snowden
dandypeople.com/blog Developer Tester
or Scrum Master Modern Agile by Joshua Kerievsky