Fear Driven Development is closely linked to PDD - Panic Driven Development.
PDD - Panic Driven Development.
"Panic is a sudden sensation of fear, which is so strong as to dominate or prevent reason and logical thinking, replacing it with overwhelming feelings of anxiety and frantic agitation consistent with an animalistic fight-or-flight reaction."
I see PDD as an anti-pattern that many organisations and product development teams end up adopting. It's not conductive to creating anything. It's destructive to the team. It's destructive to the organisation and it's destructive to the product.
As software product development is primarily knowledge work, there is a requirement for calm, peaceful space so that enhanced thinking and problem solving can be attained.
Yes - I see "Panic Driven Development" as something to be avoided for sure: you don't want to be rushing because of some anxiety - that leads to errors.
What I really mean by "Fear" driven development is kind of the opposite: instead of succumbing to whatever fears you have, fully embrace them in a calm and collected way. Basically: the things that seem scary are often not so scary once you have all the information :) (whereas with Panic Driven Development, you never get to that point: you're always "running scared")
Fear Driven Development is closely linked to PDD - Panic Driven Development.
PDD - Panic Driven Development.
"Panic is a sudden sensation of fear, which is so strong as to dominate or prevent reason and logical thinking, replacing it with overwhelming feelings of anxiety and frantic agitation consistent with an animalistic fight-or-flight reaction."
I see PDD as an anti-pattern that many organisations and product development teams end up adopting. It's not conductive to creating anything. It's destructive to the team. It's destructive to the organisation and it's destructive to the product.
As software product development is primarily knowledge work, there is a requirement for calm, peaceful space so that enhanced thinking and problem solving can be attained.
Yes - I see "Panic Driven Development" as something to be avoided for sure: you don't want to be rushing because of some anxiety - that leads to errors.
What I really mean by "Fear" driven development is kind of the opposite: instead of succumbing to whatever fears you have, fully embrace them in a calm and collected way. Basically: the things that seem scary are often not so scary once you have all the information :) (whereas with Panic Driven Development, you never get to that point: you're always "running scared")
Yes - so the Fear, isn't external to your team, but the Fear of something uknown. As you say, embrace the "Fear" and let it drive you forward