Logged in as    

Does your project have a Business Requirement Specification (BRS), if not, why not?

Three women and a man looking at a MacBook

If the answer is no then your project maybe the:

47% “Unsuccessful projects fail to meet goals due to poor requirements” Project Management Institute (PMI)


3 of the top 5 reasons projects fail are related to requirements: Users are not involved enough in requirements definition, requirements are incomplete or don’t meet acceptance criteria, requirements are constantly changing, and these changes are not managed effectivelyThe Standish Group International, Incorporated

A well-constructed and managed Business Requirement Specification (BRS) is the cornerstone of enabling change to happen, aligning the stakeholders to common understanding of the “as is” and the agreed “to be”. Business requirements are the foundation of the BRS, which should be of quality; correct, complete, precise, unambiguous and consistent.

In both the Business Analysis Body Of Knowledge (BABOK®) and PMI® – BA Practitioners Guide© requirements are defined in high & low levels. The standard types of requirements are Business Requirements, Stakeholder Requirements, Solution Requirements, Functional and Non-Functional Requirements and Transition Requirements.

A BRS is not 80 pages of dribble, but is a structured document, which decomposes the scope into a lower level of detail. Less is more, and the very best BRS documents have less words and more stakeholder understanding than pages of unread text.

Want to know more? Contact us on info@business-analysis.com.au or at www.business-analysis.com.au

Make an Enquiry

We're glad to help and answer any questions you might have.

Send us a message

For Landlines – (##) #### ####

Please login below to access this page