1 / 8

Managing scope

Learn how to effectively manage project scope by establishing a high-level requirements baseline and setting priorities based on resources, time, and user needs. Assess effort and risk to reduce scope assignment and deliver a successful project.

plibby
Download Presentation

Managing scope

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. Managing scope

  2. Establishing project scope • Project scope is a combination of product functionality, project resources and available time. • If the effort required to implement the system features is equal to the resources available during the scheduled time, the project has an achievable scope. • Overscoped projects are typical. In many projects, it will be necessary to reduce the scope by as much as a factor of two. • The first step in establishing project scope is to establish a high-level requirements baseline

  3. What is project scope • The functionality that must be delivered to meet the user’s needs • The resources available to the project • The time available in which to achieve the implementation Resour ces Scope Developers, testers, tech writers, QA personnel For our project, the resources and time are fixed. Time Deadline

  4. The requirements baseline • The baseline is the itemized set of features intended to be delivered in a specific version of the application • The baseline must • Be at least acceptable to the customer • Have a reasonable probability of success in the team’s view • In creating the baseline, list the features, no matter how complex, a new system can be described by a list of 25-50 features. • More than that – too complex • Less than that – the level of detail may be too simplified to provide a sufficient understanding

  5. Setting priorities • User, customer, product managers should involve in prioritization • Less influence from the technical community • Scale – critical, important, useful Assessing effort • Estimate the rough level of effort implied by each feature of the proposed baseline • Scale – high, medium, low

  6. Adding the risk element • The probability that the implementation of a feature will cause an adverse impact on the schedule and/or budget • A high-risk feature has the potential to impact the project negatively • The development team may use heuristic method that they comfortable with • Scale –low-medium-high

  7. Reducing scope

  8. assignment • Prioritize the features • Identify the baseline features – highlight mandatory, optional and future features • Present your results.

More Related