I was so focussed on Lean 6 Sigma and Change Management that I did not even realize I was actually working 80% or more in an Agile enviornment. Often times I had my hand slapped (virtually) during a Kaizen process because I did not follow strict rules to get from A to Z and now I see that A and Z should have been working together from the beginning. Thanks guys.
Its time to update the Face to Face with Zoom/Teams with Camera On. Agile methodology is not keeping up with the change in the world at this point in time IMO.
@@TheAgileCoachLLC Google's landing page is simple, so there's some merit to your explanation, but I agree with Somaye that you've missed the mark on this one. This principle would generally be interpreted as "don't do unnecessary work" As a possibly more relevant example: I have a customer tell me I must create a product that decrypts three types of video encryption. My team adds the capability to decrypt the first type, and give that software to the customer. Customer starts trying it out, and my team starts on the second type. At our next meeting, the customer might say something like "We tried it out, and it turns out that what you gave us actually solves the problem completely. We didn't think we could provide the same encryption type to all deployments, but now that we tried it, we can. We don't need the other two types at all!". At this point, the team can roll back the work they did on decrypting the second encryption type, never implement type 2 and 3, and move on to whatever the customer wants next.
Wonderful information. Thanks for your efforts 👍
Glad you enjoy our content, Jasu! Thanks for letting us know we're providing value!
Very nicely explained. I like the way you both interact. 👍
Thank you 😊
Thanks
thank you, it was quite helpful😊
We're glad you found it helpful! ☺
Thank you:)
Fantastic
I was so focussed on Lean 6 Sigma and Change Management that I did not even realize I was actually working 80% or more in an Agile enviornment. Often times I had my hand slapped (virtually) during a Kaizen process because I did not follow strict rules to get from A to Z and now I see that A and Z should have been working together from the beginning. Thanks guys.
Great Conversation!
not bad
Its time to update the Face to Face with Zoom/Teams with Camera On. Agile methodology is not keeping up with the change in the world at this point in time IMO.
Sounds like it's not so agile on that front then.
Hey guys
you are wrong about the meaning of the principle number 10!
Hi Somaye! Thanks for commenting. What do you feel is the meaning of principle number 10?
@@TheAgileCoachLLC Google's landing page is simple, so there's some merit to your explanation, but I agree with Somaye that you've missed the mark on this one. This principle would generally be interpreted as "don't do unnecessary work"
As a possibly more relevant example: I have a customer tell me I must create a product that decrypts three types of video encryption. My team adds the capability to decrypt the first type, and give that software to the customer. Customer starts trying it out, and my team starts on the second type. At our next meeting, the customer might say something like "We tried it out, and it turns out that what you gave us actually solves the problem completely. We didn't think we could provide the same encryption type to all deployments, but now that we tried it, we can. We don't need the other two types at all!". At this point, the team can roll back the work they did on decrypting the second encryption type, never implement type 2 and 3, and move on to whatever the customer wants next.
@@KnightElite0 perfect! It make sense in this scenario :)
Bn