Any testing methodology is influenced by waste. This workshop has 3 parts:
How is waste categorized? What waste can endanger an Agile approach.
We’ll use 10 minutes to explain the waste categories based on the acronym TIMWOOD++ (transport, inventory, moving, waiting, over production, over processing, defects, talent, bureaucracy)
We’ll use the rest of the first half to gather waste in Agile project with the help of the people present.
Identifying waste is one thing. Knowing the origin is another.
We’ll use 5 minutes to explain how to get to the bottom of things, using MUDA, MURA, MURI.
We’ll use 20 to discuss in group a number of wasteful things.
Having a solution for waste is like hitting the ball out of the park.
We’ll use 20 minutes to brainstorm over:
Agile manifesto 2.0
Agile principles 2.0
All people present should receive upfront the agile manifesto and the agile principles, to help them in the exercises.
Conclusion at the end should be: Agile just like other methodologies is prone to waste. Solving waste problems in Agile will need teams to think about what they are doing and to adapt and to deviate away from the black and white view of the Agile manifesto and the Agile principles.
