Professional Documents
Culture Documents
Purpose
Use the Request for Change document to document and approve project changes. Always include the
project and business impact.
PROJECT/PHASE IDENTIFICATION
CHANGE DESCRIPTION
Change Number Priority Project Phase
< Indicates the impact of this change <The Project Phase that this change
on the project> applies to>
Benefits or Reasons for Change: < Specify benefits of the change >
CUSTOMER
SAP Business One Accelerated Implementation Program Request for Change
IMPACTS
Factor Description
Scope <How does this change affect scope? >
Schedule <How does this change affect the project schedule? Describe any major milestone
target date modifications or if the end date of the schedule has changed. >
Resources < Are additonal resources needed? Define the staff needs or other resources required
for this change. >
Budget <Are there costs involved? Identify projected financial consequences of making the
change. Estimate cost differentials as precisely as possible. >
Assumptions <List any business and/or technical assumptions for this change.>
Impact of not <List the impact to the project if this change is not made. >
doing the
change
Other <State any other factors, such as impact on other interrelated projects. >
RECOMMENDED ACTION
▪ <List the action steps needed to carry out the change. >
▪
Project Owner
© SAP AG 2011 2