Vision and Scope Project Form

7/29/2019 Vision and Scope Project Form

1/16

Vision and ScopeDocument

for

Version 1.0 approved

Prepared by


2/16

Vision and Scope for Page ii

Table of Contents

1. Introduction..................................................................................................12. Business Requirements................................................................................13. Stakeholders and Users Profiles...................................................................5

4. Vision Statement..........................................................................................75. Product Overview.........................................................................................76. Scope and Limitations................................................................................117. Documentation Requirements ..................................................................118. Glossary.....................................................................................................13


3/16

Vision and Scope for Page iii

Revision History

Name Date Reason For Changes Version


4/16

Vision and Scope for Page 1

1. Introduction

This section provides an overview of the entire document. It should include thefollowing:

Section 1: Purpose of the documentSection 2: Brief description of the scope of the document, what project(s) itis associated with and anything else that is affected orinfluenced by this document

Section 3: An overview that contains and explains how the document isorganized

2. Business Requirements

2.1. Background

This section summarizes the rationale for the new product or the proposedenhancements. It provides a general description of the history or situation thatleads to the recognition that this product should be built or why the productshould be enhanced.

2.2. Business Opportunity

For new product

Describe the market opportunity that exists for the new product. Identify thefollowing:

problems that cannot be solved without the product,; how the product fits in with the corporate strategic direction, ; and alternatives and known competitive products that exist or may

become available. Include the major strengths and weaknesses ofeach competitor.

For enhancements

Describe the problem that will be solved by the proposed enhancement.

Identify the following: problems that cannot be solved without the product,; how the product fits in with the corporate strategic direction, ; and

2.3. Business Objectives and Success Criteria

List the important business objectives of the product. The business objectivesshould be quantitative and measurable. It should focus on the value providedto the client. This may include the following:


5/16


estimates of revenue or cost savings return on investment analysis

Describe how success will be defined and measured on this project. Identifythe factors that are likely to have the greatest impact on achieving success.

Include things within the direct control of the organization, as well as externalfactors. Establish measurable criteria to assess whether the businessobjectives have been met.

2.4. Client Needs (NEED)

Describe the clients problems and needs that the new product or theenhancements will address.

Avoid including any design or implementation details.

Present the needs in a numbered list so that detailed user or functionalrequirements can be traced to them. The following format may be used for the

problem statement. You may not use the suggested format but make sure thatthe problem statement includes the problem, the stakeholder affected by the

problem and the impact of the problem.

ProblemNo Problem statement Source

1 The problem of< describe the problem >affects< the stakeholders affected by the

problem >the impact of which is< what is the impact ofthe problem>.

Name of thestakeholder /user whoidentified the

problem2 < another problem statement >

2.5. Business Risks

Summarize the major business risks associated with developing this productsuch as marketplace competition, timing issues, user acceptance,implementation issues, or possible negative impacts on the business. Estimatethe severity of the risks and identify any risk mitigation actions that could betaken.

Risks should be arranged by probability of occurrence starting with the highestrisk exposure.

Listed below are some of the risks that may be encountered during productdevelopment. You may add or delete a risk category from the list.

ID Risk Category P L E MitigationApproaches

Who Date Due

1 Projectrequirements arepoorly structuredand lack

Ensure that theauthor who willconduct theinterview

ProjectManager

Prior totheinterview


6/16


essentialinformation.

understands thesoftwaredevelopmentprocess.

Also, make sure that

the author wastrained on thefollowing areas: interviewing

techniques technical writing

If the author is nottrained oninterviewingtechniques, theauthor must beaccompanied by

somebody who wastrained on this area.

2 Project does nothave effectivesponsorship ormanagementsupport

Find a person withauthority who couldbe a project sponsor.

Client Beforetheinterview

3 Project championleaves thecompany

When a projectsponsor is appointed,a person who can actas his/her alter egoshould also beappointed.

Client Beforetheinterview

4 Intended users of the product lackIT skills

Provide training toupgrade the IT skillsof the users.

If client is amenable,include in theproposal that ITtraining will beprovided by Vendor

Client Beforedevelopment ofsoftwarerequirements

5 Stakeholderinvolved in the

various phases ofthe softwaredevelopmentlifecycle (SDLC)was notpreviouslyinvolved insoftwaredevelopment

Train the stakeholderin SDLC appreciation

in phases where thestakeholder will beinvolved

Client Beforedevelopm

ent ofsoftwarerequirements


7/16


6 Loss of key staff Ensure properdocumentation of allproject activities.Identify alternates

Client

7 Stakeholderassigned to do

user testing andvalidation do nothave knowledgeon softwaretesting

Provide training onsoftware testing.

Outsource usertesting andvalidation

Client Beforethe start

of the testphase

8 Inadequatetesting facilities,includinghardware andsoftware

Provide the requiredfacilities.Outsource testing tocompanies that havethe requiredfacilities.

Client Beforethe startof the testphase

