Why software developers refuse to improve

Many developers fail to acknowledge that there are more productive environments. When a software organization loses a bidding contest, the losers roll their eyes heavenward and tell each other, “Better luck next time”. Well, this is the reality: There are software development organizations that are more productive than others. “Luck” is not the whole story; you need to look for ways to improve. Use valid process; there are a dozen or so well-regarded methodologies. We especially need to reach two audiences. Sponsors, those who finance new ideas, need information tailored to the functions they perform in adopting and financing new ways of working. Practitioners those actually applying the new ideas, need detailed books, manuals, short courses, helpful supervision, and mentoring. They also need software tools to do what tools can do better than people. Even after simplification, there will still be a lot of changes to implement. Leading companies understand that implementation takes: Investment money up front (sometimes for years before payback begins); a champion; dedicated people, and consistent management, dedicated to long-term financial support. The accomplishment to which the idea leads has to be evident to all, and demonstrated by some type of metrics. The ultimate drivers that influence practitioners and management alike to sue a difficult course are results that establish the course's success