Oracle Policy Automation
Project Name
Project Set-Up
This document has been provided as a guide to some of the decisions you may need to make when
establishing a successful Oracle Policy Automation project. You should add and remove detail as
relevant to your project and you may need to split the content into several documents, depending on
the audience for each.
Version Error! Unknown document property name.
Page 1 o
People and Communication
Team Profile
The following people will make up the project team:
Name
Role(s)
Project Manager
Lead Policy Modeler
Policy Modeler
Developer
Tester
Subject Matter Expert
Stakeholder Profile
<Key Stakeholder Name>
Description
Expectations
Goals and
priorities
Driving
requirements
Tolerance for risk
Other Stakeholders
Stakeholder
Interest in project
Version Error! Unknown document property name.
Page 2 o
Communications Plan
Reports
Report Type
Submitted To
Regularity
Attendees
Regularity
Weekly Progress Report
Testing report
Meetings
Meeting Type
Team meeting
Stakeholder review
Responsibilities
The person responsible for managing project risk, budget and timing is: Insert name
The person responsible for managing policy model quality is: Insert name
The person responsible for making the final decision on any policy interpretation / scoping /
functionality is: Insert name
The person for signing off that the project is complete / acceptable is: Insert name
Version Error! Unknown document property name.
Page 3 o
Infrastructure and Logistics
Software
The following software will be required to develop the project:
Software Name
Version
Location / details
for installing
Oracle Policy Automation
File Storage and Backup
The project files will be stored ….
A copy of development files will be stored …..
<Insert details of backup plan>
Development Location
Development will take place at …
Test Location
Testing will take place at …
Issue Management
The process for managing issues identified during development and testing is…
Production Installation
The solution will be installed by ...
Users of the system will access the system by …
Version Error! Unknown document property name.
Page 4 o
Deliverables and Success
Background
<Insert any relevant background information >
Vision Statement
The vision for this project is to deliver...
Scope and Requirements
The agreed scope and requirements for the project are documented in ....
Assumptions, Dependencies and Constraints
The following assumptions have been made...
Project Success Factors
The success factors for the project are:

<Success factor 1>: can be measured by <insert measure>

<Success factor 2>: can be measured by <insert measure>

<Success factor 3>: can be measured by <insert measure>
Deliverables
This project will deliver the following in version 1.0:
Deliverable
Acceptance Criteria
<Deliverable 1>
Verified as being acceptable by <insert acceptance
criteria>
<Deliverable 2>
Verified as being acceptable by <insert acceptance
criteria>
Delivery Schedule
The project will deliver version 1.0 on <insert delivery date>.
Version Error! Unknown document property name.
Page 5 o