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.
@IndigoCube
/company/indigocube.co.za
LET’S GET SOCIAL!
A Collaborative Approach
to Quality in the
Agile Enterprise
Jaco Viljoen | IndigoCube | jaco@indigocube.co.za
www.indigocu...
JACO VILJOEN
Principal Consultant
• Introduction
• Challenges
• Vision/Solution
• Implementation
 Obstacles faced with implementation
 Outcome
 Lessons l...
• Systems Thinking 101
 The structure of a system determines the behaviour
 Pervasive problems are caused by many intera...
LEVEL DELIVERY
FOCUS
CHARACTERISTICS RESULT
5: Optimizing Hypothesis-driven
delivery
Teams focus on
optimizing cycle time ...
Value
4 :
Documents Working Software System
4 444 :
Va
4
Documents
• Enterprise Challenge #1: Collaboration
• Enterprise Challenge #2: Quality
Challenges
Enterprise Challenge #1: Collaboration
- Waterfall -
Enterprise Challenge #1: Collaboration
- Water-Scrum-Fall -
Enterprise Challenge #1: Collaboration
- Water-Scrum-Fall -
Enterprise Challenge #1: Collaboration
- Water-Scrum-Fall -
Enterprise Challenge #1: Collaboration
- Continuous Delivery -
Enterprise Challenge #1: Collaboration
- Continuous Delivery -
Enterprise Challenge #1: Collaboration
- Continuous Delivery -
Enterprise Challenge #1: Collaboration
- Continuous Delivery -
Enterprise Challenge #2: Quality
- Waterfall -
Product v2.0
Quality
Time
Product v1.0 Acceptable level of
quality in Produ...
Enterprise Challenge #2: Quality
- Waterfall -
Product v2.0
Quality
Time
Acceptable level of
quality in Production
Too man...
Enterprise Challenge #2: Quality
- Water-Scrum-Fall -
Quality
Time
Acceptable level of
quality in Production
Technical
Deb...
TimeTechnicalDebt
Quality
Time
Acceptable level of
quality in ProductionProduct
v3.0
Product v3.0
Technical
Debt
Technical...
Enterprise Challenge #2: Quality
- Continuous Delivery -
Quality
Time
Product v1.0
Acceptable level of
quality in Producti...
Enterprise Challenge #2: Quality
- Continuous Delivery -
Quality
Time
Product v1.0
Acceptable level of
quality in Producti...
Enterprise Challenge #2: Quality
- Continuous Delivery -
Quality
Time
Product v1.0
Acceptable level of
quality in Producti...
Vision/Solution
• Shift user acceptance testing left
• Prevent defects
• Collaborate around quality
• Automate acceptance and regression t...
Acceptance Test Driven Development
for the Whole Team
LEVEL DELIVERY
FOCUS
5: Optimizing Hypothesis-driven
delivery
4:
Quantitatively
Managed
Release on demand
3: Defined Regul...
Continuous Delivery Pipeline43
Continuous Delivery Pipeline
• From “Water-Scrum-Fall” to “Continuous Delivery”
• Strategy to minimise impact of necessary change
Implementation
LEVEL DELIVERY
FOCUS
CHARACTERISTICS RESULT
5: Optimizing Hypothesis-driven
delivery
Teams focus on
optimizing cycle time ...
Continuous Delivery Process
Continuous Delivery Process
Shift user acceptance testing left and automate it
Continuous Delivery Process
Vision of Changes Needed (Was there)
Vision of Changes Needed (Done)
Vision of Changes Needed (To do)
• Whole team approach
• Acceptance test driven development
• Continuous delivery pipeline
Summary
A collaborative approach to the quality in the agile enterprise by Jaco Viljoen
A collaborative approach to the quality in the agile enterprise by Jaco Viljoen
A collaborative approach to the quality in the agile enterprise by Jaco Viljoen
A collaborative approach to the quality in the agile enterprise by Jaco Viljoen
A collaborative approach to the quality in the agile enterprise by Jaco Viljoen
Upcoming SlideShare
Loading in …5
×

A collaborative approach to the quality in the agile enterprise by Jaco Viljoen

1,052 views

Published on

A collaborative approach to the quality in the agile enterprise by Jaco Viljoen from IndigoCube

Published in: Technology
  • Be the first to comment