9 Inadequatehardware and

software

Before starting theproject, make sure

that all requiredhardware andsoftware areavailable.

Client Beforethe start

of thesoftwaredevelopment.

10 Late productdelivery.

Perform progressreview.Monitor stakeholdercommitments.Ensure that thestakeholderscompliance tocommitments.

ProjectManager

11 Deadlines areunrealistic Negotiateddeadlines.Explore alternativemeans or stop gapmeasures.

12 Potentialregulatory/policychanges

Inquire fromregulatory/policy-making bodies ifthere will be changesin the regulations /policies.

Client

P = probability of occurrence (0 to 1)

L = relative loss factor (0 to 10)E = risk exposure = P*L


8/16


3. Stakeholders and Users Profiles

3.1. Stakeholders Profiles

Stakeholders are individuals, groups, or organizations that are actively

involved in the development of the product. They can influence the projectsoutcome and are affected by its outcome.

Stakeholders are not the end users of the product to be developed but theymay be the users of the output of the product (e.g. reports, interface files).Some stakeholders have sign-off authority and are the only one who mayrequest or approve any changes to the project requirements and scope.

Vendor is also a stakeholder who is represented by the Project Manager of theteam that will develop the product.

[This should state the stakeholders / users duties and responsibilities,expertise, level of involvement, and attitudes toward the project.]

3.1.1 Stakeholders Summary

NamePosition / Job Title Responsibilities Role

< a stakeholder > List the stakeholders keyresponsibilities in relation tothe system being developed,that is, their interest as astakeholder.

At what point in thesoftware developmentcycle is the stakeholderinvolved (during projectinitiation, Planning,Development,

Implementation andDelivery)?

How is the stakeholderinvolved in the project?Relate where possible toRational Unified Processrole, that is, RequirementsReviewer, etc.

e.g.Project Initiation Requirement specifier

Planning Approveschanges to requirementsDevelopment TesterImplementation andDelivery DeploymentManager

< another stakeholder>


9/16


3.1.2 Stakeholders Details

3.1.2.1 Stakeholder Name, Position / Job Title

Department / Unitand contact numberRepresentative Who is the stakeholder representative to the project?

If the stakeholder is an institution, identify the contactperson and contact number.If not applicable, put NA.

Type Qualify the stakeholders expertise and technicalbackground.

Success Criteria How does the stakeholder define success of thesystem being developed?

ExpectedDeliverables

What are the deliverables required by stakeholders?These could be project deliverables or outputs fromthe system under development.

Comments / Issues Problems that interfere with success and any otherrelevant information go here.

3.1.3

3.2. User Profiles

This section identifies the users of the product that will be developed.

3.2.1 User Summary

NamePosition / Job Title Responsibilities Roles

< a user > List the users key responsibilities in relationto the system beingdeveloped, that is,captures details, producesreports, coordinates workand so on.

At what point in thesoftware developmentcycle is the stakeholderinvolved (during projectinitiation, Planning,Development,Implementation andDelivery)?

How is the user involvedin the project? Relatewhere possible to RationalUnified Process role.

e.g.Project Initiation Requirements ReviewerPlanning test designer


10/16


Development TesterImplementation andDelivery Trainor

< another user >

3.2.2 User Details

3.2.2.1

User name may be blank. For example, a time deposit system is implementedbranch wide, you may say that the user of the system are bank tellers.

Department / Unitand contact numberRepresentative Who is the user representative to the project? This

refers to the stakeholder that represents the set of

users.If not applicable, put NA.Type Qualify the users expertise and technical

background.Success Criteria How does the user define success of the system being

developed?Deliverables Are there any deliverables the user produces? If so,

for whom?Trainingconsiderations

Describe the kind of training and training time thatmust be provided to the user.

Comments / Issues Problems that interfere with success and any otherrelevant information go here.

3.2.3

4. Vision Statement

Write a concise vision statement that summarizes the purpose and intent of thenew product. This section describes what the world will be like when it includesthe product. The vision statement should reflect a balanced view that willsatisfy the needs of diverse clients as well as those of the developingorganization. It may be somewhat idealistic, but it should be grounded in the

realities of existing or anticipated client markets, enterprise architectures,organizational strategic directions, and cost and resource limitations.

5. Product Overview

This section provides a high level view of the product capabilities, interfaces toother applications, and systems configuration. This section usually consists ofthree subsections, as follows:


11/16


Product Perspective Product Features Assumptions and Dependencies

5.1. Product Perspective

This section puts the product in perspective to other related products and theusers environment.

If the product is a component of a larger system or has interface with otherapplication systems, then this section relates how the product interact withthe other systems and identifies the relevant interfaces between the systems.It should be able to answer the following questions:

What does the product do to / for the other application systems? What does the other application systems do to / for the product?

One easy way to display the major components of the larger system,interconnections and external interfaces is with a block diagram.

If the product is independent and totally self-contained, state it here.

