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.
Duncan Nisbet
Software Test Coach
duncannisbet.co.uk
@DuncNisbet
Feedback
The conclusion…
Shared documentation
!=
Shared understanding
The conclusion…
Shared documentation
≠
Shared understanding
The conclusion…
Shared documentation
<>
Shared understanding
The conclusion…
Shared documentation
does not equal
Shared understanding
“Let’s give our NHS the £350 million
the EU takes every week’ and ‘We
send the EU £350 million a week, let’s
fund our NHS ...
The premises…
• Shared docs do not equal shared understanding
• Misunderstanding results in incorrect assumptions
• Incorr...
The argument…
• Testing is asking questions to squash assumptions
• The earlier we ask questions, the sooner we can
squash...
Shared understanding
?
?
The dice product challenge
• You are the development team creating
fantastic dice shaped products
• Team:
• Product Owner
...
Round 1 – 15 mins
• BA - describe the product in words (requirements)
• Dev – build the product from the requirements
• Te...
Round 2 – 15 minutes
• Everyone can ask questions of Everyone
• The PO can accept parts of the product
Implicit requirements
• 1 cube = 1 dice
• All spots on top of the dice must be odd
• Dice with the same number of spots on...
Expected
(required system)
Actual
(delivered system)
James Lyndsay’s #1 diagram of testing
Expected
(required system)
Actual
(delivered system)
Expected
(required system)
Actual
(delivered system)
Test Driven Development
Test First Development
Expected
(required system)
Actual
(delivered system)
Need
3 Amigo sessions
Frequent releases
Small batches
Test Driven Dev...
Dream
Requirements
Design
Build
How can I test upstream?
Dream
Requirements
Design
Build
• Question the product
• Break illusions
• Feedback information
Dream
Requirements
Design
Build
• Discuss testability
• Understand the design patterns
• Understand the implications
• Make the implicit explicit
• Discuss testability
• Squash assumptions
Dream
Requirements
Design
Build
• Question the idea of the product
• Understand the need
• Understand the why
Dream
Requirements
Design
Build
Feedback
Squash
Assumptions
Discover
Information
Feedback
Key takeaways
Starting testing early helps:
• Challenge assumptions early
• Reduce size of work products
• Deliver value s...
Duncan Nisbet
Software Test Coach
duncannisbet.co.uk
@DuncNisbet
END
Agile Manifesto
Agile Manifesto
• Eliminate waste
• Amplify learning
• Defer commitment
• Deliver as fast as possible
• Empower the team
• Build integrity...
Round 2 – 12 mins
• BA – can ask questions of PO
• Dev – can ask questions of BA
• Test – can ask questions of Dev
• PO – ...
Testing! Be More Salmon! - Agile North
Testing! Be More Salmon! - Agile North
Testing! Be More Salmon! - Agile North
Testing! Be More Salmon! - Agile North
Testing! Be More Salmon! - Agile North
Testing! Be More Salmon! - Agile North
Testing! Be More Salmon! - Agile North
Testing! Be More Salmon! - Agile North
Testing! Be More Salmon! - Agile North
Testing! Be More Salmon! - Agile North
Testing! Be More Salmon! - Agile North
Testing! Be More Salmon! - Agile North
Testing! Be More Salmon! - Agile North
Testing! Be More Salmon! - Agile North
Upcoming SlideShare
Loading in …5
×

Testing! Be More Salmon! - Agile North

381 views

Published on

slide deck from my "Testing! Be More Salmon!" workshop which I ran at Agile North 2016

Published in: Software
  • Be the first to comment

  • Be the first to like this

Testing! Be More Salmon! - Agile North

  1. 1. Duncan Nisbet Software Test Coach duncannisbet.co.uk @DuncNisbet
  2. 2. Feedback
  3. 3. The conclusion… Shared documentation != Shared understanding
  4. 4. The conclusion… Shared documentation ≠ Shared understanding
  5. 5. The conclusion… Shared documentation <> Shared understanding
  6. 6. The conclusion… Shared documentation does not equal Shared understanding
  7. 7. “Let’s give our NHS the £350 million the EU takes every week’ and ‘We send the EU £350 million a week, let’s fund our NHS instead” Vote Leave Campaign, Brexit
  8. 8. The premises… • Shared docs do not equal shared understanding • Misunderstanding results in incorrect assumptions • Incorrect assumptions result in an undesired product
  9. 9. The argument… • Testing is asking questions to squash assumptions • The earlier we ask questions, the sooner we can squash assumptions • The sooner we test the greater chance we have of delivering the desired product first time
  10. 10. Shared understanding
  11. 11. ?
  12. 12. ?
  13. 13. The dice product challenge • You are the development team creating fantastic dice shaped products • Team: • Product Owner • Business Analyst • Developer • Tester
  14. 14. Round 1 – 15 mins • BA - describe the product in words (requirements) • Dev – build the product from the requirements • Test – add up the spots on the touching sides • PO – accept or reject product • No talking!
  15. 15. Round 2 – 15 minutes • Everyone can ask questions of Everyone • The PO can accept parts of the product
  16. 16. Implicit requirements • 1 cube = 1 dice • All spots on top of the dice must be odd • Dice with the same number of spots on top cannot be next to each other • Red & blue dice cannot be touching • Red dice must be facing the PO • Each iteration of the product needs to have •same explicit requirements (i.e. shape as per image) •different patterns of spots that still adhere to the implicit requirements
  17. 17. Expected (required system) Actual (delivered system) James Lyndsay’s #1 diagram of testing
  18. 18. Expected (required system) Actual (delivered system)
  19. 19. Expected (required system) Actual (delivered system) Test Driven Development Test First Development
  20. 20. Expected (required system) Actual (delivered system) Need 3 Amigo sessions Frequent releases Small batches Test Driven Development Test First Development
  21. 21. Dream Requirements Design Build How can I test upstream?
  22. 22. Dream Requirements Design Build • Question the product • Break illusions • Feedback information
  23. 23. Dream Requirements Design Build • Discuss testability • Understand the design patterns • Understand the implications
  24. 24. • Make the implicit explicit • Discuss testability • Squash assumptions Dream Requirements Design Build
  25. 25. • Question the idea of the product • Understand the need • Understand the why Dream Requirements Design Build
  26. 26. Feedback Squash Assumptions Discover Information Feedback
  27. 27. Key takeaways Starting testing early helps: • Challenge assumptions early • Reduce size of work products • Deliver value sooner
  28. 28. Duncan Nisbet Software Test Coach duncannisbet.co.uk @DuncNisbet
  29. 29. END
  30. 30. Agile Manifesto
  31. 31. Agile Manifesto
  32. 32. • Eliminate waste • Amplify learning • Defer commitment • Deliver as fast as possible • Empower the team • Build integrity in • See the whole
  33. 33. Round 2 – 12 mins • BA – can ask questions of PO • Dev – can ask questions of BA • Test – can ask questions of Dev • PO – accept or reject product • Yes / No questions only

×