Project Smart ~ Exploring trends and developments in project management today

Calendar iconNot recorded
Adobe PDF icon

Project Requirement Needs For Success: Important Considerations

~ By Samantha Lorry

Spiral bound document

A company with poor requirements practices is just asking for over-budget costs and regular failure, according to a report by IAG Consulting. The report, entitled Business Analysis Benchmark, examined 110 enterprise technology projects at 100 companies to determine just how important project requirements really are.

All projects mentioned in the survey had a minimum value of $250,000, although the mean value was $3 million. Each concentrated on adding additional functionality. The study looked at the business requirements policies associated with each project, as well as the financial outcomes resulting from those policies. It could then decide which policies often lead to the success of a project.

The study found that 68 out of the 100 companies had poor requirements practices. These companies were more likely to have a marginal project or outright failure than a success and their projects were more likely to run away (take 80% longer than expected, deliver a product 30% less functional than desired, or cost more than 160% of the original budget). These poor analysis capabilities led to three times more project failures than successes.

The remaining 32 companies were more likely than not to have projects be delivered on time and on budget with the expected functionality, due to the superior business requirements processes, technologies, and competencies of people in the organisation.

A common question among business owners is how they can improve their requirements process. The questionnaire has a lot of suggestions for those clueless business owners, such as choosing and meticulously reviewing three aspects of their current documentation, or making substandard projects redo their requirements. Other advice for them in the study includes:

Focus on requirements as a process instead of a deliverable. Companies that focus on both the process and the deliverables of requirements are far more successful than those that only focus on the documentation quality. Focusing on the progress and techniques used to develop documentation is essential to gaining economic advantage and success.

Seventy percent of all companies in the study needed better IT personnel than they had available. Your company will be far more efficient once you have employees with sufficient competence in position to work on projects where their skills are needed.

Make a commitment to change. Most organisations know that requirements are important; few actually change their routine. CIOs must look at making improvement across all the areas of people, process, and tools used to support processes to gain organisational improvement.

None of these are as easy as they sound, however. Improving business requirements practices involves making systematic changes throughout an organisation. Plus, even companies with optimised requirements processes still have to deal with scope creep, mistakes, and failures. According to the report, even the best companies end up spending an average of $3.63 million on a project budgeted to cost $3 million. But that's a big improvement over most companies, who meet their budget expectations on fewer than 20 percent of all projects. IAG Consulting says that by implementing better requirements practices, companies can, and do, achieve over 80% success rates and can bring the majority of strategic projects in on time and on budget.


Comments

Be the first to comment on this article.

Add a comment



(never displayed)



 
2000
How many letters are in the word four?
Notify me of new comments via email.
Remember my form inputs on this computer.

Top Three Causes of Project Failure

Businessman in a black suit holding up a white sign reading failed

The top three causes of project failure, which if addressed will greatly increase the chances of project success.

Four Steps to Project Time Management

Man pointing at an alarm clock

The four steps outlined in this article will help you better define and measure the activities that make up your project timeline.

How to Avoid Project Burnout

Exhausted businessman resting on a pile of paperwork with tongue hanging out from overwork

Resources on projects can be susceptible to burning out before the project finishes. Here are a few ideas to prevent burnout in project teams.

Capturing Those Lessons Learned

Project team reviewing lessons learned

Do you capture your lessons learned? If you do, how effectively do you capture them?

PROJECT SMART is the project management resource that helps managers at all levels improve their performance. We provide an important knowledge base for those involved in managing projects of all kinds. With weekly exclusive updates, we keep you in touch with the latest project management thinking.

WE ARE CONNECTED ~ Follow us on social media to get regular updates and opinion on what's happening in the world of project management.


Latest Comments

Paula commented on…
How to Deal with the People Factor of Change Management
- Thu 16 May 2:52am

Billy Rane commented on…
6 Success Factors for Managing Project Quality
- Tue 14 May 4:30am

Duncan Haughey commented on…
When is a Project Manager not a Project Manager
- Fri 10 May 3:10pm

Latest tweets

In his short, but insightful article, A Thought-Provoking Idea on the Dangers of 'Nouns', Vishen Lakhiani looks at… https://t.co/PZ7MgdRqzw about 1 hour ago

General Project Management • Some advice on software https://t.co/VX5cy3IdLb about 5 days ago

General Project Management • Advice for Best Complimentary Qualification https://t.co/djava71tDD about 7 days ago