1 / 18

Getting the Scope and Business Requirements Right!

Getting the Scope and Business Requirements Right!. Presented By: Sonya Hawkins. Today’s Discussion. Discuss Scope Discuss Requirements. P roject Scope. “The work that needs to be accomplished to deliver a product or results with the specified features and functions.”.

tala
Download Presentation

Getting the Scope and Business Requirements Right!

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Getting the Scope and Business Requirements Right! Presented By: Sonya Hawkins

  2. Today’s Discussion • Discuss Scope • Discuss Requirements

  3. Project Scope “The work that needs to be accomplished to deliver a product or results with the specified features and functions.”

  4. Project Management Triangle Quality Resources COST TIME SCOPE

  5. Scope Creep COST TIME Quality Resources SCOPE

  6. Scope Control Starts Day One! • Thoroughly understand the project vision • Understand your priorities and the priorities of the project drivers. • Define your deliverables and have them approved by the project drivers. • Break the approved deliverables into actual work requirements.

  7. Project Scope The purpose of doing the project.

  8. “The most difficult part of requirements gathering is not documenting what the user ‘wants’; it is the effort of helping users figure out what they ‘need’ that can be successfully provided within the cost and schedule parameters available to the development team.” Steve McConnell Software Project Survival Guide. Redmond, Washington. :Microsoft Press, 1998

  9. Getting The Requirements Right!

  10. Requirement Risks • The cost of rework is typically 45% of a project's cost. • There is as much as a 2000:1 cost savings from finding errors in the requirements stage vs. in the maintenance stage of the life cycle • Reducing requirements errors is the single most effective action developers can take to improve project outcomes. Young, Ralph R., 2001

  11. Requirement Principle Separate the “What” from the “How” The “what” refers to the requirements – what is needed to solve the problem The “how” refers to how the solution will be designed and implemented.

  12. Requirements Should Be…… • Consistent • Measurable and testable • Prioritized • Unambiguous • Verifiable • Does not define solution • Attainable • Complete • Correct • Feasible • Necessary • Traceable • Understandable

  13. A Misunderstood “Need” Leads to an Unsatisfied “Requirement” • Unclear, imprecise, incomplete • Conflicting • Difficult to predict impact and feasibility

  14. Example 1 • “The product shall switch between displaying and hiding non-printing characters instantaneously” OR • “The user shall be able to toggle between displaying and hiding all HTML markup tags in the document being edited with the activation of a specific triggering condition”

  15. Example 2 • “Charge numbers should be validated online against the master corporate charge number list, if possible.” OR • “The system shall validate the charge number entered against the online master corporate charge number list . If the Charge number is not found on the list, an error message shall be displayed and the order shall not be accepted.”

  16. Example 3 • The website shall be user friendly and load fast. How would you re-write…………..? • Can you measure? • Can you test? • Can you verify you satisfied this requirement?

  17. Lastly • Understand the Scope of the project • Define the Requirements for the project to be a success

  18. Questions

More Related