Project Management Central

Please login or join to subscribe to this thread

Is failing fast always good to learn, improve and succeed fast?
Network:192



Fail fast is a tenant of Agile but is it always good to learn and improve fast? Sometimes complete effort and all possible alternatives are not explored with the intent to fail fast. Is this aligned with Agile principles?
Sort By:
Network:19



I believe Agile is a new tendency. It has not explored by many organizations. Therefore, it is acceptable to fail fast in this methodology since it has been introduced recently. Once it is implemented in most small and giant corporations, then it is better to utilize it without failing.
Network:1835



There is a big misunderstanding about it. Is not because I am saying that. Is because if you go to the basement of Agile you will find it, the real meaning of it. Is not about failing fast and learn. Is about to control risks. Go to Barry Bohem´s Spiral model and Tom Gilb´s Software Engineering book. In addition go to Rick Dove´s work that was taken from the place wher Agile was born and you will see that one of the pillars of Agile is knowledge management.
Network:1480



Gaurav -

Agile approaches encourage earlier exploration of risks through techniques such as spikes and MVPs. The expectation is that if you are going to hit any challenges with the solution or other aspects of the project then it is better to hit those early when you have more budget and time to be able to take a different route.

Kiron
Network:98163



Failing fast really means I will do what I can with what I have and know at this moment. I keep telling people not to put a "draft" watermark in a document ready for review. The document is as done as it can be at that point in time.

Not only does failing fast allow you to change direction but it also limits your sunken costs. Finally, it keeps us from getting too attached to our solutions, documents and products.
...
1 reply by Eric Simms
May 17, 2019 7:19 PM
Eric Simms
...
I like the part about not getting unduly attached to our work products or ways of doing things.
Network:608



May 17, 2019 7:11 PM
Replying to Stéphane Parent
...
Failing fast really means I will do what I can with what I have and know at this moment. I keep telling people not to put a "draft" watermark in a document ready for review. The document is as done as it can be at that point in time.

Not only does failing fast allow you to change direction but it also limits your sunken costs. Finally, it keeps us from getting too attached to our solutions, documents and products.
I like the part about not getting unduly attached to our work products or ways of doing things.
Network:192



Thank you all for the interesting and insightful view points. Having different view points definitely brings more clarity on the topic.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Try not to have a good time...this is supposed to be educational."

- Charles Schultz

ADVERTISEMENT

Sponsors