You are on page 1of 1

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.0
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 Value
in one
Complex Complicated
Teamwork to find Value Modern Agile

Scrum is here
Big Bang Incremental Delivery Probe Sense
Delivery
Usable Sense Analyze
Cost

1 2 3 Respond Respond
Make People Emergent Good Practices
sk GUI
Ri Awesome
Sellable Feasible DISORDER
Client
Experiment & Deliver Value Chaos Obvious
Learn Rapidly Continuously Server Act Sense
Time
DB schema Sense Categorise
Agile Valuable Make Safety
a Prerequisite
Respond
Novel
Respond
Best Practises
- or “Incremental Development”
Product The Scrum Team Sprint Backlog Sprints
Delivers
Value Backlog The awesome X-functional Team, Prio To do Doing Done
Agile Heartbeat - Cadence

in Incremental
Co-located, with mandate Week 1 Week 2
Goal to make decisions on business-
Deliveries
& user value and tech solutions.
Cost

Daily Standups 15 min


They have the competences Backlog Refinement to find Value
sk needed to build and ship it. Sprint Planning Review
Ri User Story Sprint Goal Retrospective
PO owns Tester Task
UX
the PB and DoD Working Agreement
Time product
vision. Product
Owner
Backend Discovery Delivery Agile Onion by AWA, Simon Powers
Poster by mia.kolmodin@crisp.se Dev
Content Cynefin by Dave Snowden
Free download: blog.crisp.se Frontend Dev
Social Media Modern Agile by Joshua Kerievsky

You might also like