Xanpan - what do you get if you cross XP and Kanban?

2,183 views
2,010 views

Published on

Xanpan - principles and practices from adding Kanban and flow to XP

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,183
On SlideShare
0
From Embeds
0
Number of Embeds
1,050
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Xanpan - what do you get if you cross XP and Kanban?

  1. 1. allan kelly Twitter: @allankellynet http://www.allankelly.net Xanpan “Zan-pan” The Cigarettes & Colas talk What do you get if you cross Kanban with Extreme Programming? Skills Matter In the Brain September 2013
  2. 2. Allan Kelly • Business Analysis and Leadership, Pullan & Archer 2013 • 97 Things Every Programmer Should Know, Henney, 2010 • Context Encapsulation in Pattern Languages of Program Design, vol#5, 2006  Consulting on software development & strategy  Training for Agile Author – Changing Software Development: Learning to be Agile (2008, Wiley) – Business Patterns for Software Developers (2012, Wiley - ISBN: 978-1119999249) – Xanpan: Reflections on agile (work in progress) https://leanpub.com/xanpan
  3. 3. We don’t need another Methodology
  4. 4. Choose your Cola Kent Beck XP-Cola Ken & Jeff’s Scrum-Cola David Anderson Kanban-Cola Allan Kelly Xanpan-Cola
  5. 5. Where did Xanpan come from? • Experience (Lean+XP) – Blue-White-Red • Kanban • XP • Plus – Seeing others – Reports of other cross-overs • Making sense of what I see XP Kanban & Lean 1 First concept XP Kanban & Lean Product Management 2 XP & Scrum Kanban & Lean Product M anagem ent O therstuff 3
  6. 6. Principles • Iteration routine • Team Centric – Planned & Unplanned work – #NoProjects • Invest in Quality / “Quality is Free” • Dis-economies of Scale • Flow: Emphasize, Level, Span, Constrain • Goodhart’s Law • Constructivism learning • Visualise
  7. 7. Practice 1. XP Technical practices: TDD, CI, etc. 2. Teams can work on more than 1 stream – Flow multiple projects/product to 1 team 3. Break Stories to Tasks – Colour code work – Estimate in Points – Small is better - Think Small! 4. Benchmark against self – Velocity, #NoCommitment
  8. 8. Practices 5. Flow – Use Product “Ownership” (Product Management & Business Analysis) to restrict flow – Apply WIP limits – Absolute Prioritization 6. Planning levels (horizons) 7. Pick’n’Mix 8. Action over words
  9. 9. Practices 9. Fit work to the time – Deadlines are good – Limit WIP 10.Evolutionary change – Small Bangs are OK – but Big Bangs are bad
  10. 10. Some detail….
  11. 11. Iterations & Flow • Iterations bring structure But • Strict iterations break flow – “Story must be finished in sprint” – “Story cannot be bigger than a sprint” – Sprint tail overwhelmed by finished stories – Testers drop standards • Strict iteration – Difficult at first – learn to think small
  12. 12. Iterations & Flow • Stories spanning sprints levels work – Break down stories to tasks – Tasks only counted when completed – When all tasks done, Story done • 3 Strikes and you are out! – Story span 1 Sprint, OK, good – Story spans 2 Sprints, umm… Red Flag – Story spans 3 Sprints, Out! Story too big
  13. 13. Breakdown • In planning meeting • Part – Software Design – Requirements elicitation – Opportunity to reduce scope – Estimation exercise Image from Paul Goyette, Creative Commons License http://commons.wikimedia.org/wiki/File:Wrecking_ball.jpg
  14. 14. Epic StoryStoryStoryStory Discouraged but accepted Blues – Stories • Business facing • Have automatic business value • Deliverable in own right • Deliverable sometime soon • Typically software feature but anything which brings value – documentation, etc. TaskTaskTaskTask Whites – Tasks • Typically developer tasks • No business value alone
  15. 15. Yes, Estimation I’ve come to like Planning Poker but choose your own poison • Estimate White tasks in planning meeting – Ball-park estimate Blues • Estimates in Points – Your currency £ $ € – One currency – Forget hours
  16. 16. Estimation worthwhile? “I can bring a project in to the day”• For scheduling? Perhaps – Some teams report good results – Some teams placebo effect – Long run average accurate enough • Provides Developers with safety valve • Useful input to design process (Forget actuals – retrospective estimates)
  17. 17. Reds Yellows Unplanned work Green Specific to you
  18. 18. Planned & Unplanned work • Work planned in planning meeting • Unplanned work allowed at any time – Tag it, e.g. Yellow card – Retrospective estimation • At end of the iteration count points unplanned – Graph/Track planned v. unplanned – Incorporate into planning velocity
  19. 19. Light Sabre Every team must design their own board
  20. 20. Goodhart’s Law And so do other measurements Any observed statistical regularity will tend to collapse once pressure is placed upon it for control purposes. Professor Charles Goodhart, CBE, FBA Velocity & points break down if abused
  21. 21. Is Xanpan useful? • Maybe – Take it – Use it • Inspiration – Roll your own Image from Ildar Sagdejev under Creative Commons license http://commons.wikimedia.org/wiki/File:2009-02-15_Rolling_a_cigarette.jpg
  22. 22. WIP – Work in Progress http://leanpub.com/xanpan Comments please!
  23. 23. allan kelly www.softwarestrategy.co.uk www.allankelly.net allan@allankelly.net Twitter: @allankellynet (c) Allan Kelly http://www.softwarestrategy.co.uk 25 http://leanpub.com/xanpan Which brand of Cola are you drinking?

×