Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
FROM CHAOS TO KANBAN: EPISODE II AGILE NORTH CONFERENCE UCLAN, Preston, UK Prepared by Paul Shannon & Neil Kidd June 2011
BACKGROUND
FROM CHAOS TO KANBAN http://xp2010.codeweavers.net
EPISODE II
THE BACKLOG BOARD IS NOT WORKING
Urgent / Important matrix Iteratively reduced to 4 weeks Pushed back on clients – say no! Clarity restored RESPONSE: BACKL...
IS THE TEAM TOO BIG?
Split the team to multiple streams Separate projects are worked on - where possible   Worked on waste and defects to synch...
ARE WE SUPPORTING OUR CUSTOMERS?
Dedicated support desk Away from the development pods Identify issues fast and feed back directly into the team Dramatical...
A MISSING PRODUCT OWNER?
Increase customer collaboration and manage expectations High availability as the on site customer Enforce demos prior to d...
LOW CODE QUALITY AND DEVELOPMENT BOTTLENECKS
Separated applications into modules Versioned API objects Introduced mocking and collaboration style testing Evolving towa...
RETROSPECTIVES
Nominated a retrospective leader Minutes taken and emailed Management member included Common retrospective format used Act...
OUTCOMES
Focus on customer value - we deliver better quality software, sooner. We’ve found time to innovate and reinvest in improvi...
We’re not afraid to go back – just because it didn't work before doesn't mean it won’t now.   Changes are smaller – tweaks...
http://www.codeweavers.net  
Upcoming SlideShare
Loading in …5
×

From Chaos To Kanban: Episode II

530 views

Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

From Chaos To Kanban: Episode II

  1. 1. FROM CHAOS TO KANBAN: EPISODE II AGILE NORTH CONFERENCE UCLAN, Preston, UK Prepared by Paul Shannon & Neil Kidd June 2011
  2. 2. BACKGROUND
  3. 3. FROM CHAOS TO KANBAN http://xp2010.codeweavers.net
  4. 4. EPISODE II
  5. 5. THE BACKLOG BOARD IS NOT WORKING
  6. 6. Urgent / Important matrix Iteratively reduced to 4 weeks Pushed back on clients – say no! Clarity restored RESPONSE: BACKLOG BE GONE!
  7. 7. IS THE TEAM TOO BIG?
  8. 8. Split the team to multiple streams Separate projects are worked on - where possible   Worked on waste and defects to synchronise streams Used a Scrum-style sprint of 2 weeks to swap pairs for development and support RESPONSE: SPLIT THE TEAM
  9. 9. ARE WE SUPPORTING OUR CUSTOMERS?
  10. 10. Dedicated support desk Away from the development pods Identify issues fast and feed back directly into the team Dramatically improved relationships RESPONSE: IMPROVING SUPPORT
  11. 11. A MISSING PRODUCT OWNER?
  12. 12. Increase customer collaboration and manage expectations High availability as the on site customer Enforce demos prior to deployment Maximise work not done RESPONSE: APPOINT AN OPERATIONS MANAGER
  13. 13. LOW CODE QUALITY AND DEVELOPMENT BOTTLENECKS
  14. 14. Separated applications into modules Versioned API objects Introduced mocking and collaboration style testing Evolving toward BDD RESPONSE: SERVICE ORIENTED ARCHITECTURE
  15. 15. RETROSPECTIVES
  16. 16. Nominated a retrospective leader Minutes taken and emailed Management member included Common retrospective format used Action points placed straight on board RESPONSE: RETROSPECTIVE RESTRUCTURE
  17. 17. OUTCOMES
  18. 18. Focus on customer value - we deliver better quality software, sooner. We’ve found time to innovate and reinvest in improving development Everything needs to be visible, on a card, on a task board
  19. 19. We’re not afraid to go back – just because it didn't work before doesn't mean it won’t now.   Changes are smaller – tweaks rather than changes of direction Occasionally make changes too soon 
  20. 20. http://www.codeweavers.net  

×