5.2. Product Features (FEAT)

List and briefly describe the product features. Features are the high-levelcapabilities of the system that are necessary to deliver benefits to the users.Each feature is an externally desired service that typically requires a series ofinputs to achieve the desired result.

The level of detail needs to be general enough for everyone to understand.However, enough detail must be provided to the team to be able to create ause-case model.

Avoid design. Keep feature descriptions at a general level. Focus oncapabilities needed and why (not how) they should be implemented.

FeatureNo Feature Description

Trace to ClientNeed No Source

1 < a Feature> Name of thestakeholder /user whorequested thefeature

2 < another Feature >

5.3. Other Product Requirements (Optional)

At a high-level, list applicable standards, hardware or platform requirements,performance requirements and environmental requirements.


12/16


5.3.1 Applicable Standards (AS)

List all standards with which the product must comply. These can includelegal and mandatory, communication standards (TCP/IP, ISDN), platformcompliance standards (Windows, Unix, etc), and quality and safety standards(UL, ISO, CMM.

Requirement No Requirement Description


1 < a Requirement> Name of thestakeholder /user whorequested thefeature

2 < another Requirement >

5.3.2 System Requirements (SR)

Define system requirements necessary to support the application. These caninclude the supported host operating systems and network platforms,configurations, memory, peripherals, and companion software.





5.3.3 Performance Requirements (PR)

Use this section to enumerate performance requirements. Performanceissues can include user load factors, bandwidth or communication capacity,throughput, accuracy and reliability or response times under a variety ofloading conditions.





5.3.4 Environmental Requirements (ER)


13/16


Identify environmental requirements as needed. For hardware-basedsystems, environmental issues can include temperature, shock, humidity,radiation and so forth. For software applications, environmental factors caninclude usage condition, user environment, resource availability,maintenance issues, and error handling and recovery





5.3.5 Security Requirements (CR)

Discuss the data protection and access security controls requirements





5.4. Assumptions and Dependencies

5.4.1 Assumptions

Record any assumptions that were made when conceiving the project andwriting this document. List assumptions that, if changed, will alter thedocument.

Examples:

A specific operating system will be available for the hardware designated forthe software product. If the operating system is not available, the documentwill need to change.

The stakeholder assigned to do user acceptance testing and validation istrained on the software testing process. If the stakeholder is not trained onthe process, the stakeholders roles and business risks of the document willchange.


14/16


The intended users of the product are computer literate. If the users are notcomputer literate, the training needs and business risks sections of thedocument will change.

5.4.2 Dependencies

Note any major dependencies the project must rely upon for success, such asspecific technologies, third-party vendors, development partners, or otherbusiness relationships.

6. Scope and Limitations

6.1. Scope of Initial Release

Describe the intended major features that will be included in the initial release

of the product. Focus on those features and product characteristics that willprovide the most value, at the most acceptable development cost, to thebroadest community.

FeatureNo Feature Description Priority

1 < a Feature>2 < another Feature >

Priority 1 = feature is essential, mandatory, non-negotiable or urgentrequirements

Priority 2 = feature is useful, negotiable or slightly deferrable requirementsPriority 3 = feature is desirable if low cost, can be readily descoped, flexible orlonger delay requirements

6.2. Scope of Subsequent Releases

If a staged evolution of the product is envisioned over time, indicate whichmajor features will be deferred to later releases.

6.3. Limitations and Exclusions

Identify any product features or characteristics that a stakeholder might anticipate, but

which are not planned to be included in the new product.

7. Documentation Requirements

7.1. Users Manual


15/16


Describes the purpose and content of the User Manual. Discuss the desiredlength, level of detail, need for index, glossary of term, tutorial versusreference manual strategy, and so on. Formatting and printing constraintsmust be identified also.

The source of the requirement must be identified.

7.2. Online Help

Many applications provide an online help system to assist the user. Thenature of these systems is unique to application development as theycombine aspects of programming with aspects of a technical writing such asorganization and presentation. Many have found the development of onlinehelp system is a project within a project that benefits from up-front scopemanagement and planning activity.


7.3. Installation Guides, Configuration and Read Me File

A document that includes installation instructions and configurationguidelines is important to a full solution offering. Also, a Read Me file istypically included as a standard component. The Read Me file can include aWhats New With This Release section, and a discussion of compatibilityissues with earlier releases. Most users also appreciate documentationdefining any known bugs and workarounds in the Read Me file.


7.4. Labeling and Packaging

Todays state-of-the-art applications provide a consistent look and feel thatbegins with product packaging and manifests through installation menu,splash screens, help systems, GUI dialogs, and so on. This section defines theneeds and types of labeling to be incorporated into the code. Examplesinclude copyright and patent notices, corporate logos, standardized icons and

other graphic elements, and so forth.



16/16


8. Glossary

Vision and Scope Project Form

Documents

Transcript of Vision and Scope Project Form