Having good or effective project sponsors is one of the ways you can prevent project failure which is a real problem considering that nearly two – thirds of projects fail!
The project sponsor is not the business analyst even though the project sponsor helps the business analyst in gathering requirements and the project sponsor is not the project manager even though the project sponsor helps the project manager deliver a successful project.
It is important in business to deliver whatever is promised on time.
However, the urgency attached to deadlines can become overwhelming due to all the multi-tasking, conflicting priorities or task / time juggling that we all have to do!
However, from the viewpoint of a client or employer, saying, “I didn’t have enough time is a sure sign of poor time management skills or incompetency.”
The inconvenient truth is that missing a deadline is unprofessional and excuses are no longer welcome in today’s fast-paced workplace.
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.
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:
Scott Berkun, a former Microsoft Program Manager shares his views about becoming a project manager.
His views are startingly similar to the views we have been posting on this website … that getting more handson experience is the best way to jumpstart your career!
Notice Scott does not start with a long list of educational requirements or certifications for aspiring project managers but with something that you have heard me talk a lot about … hands-on experience!
Scott’s Advice for Aspiring Project Managers:
WORK ON A PROJECT.
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.