home

A Requirements Management Myth Busted at Rational Software Conference

Well it's the final day today of the Rational Software Conference / Telelogic User Group Conference in cloudy Orlando today. What a great day of keynote and session tracks here yesterday. Although the keynote featuring Watson and the Mythbusters was very entertaining, highlight of the day for me was hearing a requirements  management myth busted that IBM Rational (formerly Telelogic) DOORS is only for large engineering teams building battleships.

An IBM customer has deployed DOORS in a small software development team (less than 20 people) developing a web application that uses the Electronic Medical Record to provide patient data analytics vital to the treatment and care of medical patients.

Before putting in place an improved requirements management process, the team were surviving on a hero culture, but often didn't completely satisfy stakeholder expectations and they didn't have the ability to estimate software delivery times and had loose project schedules. After taking steps to capture and structure requirements in DOORS, and review with development and QA stakeholders using DOORS Web Access (web browser access to the requirements database), estimation and understanding of what can be delivered in a timeframe has improved, similar functionality has been delivered in 25% of the calendar time, and they've seen a 69% net reduction in the cost of test preparation, testing, and rework, with the most dramatic improvements in reduced rework because of better management of what is to be delivered. And not only that but also team morale has improved because of the satisfaction of delivering higher quality work.

Well it's time I headed off for breakfast and into the last morning keynote and track sessions. More from me tomorrow.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
DOORS is a good product by gengstrand

    Sponsored Announcements & Special Offers

view counter

Whitepaper from HP - Why Focus on Requirements Definition Management in the Application Lifecycle?

Increasingly, smart businesses are looking much closer at requirements definition (RD) and requirements management (RM) (sometimes grouped together under the Gartner-coined phrase, requirements definition management (RDM)) to streamline the entire application lifecycle. Why? Because systematic and effective RDM captures software defects earlier in the lifecycle, and it reduces the overall likelihood that defects will be introduced. That’s important. How important? According to one study, the cost to fix a defect after delivery is more than 100 times the cost to fix it in the requirement and design phase. No business wants to be hit with that bill. Now to add to this the growing interest in agile development techniques as a way to deliver higher quality applications and we have an interesting recipe for success.

Download a Free Copy

view counter
© 2007-2010 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group