Pain Driven Developement

Pain Driven Development (PDD)!....

Yet another term!.... that is what my first thought/impression when I saw Jeff''s Blog Post on the same. I couldn't agree more to Jeff''s views on considering pain reduction as an ROI.

More from Jeff's blog,

"The point of this post is to think of pain reduction as ROI. In business, we might spend money on software for some expected return on investment. While working with the software, we also have returns on investment, but in the form of productivity. Pain kills productivity. Over time, we might learn to live with pain through parts of the process by taking a constant does of , but that only hides the pain. It doesn't cure it.

Pain-driven development is a mindset where developers react intensely to pain and solve it so that it goes away once and for all. PDD practitioners don't just cover up the pain. We eradicate it. PDD leads to a completely frictionless software process that is a joy to experience."

Perfectly agree to you Jeff.

I can't even count the number of times I took pain killers to resolve(it is not resolving, just hiding) the bottlenecks. Most of them related to design flaws, SCM issues and off course all impacted on the quality. Most of the time, a marginal developer(an ALT.NET terminology) will try to get his business ( software development process) to break even... not worried about ROI and profit. It is the same same place, this pain kills most of us, and in turn calls the need of better thoughts/mid set to overcome these bottlenecks.

Note: In real life am allergic to pain killers!... (Let me recall the first 911 experience because of the same here.)

Let's more people realistically think and propose some common scenarios and solutions/ways to avoid pain killers in software industry.

Nice starting Jeff. Thanks a lot.

Jeff''s complete blog post can be found here: http://codebetter.com/blogs/jeffrey.palermo/archive/2008/02/11/pain-driven-development-uncovering-the-motivation.aspx