Key findings from several reports have shown that up to 60% of Software / Information Technology (IT) Projects fail because of cost / budget overruns, and missed or poorly delivered functionality.
In this article, I will show you how to prevent that from happening to you or your projects …
Why Do We Need Better Requirements?
The following article is a frank, open and surprising discourse on why we need better requirements.
According to Standish or Gartner reports and other case studies, nearly “two-thirds of all IT projects fail” because of poor requirements and other causes.
Why Do Projects Fail?
Consider that a project fails when it overruns the budgeted allocation of resources, time or money or fails to deliver the intended business requirements or value.
Some teams are so deep into this, that throwing more money, people or extending the shipping date is their default solution to scope creep, budget overruns or project failure!
There comes a time in your career when you will have to take a serious look at the possibility of moving into management.
This may be preceded by a time of dis-satisfaction with the status quo either because:
- You are beginning to feel that you have hit a glass ceiling
- You are thinking that you would do a better job than some managers you’ve worked for
Statistics show that the majority of software development (web, IT, desktop, mobile…) projects are doomed to fail from inception.
The challenges facing technical leads, project managers, software development, IT managers or project sponsors are often under-estimated leading to less than successful projects.
While some software teams may argue or live in-denial of the risk facing their projects, the facts are that more than 60% of software projects fail!
The effects of poorly managed software projects are also obvious. They include:
Michael Surkan a former Microsoft Senior Product Planner and Program Manager is looking for Volunteer Software Testers and Project Managers for an on-line customer relationship management (CRM) and business management software service project.
While at Microsoft, Michael conducted customer, industry and research to help make decisions for future versions of the Windows operating system.
Michael’s work includes using surveys, focus groups, and customer interviews as part of research strategies and synthesized all the data into conclusions and recommendations for senior managers.