Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Accountable (A): Role on project that should be able to explain or substantiate the logic or reason behind the deliverable
The one person to oversee the correct and thorough completion of the deliverable or task, and the one who delegates work to the Responsible. An Accountable must sign off (Approve) on the work that the Responsible provides. There must be only one Accountable specified for each task or deliverable.


Stage

Activity

Customer

iRely


Stage 1

 

BPR –

Solution Blueprint and Functional Design


The activities of the BPR (Business Process Review) are centered primarily on three aspects:


Create and establish:

Project team

Steering committee

Project charter

Clear measurable goals and objectives

AR

R

Project governance

Roles and responsibilities

Reporting requirements

AR

I

Data conversion strategy

Only open transactions (or full conversion)

Cutover strategy

Data will be provided in iRely formats for conversion

A

R

Business/Functional aspects of the project.  Areas of focus include:

Software Orientation for Project Team

System Review (on demo system)

Base function and setup

A

R

Conducting Business Analysis Sessions

Review Customer’s business flows

Use Case Design - Using a series of customer specific scenarios, the project team will demonstrate the system inputs, processes and outputs to illustrate the way the system will be utilized at go-live.


AR

R

Identifying Transaction Data, Reference Data and Security Profiles that will be required at Go-live (commence the compilation of such data)

Master Data

Open transactions

AR

C

Determining modifications to system, if any

Determining the End User Training Strategy

Determining the User Acceptance and Parallel Test Strategies (commence the compilation of the required scenarios and test cases) Preparing and Approving the BPR Document


AR

R

Determining the Deployment Strategy

AC

R

Business process re-engineering, if any


AR

R

Stage 2

 

Planning

Integration planning - Definition, design, specification of any intended integrations

AR

C

Create Detailed project plan based upon results of BPR stage

AR

R

Stage 3


System Configuration and Build


During this stage, our efforts are principally on two areas: Configure the standard solution and design/build new RICEFWs*. Specific steps are:


a.    Configuring set up data

b.    Loading and approving Reference Data & Security Profiles

A

R

c.     Configuring views to meet reporting requirements

A

R

d.    Detailed design, Coding, Review and Approval of Integrations between i21 and other systems

AR

R

e.     Loading and Configuring Integrations 

AR

R

f.     Detailed Design, Coding, Review and Approval of Modifications

AR

R

g.    Installing & Configuring Test & Production environments

*RICEFW - Reports, Interfaces, Conversions, Extensions, Forms and Workflow

A

R

Stage 4

 

Testing


During this stage, we will have a detailed execution of test plans. iRely will assist Customer by recording and sharing results that are required for Customer audit needs.

Execute standard Unit and Functional test scripts

AR

R

Execute Client Functional Test Plan & Evaluate results


AR

R

Stage 5


Training & UAT (User Acceptance Testing)

The UAT will provide validation to confirm and approve the production-ready environment:

Execute Key User Training (“Train the Trainers”)

Simulation of daily activities in i21

A

R

Execute Client User Acceptance Test Plan & evaluate results

There could be multiple rounds of UAT


AR

R

Stage 6

Parallel Testing

Execute Production Parallel Test Plan & Evaluate results

AR

R

Stage 7


Go-live and Hypercare

Activities include:

Go/No-Go Decision for Go-Live

AR

R

Cutover from Legacy Systems to i21 in Production Environment

A

R

Post Go-Live Support

AR

R

Transition to Support


AR

R

Stage 8

Ongoing Support

Ongoing support

AR

R

3. CUSTOMER RESPONSIBILITIES

...