Project Perfect
PROJECT  PERFECT
                 Project Management Software
                          Specialists in Project Infrastructure

Home - White Paper Index

Reducing Time Spent on Requirements

Rating

Neville Turbit - Project Perfect

Requirements Management

Recent research in the US indicated the time spent between

  • Gathering requirements (Business Requirements & System Requirements) for a new system and
  • Building and testing the system

was becoming more biased towards the requirement gathering.  A range of languages were investigated and the results ranged from a 50:50 split for Assembler to a 90:10 split for Ada.  In other words, for every week spent coding and testing in Ada, 9 weeks were spent gathering requirements. 

Requirements

50% to 90%

Build & Test

50% to 10%

 As languages become more sophisticated and develop drop and drag, point and click type interfaces, there is a real benefit to the developers but it doesn't have a big impact on the Business Users. Obviously the systems can be delivered sooner but the time the Business Users spend specifying the system is not significantly effected.

The trend to buy package solutions does not take away the issue of improving speed of delivery.  If software is to be written from scratch or bought, the requirements still need to be developed. 

In one sense, if you have a choice between cutting the requirements gathering process by a month on every project or, with the same effort, cutting coding and testing time by a month, the obvious focus would be on requirements.  Requirements are needed whether you write your own software or buy it.

 

Get Organised with Project Administirator Software

Key Points:

  • RAD (Rapid Application Development)

  • Prototyping

  • Requirement Gathering

  • 1.  Difficulties in Visualization

  • 2.  Difficulties in gaining access to people

  • 3.  Difficulties in Compromise

  • 4.  Difficulties in reaching Decisions

  • Standish Research

  • Success Factors (weighted)

  • Past Attempts to Improve Requirement Gathering

  • The Three Generations of gathering System Requirements

  • Generation 1.  Direct Contact

  • Generation 2.  Business Analyst

  • JAD - Joint Application Development

  • The Way Forward

  • Business Involvement

  • Generation 3 - Team Based

  • Process for Decision Making

  • Evolutionary approach for Requirements

  • Other Aids

  • Break it Down

  • Templates

  • Quality Assurance

  • Planning

  • Repeatability.

  • Evaluating an Organisation

  • Summary

To date, 133 people have rated this article. The average rating is 4.15

Join our Members Club to view the article. It costs only A$10:00 ( ) per month. No minimum term. There are lots of other benefits including access to 150 project management white papers, online project management methodology, free templates and user guides, and 40% discount on Project Administrator Software (with 12 mth registration).

test
Register for the Members Club