A collaborative approach to the quality in the agile enterprise by Jaco Viljoen

  1. 1. @IndigoCube /company/indigocube.co.za LET’S GET SOCIAL!
  2. 2. A Collaborative Approach to Quality in the Agile Enterprise Jaco Viljoen | IndigoCube | jaco@indigocube.co.za www.indigocube.co.za | info@indigocube.co.za
  3. 3. JACO VILJOEN Principal Consultant
  4. 4. • Introduction • Challenges • Vision/Solution • Implementation  Obstacles faced with implementation  Outcome  Lessons learned • Summary Agenda
  5. 5. • Systems Thinking 101  The structure of a system determines the behaviour  Pervasive problems are caused by many interacting agents leading to emergent properties  Nobody is to blame • 3 Types of Systems in Agile Enterprises  Waterfall  Water-Scrum-Fall  Continuous Delivery Introduction
  6. 6. LEVEL DELIVERY FOCUS CHARACTERISTICS RESULT 5: Optimizing Hypothesis-driven delivery Teams focus on optimizing cycle time to learn from customers Continuous deployment capability enables business innovation / experimentation 4: Quantitatively Managed Release on demand Delivery teams prioritize keeping code trunk deployable over doing new work Release on demand: Software is always in a releasable state. Relea time box is well defined and equa to, or less than, business need 3: Defined Regular releases over a defined period with interim milestone builds Teams build quality into release process Regular release cadence: Release time box is well defined, but duration from idea inception to production release is greater than business need 2: Managed Time-boxed releases (the team sets a release date and manages to it) There is an adaptive delivery process Planned release: Release time box well defined, but duration from id inception to production release is greater than business need 1: Initial A few smart people performing heroics There is an ad hoc release delivery process Ad hoc deployments
  7. 7. Value 4 : Documents Working Software System 4 444 : Va 4 Documents
  8. 8. • Enterprise Challenge #1: Collaboration • Enterprise Challenge #2: Quality Challenges
  9. 9. Enterprise Challenge #1: Collaboration - Waterfall -
  10. 10. Enterprise Challenge #1: Collaboration - Water-Scrum-Fall -
  11. 11. Enterprise Challenge #1: Collaboration - Water-Scrum-Fall -
  12. 12. Enterprise Challenge #1: Collaboration - Water-Scrum-Fall -
  13. 13. Enterprise Challenge #1: Collaboration - Continuous Delivery -
  14. 14. Enterprise Challenge #1: Collaboration - Continuous Delivery -
  15. 15. Enterprise Challenge #1: Collaboration - Continuous Delivery -
  16. 16. Enterprise Challenge #1: Collaboration - Continuous Delivery -
  17. 17. Enterprise Challenge #2: Quality - Waterfall - Product v2.0 Quality Time Product v1.0 Acceptable level of quality in Production DEV makes changes… Bug fixing… Testing… Regression... Underlying assumption: • Capacity matches demand • No surprises
  18. 18. Enterprise Challenge #2: Quality - Waterfall - Product v2.0 Quality Time Acceptable level of quality in Production Too many changes to fix up in time provided Product v2.0 Product v1.0 Not enough time for fixing the quality Technical Debt
  19. 19. Enterprise Challenge #2: Quality - Water-Scrum-Fall - Quality Time Acceptable level of quality in Production Technical Debt Product v2.0Product v1.0 Product v2.0 Traditional practices fail if timeline is too short 50% Getting all testing done in the current iteration/sprint 37% Adopting test-driven development (TDD) approaches The most difficult challenges when adopting agile testing approaches - Agile Testing Survey 2012
  20. 20. TimeTechnicalDebt Quality Time Acceptable level of quality in ProductionProduct v3.0 Product v3.0 Technical Debt Technical Debt grows… Product v2.0 Product v1.0 Enterprise Challenge #2: Quality - Water-Scrum-Fall -
  21. 21. Enterprise Challenge #2: Quality - Continuous Delivery - Quality Time Product v1.0 Acceptable level of quality in Production Team collaborate around changes… Product v2.0 Team collaborate around changes… Team collaborate around changes… Team collaborate around changes…
  22. 22. Enterprise Challenge #2: Quality - Continuous Delivery - Quality Time Product v1.0 Acceptable level of quality in Production Team collaborate around changes… Team collaborate around changes… Team collaborate around changes… Team collaborate around changes… Product v2.0
  23. 23. Enterprise Challenge #2: Quality - Continuous Delivery - Quality Time Product v1.0 Acceptable level of quality in Production Team collaborate around changes… Product v2.0 Team collaborate around changes… Team collaborate around changes… Product v2.0
  24. 24. Vision/Solution
  25. 25. • Shift user acceptance testing left • Prevent defects • Collaborate around quality • Automate acceptance and regression testing • Build a parallel “system that tests the system” Vision/Solution
  26. 26. Acceptance Test Driven Development for the Whole Team
  27. 27. LEVEL DELIVERY FOCUS 5: Optimizing Hypothesis-driven delivery 4: Quantitatively Managed Release on demand 3: Defined Regular releases over a defined period with interim milestone builds 2: Managed Time-boxed releases (the team sets a release date and manages to it) 1: Initial A few smart people performing heroics D D DB B BT T T D D DB B BT T T D D DB B BT T T Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprin Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprin Define Define Define Build Build Build Test Test Test Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprin Define Build Test BuildDefine Test Define Build Tes Define Build Test BuildDefine Test
  28. 28. Continuous Delivery Pipeline43
  29. 29. Continuous Delivery Pipeline
  30. 30. • From “Water-Scrum-Fall” to “Continuous Delivery” • Strategy to minimise impact of necessary change Implementation
  31. 31. LEVEL DELIVERY FOCUS CHARACTERISTICS RESULT 5: Optimizing Hypothesis-driven delivery Teams focus on optimizing cycle time to learn from customers Continuous deployment capability enables business innovation / experimentation 4: Quantitatively Managed Release on demand Delivery teams prioritize keeping code trunk deployable over doing new work Release on demand: Software i always in a releasable state. Re time box is well defined and eq to, or less than, business need 3: Defined Regular releases over a defined period with interim milestone builds Teams build quality into release process Regular release cadence: Relea time box is well defined, but duration from idea inception to production release is greater th business need 2: Managed Time-boxed releases (the team sets a release date and manages to it) There is an adaptive delivery process Planned release: Release time b well defined, but duration from inception to production release greater than business need 1: Initial A few smart people performing heroics There is an ad hoc release delivery process Ad hoc deployments
  32. 32. Continuous Delivery Process
  33. 33. Continuous Delivery Process
  34. 34. Shift user acceptance testing left and automate it
  35. 35. Continuous Delivery Process
  36. 36. Vision of Changes Needed (Was there)
  37. 37. Vision of Changes Needed (Done)
  38. 38. Vision of Changes Needed (To do)
  39. 39. • Whole team approach • Acceptance test driven development • Continuous delivery pipeline Summary

×