Appendix L: Software Requirements Changes

Software Requirements Changes (SRC)		CI:
		Date raised:
Source of SRC
Description of SRC
Consequence(s) of SRC
Impact on project if SRC not actioned
Responsibility for Actions
Impact of each action on: Risks Project milestones Project tolerance
Recommendations
Executive Board notification	Date	Action Required

Appendix M: Problem Report (PR)

Problem Report (PR)		CI:
		Date raised:
Source of Problem ( reported by and owner)
Description of Problem
Actual or potential consequence(s) of problem
Action(s) taken to mitigate problem so far
Responsibility for Action(s)
Impact of each action on: Risks Project milestones Project tolerance
Recommendations
Executive Board notification	Date	Action Required

Appendix N: Corrective Action Processing (CAP)

Corrective Action Processing (CAP)		CI:
		Date raised:
Source of CAP ( name , position in organization “ project group )
Area CAP relates to: Software development Quality Training Design of product Management of project Other
Description of CAP
Other areas this CAP could relate to
Impact on organization if CAP not addressed
Responsibility for actions relating to this CAP
Impact of each action on : Risks Project milestones Project tolerance Future of BEC
Recommendations
Which forum should CAP be raised at? Monthly meeting Prototype demonstration Training event Software review Ad hoc
Executive Board notification	Date	Action Required

Appendix O: Specification Change Notice

click to expand

Appendix P: Project Statement of Work

OVERVIEW

System Release # Project # CI #

VERSION: Draft

Project Statement of Work

Project Manager: < name >

Created: <date>

Last Updated: <date>

Created By: <name>

PROJECT INFORMATION

Project Request

This project has been requested to provide various Business Lines new and/or improved functionality within the <application name > System. Some of the requested changes will be beneficial for the customer also.

Project Number and Title

This project will be referred to as the "?? Project." The project number is ??.

Executive Sponsor or Delegate

The Business Group Head for this project is <group head name> of <company name> and the executive sponsor is <executive sponsor name>, Group Technology Executive.

PROJECT DEFINITION

Background

There are several requirements requested for Release ??. These requirements will be funded by various Business Lines and will benefit several different areas as well as the customer in many cases.

Release ?? is one of two remaining releases scheduled for <year> by the enterprise. The planned implementation date for Release ?? is <date>. This release will be coordinated with the <project name > scheduled between <month> and <month> <year>.

Project Objectives

To provide more functionality and data accessibility in the ?? System to the Business Lines and the customer in the least amount of time for the most reasonable cost.

Business Units Involved

Internal

Impacts to the following applications were determined in the initial data gathering phase of this project. Certain applications have been defaulted to testing only as no response was obtained during the data gathering phase. Formal sizing has been gathered from all impacted applications as a part of the requirements phase of this project. This list represents the internal interfaces.

Internal Applications/Areas: Impacts:

Application name: No development set-up and testing needed
Application name: Application name Development, testing needed
- Application name Development
- Application name Testing needed
Application name: Development, testing needed
- Sub-system name Testing needed
- Sub-system name No development; set-up, and testing needed
- Sub-system name Testing needed

External

The external organizations impacted by this project include:

Third-Party Package name: New process and procedures; development, testing needed

Business Impacts

This project will have the following business impacts:

Changes for all <application name> customers
Changes for Wholesale Sales and Relationship Managers
Changes for Regional Managers
Changes for Operations
Changes for Central Implementation and Regional Implementation Centers

Business Benefits

{% if main.adsdop %}{% include 'adsenceinline.tpl' %}{% endif %}

This project will have the following business benefits:

Improved presentation of customer statements and reports
Productivity gains on automating various processes
Productivity gains on making specific data more readily available to analysts for problem resolution
Compliance with Corporate branding standards

Risks

Risk Rating

The risk score for this project is 82. As a result of the risk rating, this project has been rated as a medium-risk project. There is additional risk due to some of the requested changes to be implemented in conjunction with the release implementation date. There is a conflict between the release date and the upgrade date.

See Appendix P2: Risk Assessment form.

Identified Risks

The risks identified for this project include the following:

Late deliverables if resource constraints
Resource constraints if work needed on other higher priorities such as production issues
Retaining key project team resources
Conflicting project priorities
Communication, coordination, and task management of all impacted/affected applications are necessary for successful implementation
Risk of impacted customers due to the complexity of some changes

Risk Mitigation

The following actions will be taken to address the identified risks:

Hire contractors as necessary to assist the team in completing the assigned tasks .
Work with the Business Lines early in the requirements gathering phase to document detailed requirements.
More accurate estimates due to detailed business requirements.
Regularly scheduled meetings will be held to keep all impacted/affected applications up-to-date on tasks.
Include adequate checkpoint reviews in the project process to ensure accurate and complete information.
Testing will be coordinated with all impacted applications to ensure the changes are correct.