This document discusses ways to improve product development cycles through effective user acceptance testing and engagement. It describes how one organization achieved targets like reducing production to release cycles from 15 to 10 months by having product owners actively participate in validation testing. Stories from the trenches are shared about having product engineers directly involved in validation testing to better represent customer needs. Exploratory "monkey" testing of system boundaries is also discussed. The key takeaway is how design thinking principles were applied, like creating focus groups, prototyping solutions, and getting faster customer feedback through various iterative testing approaches.

1. Customer value generation
through effective user acceptance
testing going beyond technical
solution
Chandan patary
Agile Coach , Global Program Manager,
ABB

2. Abstract:
• How can we achieve below target?
• Reduce cycle time from 15 months production to release cycle to 10 months
• Improve Defect removal efficiency from 75% to greater than 90%
• Reduce regression cycle time by 30%
• What we have done?
• Stories from the trenches
• Design thinking
• Requirement Engineering
• Value based delivery
• Design thinking in testing
• Acceptance testing
• Product engineer as a validation team members
• DevOps
• Exploratory test

3. • Albert Einstein said that the definition of insanity is doing the same
thing over and over again and expecting different results.
• “We can’t improve this system because we don’t have control over it.”
• It’s classic “You can’t fight city hall” syndrome.
• How can we avoid and adapt new change?
• Build and deploy fast, fail fast, learn fast, and improve fast.

15. Product owner as a validation engineer!
 Represents the customer, interfaces and engages the customer.
 Inspects the product progress at the end of every Sprint and has complete authority to
accept or reject work done
If Product owner validates the software and guide test team about the various use cases what he/she
is thinking could be area to focus and do more intensive validation will value to the product quality.

16. DevOps- Cultural changes: Stories from our team

17. Exploratory test – Monkey testing to test system
boundary

18. Key Takeaway
How we have used Design Thinking: Checklist
We have created a focus group to address the various issues in Testing
We have live customer experience,Capture customer expectation
What are the cutomer challenges? We did Brainstorm the solution,Prototye the solution.Test it with iteration
We had several Focused brainstorm session and always avoid waste of time,moderate properly the event
efficiently
We had Encouraged all the team members to contribution and captures all ideas
We did Prototype the best ideas and tested it with the people who will use the software solution
We always Looked for opportunity to get faster feedback loop
We did Document the requirements, result,record wherever possible,capture all observation at the end of testing
All information we had Captured with Mind Map diagram and all the aspects of the Product or solutions captured
We had Applied, 5 Why question to understand more about challenges

19. Thank You!!!