some input on getting more agile, within or without scrum

1. ingvald.skaug @ bouvet.no
http://skaug.no/ingvald
ingvald @ skaug.no
@ingvald

2. It's about value, esp. for:
● Customers/ Users
● Dev.team
● Business
● Management
img: http://www.flickr.com/photos/42429527@N03/5063150948/
http://skaug.no/ingvald/2010/11/what_is_agile/

3. Software Development vs Manufacturing
http://skaug.no/ingvald/2010/02/lean_development_is_not_manufa/

4. Software Development is Knowledge Work
http://en.wikipedia.org/wiki/Knowledge_work_productivity

5. img: http://availagility.co.uk/2008/10/28/kanban-flow-and-cadence/
More background by Kenji Hiranabe: http://www.infoq.com/articles/hiranabe-lean-agile-kanban
Wikipedia: http://en.wikipedia.org/wiki/Toyota_Production_System#Commonly_used_terminology

6. Signal
- Any free capacity?
http://blog.flowkaizen.com/why-physical-card-walls-are-important

7. Kanban In
Software Development
Process
Lightweight tool for evolutionary
change, step-by-step improvement
http://ingvald.posterous.com/what-is-kanban-and-why-should-you-care-about
David Anderson: The Principles of the Kanban Method

8. Feedback
Feedback loops
change human behaviour
http://www.wired.com/magazine/2011/06/ff_feedbackloop/

9. Visualize
=> Shared mental model
=> More engaged stakeholders
=> More effective thinking, collaboration
http://skaug.no/ingvald/2010/12/agile-basics-visualize-more.html
img from Tom Wujec's TED talk

10. Visualize More
img: http://blog.crisp.se/henrikkniberg/images/qconsf-2009-kanban.jpg

11. Kanban Core Concepts
Visualize + Limit Work-In-Progress (WIP)
img: http://blog.crisp.se/henrikkniberg/2009/09/15/1253019240000.html
Some background: http://agilemanagement.net/index.php/Blog/back_to_basics_with_kanban/

12. Jenkins CI
http://jenkins-ci.org/
ill.: Jørn Ola Birkeland, XP2010: From a timebox tangle to a more flexible flow
http://xp2010.org/program?sid=11&o=1

13. ...
Capacity For Systematic
Continuous Improvement
Slack
http://agileconsulting.blogspot.com/2011/07/explaining-why-limiting-wip-is-so.html

14. Slack, Utilization
http://blog.crisp.se/2011/11/15/henrikkniberg/intro-to-kanban-slides-from-leaders-of-agile-webinar

15. Multitasking
ill.: Karl Scotland: Kanban, Flow and Cadence http://availagility.co.uk/2008/10/28/kanban-flow-and-cadence/
http://www.psychologytoday.com/blog/the-power-prime/201103/technology-myth-multitasking
http://arstechnica.com/science/news/2011/08/bottlenecks-in-the-brain-limit-our-ability-to-multitask.ars

16. ...
ill.: Jørn Ola Birkeland, XP2010: From a timebox tangle to a more flexible flow
http://xp2010.org/program?sid=11&o=1

17. ...
Slack, Utilization
http://ingvald.posterous.com/kanban-slack-creates-opportunities-for-improv
http://bookstore.cutter.com/products-page/agile-management/the-viral-growth-of-kanban-in-the-enterprise/ ($50)

18. Estimating
it's human nature to estimate time based on the worst case
scenario, not average time to complete.
As soon as people are penalized for estimating average time
and then not meeting the estimate, they will revert to
estimating the maximum time, and project schedules will
again fill up with padded time estimates.
Mary Poppendieck: Theory of Constraints - It's Okay to be Late
http://www.leanessays.com/2001/03/theory-of-constraints.html

19. Estimating, Timeboxes
Parkinson's Law
- Work expands to fill the time available
Hofstadter's Law
- it always takes longer than you expect
Optimism bias
- systematic tendency to be too optimistic about planned
actions
Planning fallacy
- tendency to underestimate how long to complete task
http://en.wikipedia.org/wiki/Parkinson's_Law
http://en.wikipedia.org/wiki/Student_syndrome
http://en.wikipedia.org/wiki/Hofstadter%27s_law
http://en.wikipedia.org/wiki/Optimism_bias
http://en.wikipedia.org/wiki/Planning_fallacy
How Uncertainty Works http://www.cprime.com/knowledge/articles/uncertainty.html

20. Trouble With Timeboxes
Ten timebox tangles
1. Inestimatable work
2. Unplanned work
3. Unclear work
4. Blocked work
- need input from unavailable stakeholder
5. Parking
- unfinished work, waiting,
due to interruptions, multi-tasking
6. Changed work/ requirements
7. Legacy code
8. Integration
9. Normative estimates (=> tech debt)
10. Specialist (=> Uncertain access)
Jørn Ola Birkeland, Bekk, at XP2010
http://xp2010.org/program?sid=11&o=1

21. Cadence
(Rythm, "heartbeats")
Karl Scotland: Kanban, Flow and Cadence. http://availagility.co.uk/2008/10/28/kanban-flow-and-cadence/
Karl Scotland: Aspects of Kanban. http://www.methodsandtools.com/archive/archive.php?id=104

22. Cadence
(Rythm, "heartbeats")
http://blog.crisp.se/2010/09/01/henrikkniberg/1283373060000

23. More Agile With Scrum
http://www.wired.com/magazine/2011/06/ff_feedbackloop/
http://blog.crisp.se/2010/09/01/henrikkniberg/1283373060000
http://blog.crisp.se/2011/11/15/henrikkniberg/intro-to-kanban-slides-from-leaders-of-agile-webinar
http://xp2010.org/program?sid=11&o=1

24. More Agile Than Scrum
Estimates, "control", prediction
=> See reality, handle variation
Timebox => Flow
Revolution => Evolution
http://agileconsulting.blogspot.com/2011/08/maximizing-benefits-of-kanban-as.html
http://blog.crisp.se/henrikkniberg/2009/12/21/1261410240000.html
http://xp2010.org/program?sid=11&o=1

25. Don't build features that nobody needs right now.
Don't write more specs than you can code.
Don't write more code than you can test.
Don't test more code than you can deploy.
- Corey Ladas
@ingvald
ingvald @ skaug.no
http://skaug.no/ingvald
ingvald.skaug @ bouvet.no