Here are the slides from my presentation at Agile Copenhagen on June 26. The theme for the presentation was Agile Resilience, and how it can be incorporated as a natural part of how the team collaborates.

1. Allan Rennebo Jepsen
Agile Maturity Coach
About
Active agile community member

2. We bmuitg hcat nb ew beo htahn gdoleo dre aanlidty f?ast…

3. Collaborate
- The team needs you!
U.S. NAVY SEAL TEAM

4. The Agile Manifesto
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 the value challenge the items is to on find the the left balance
more

5. REPEAT
TO
SUCCEED
Continuous X

6. The foundation
Vision
(Epics)
User Stories
Tasks
Code
Everyone must ”live
the vision”
The User Stories
must be clear to
everyone
User Stories must
be matured enough
to align
expectations
We need to support
linking of
knowledge
Always support
transparancy

7. Continuous practices
Design &
Implementation
Peer Review Quality Assurance Documentation
Integration &
Deployment
Release
Planning &
Commitment
Understanding
C…o anldl asob muochrmaotree
- The team needs you!

8. Peer Review
If you solve it together, you review without effort

9. Continuous practices
Peer Review Quality Assurance Documentation Release
C…o anldl asob muochrmaotree
- The team needs you!

10. The implementation process
Developers picks a task
Developers explains solution to QA
QA validates and provide feedback
Developers and QA agrees
Developers implements while QA prepares
QA verifies the implementation
QA updates the board

11. The foundation
Vision
 How to support integrated knowledge
Epics
User Stories
Tasks
Code
Everyone must ”live
the vision”
The Epics must be
clear to everyone
User Stories must
be matured enough
to align
expectations
Realization
Always support
transparancy and
collaboration
Test cases
Automated testing
UAT
Peer Review
We need to support
linking of
knowledge

12. Continuous practices
Peer Review Quality Assurance Documentation Release
C…o anldl asob muochrmaotree
- The team needs you!

13. How to support integrated knowledge
Vision
Epics
User Stories
Tasks
Code
Everyone must ”live
the vision”
The Epics must be
clear to everyone
User Stories must
be matured enough
to align
expectations
Realization
Test cases
We need to support
linking of
knowledge
Always support
transparancy and
collaboration
Automated testing
UAT
Peer Review

14. The implementation process
Developers picks a task
Developers explains solution to QA
QA validates and provide feedback
Developers and QA agrees
Developers implements while QA prepares
QA verifies the implementation
QA updates the board
Documentation

15. The meaning of Documentation
If you have already done everything else (User Stories tasks, etc.), documentation can be easy
Just draw what you think,
take a picture and attach it
to the task

16. Continuous practices
Peer Review Quality Assurance Documentation Release
C…o anldl asob muochrmaotree
- The team needs you!

17. Is this easy to take over?
(If your purpose is to build houses…)
You can either have 10 houses like this, or 2 houses completely done.

18. Support clear interfaces
If you build a module with clear interfaces,
others don’t have to understand all the details
They can just use it.

19. How to finalize a release
Have we produced an
actual release with clear
interfaces?
What is the current quality and do
we have any technical debt which
Prepare the presentation
and show it to eachother Collaborate
needs to be handled in next
iteration?
How much of the agreed
scope has been
completed?
- The team needs you!

20. The bottom line…
Knowledge Transfer We arQuealitynow reDoscumilenitaetionnt Modulized

21. Go Do it!
The future belongs to the few of us still willing to get our hands dirty…