Project Management RAM Matrix Example

This assignment provides an example of a Responsibility Assignment Matrix (RAM) used in project management. It details the roles and responsibilities (R = Responsible; A = Accountable; C = Consulted; I = Informed) for various milestones within a project, including stakeholder signoff, project evaluation, long-term maintenance planning, documentation, and final completion. The RAM matrix helps visualize who is involved at each stage of the project lifecycle.

Project Scope Statement
Project Name Development of cloud based software for
accounting professionals
Project
Number
1
Project Manager Rashaad Taborn Prioritization High
Owner(s) Stakeholders
Statement of
Work—
Project
Description
and
Project
Product
The project deals with the development and implementation of cloud based
software system for managing the Abacus Data System’s data. The project
would allow easy management of data in computerized management of data
with the application proposed for reducing the technical errors. The project
deals with the development of advanced computerized software for the Abacus
Data System.
The proposed cloud based accounting system will be developed based in
Veeam Software for providing technical support and backup services.
Furthermore the system architecture will be developed using Intel.
Project
Deliverables
The significant deliverable for the undertaken project is to complete the
undertaken accounting system development project within the allocated
budget and time by Abacus Data System. For achieving the deliverables,
appropriate software and hardware platform needs to be developed. In
addition to that, other appropriate deliverables identified for the project
includes project initiations, project planning, project development, project
testing, project execution and project closure phase.
Project
Objectives
The project for accounting software system implementation needs to be
developed within the allocated budget of $75,000.00;
The proposed system design and implementation for the computerized
accounting system within the allocated time period of nine months;
The developed accounting system for the company would be able to
significantly reduce the errors in the manual computation of the accounting
information;
Project
Assumptions
The following are the detailed assumptions considered for completing the
accounting system implementation:
 For the system, development center and office has been considered for
system implementation;
 The project also includes the development of communication and

network infrastructure;
 The functional and operational background of the company has been
analyzed;
 Proper development ambiance and software platform needs to be used
in this project;
 All the business strategies are considered for the development of the
anointing software;
Project
Constraints
The following the significant constraints that has been followed for completing
the integration of the accountancy software system:
 The project needs to be completed within the 9 months of time period;
 The development of the system needs to be completed within the allocated
financial budget of $75,000.00;
 The scope of the project for implementing the accounting software
development;
Exclusions Various factors and criteria in this project have been eliminated for completion.
Several exclusion identified for the development of the accounting software
includes:
 The project does not includes hiring of new employees or project team
members for implementation of the technical parts;
 The development of company specification during the implementation of the
accounting software;
 Training of the employees of Abacus Data System for the use proposed
cloud based accounting system was not included within the project;
Acceptance
Criteria
For the success of undertaken project, various criteria or factors need to be
achieved as follows:
 The developed cloud based accounting system should be commercially
success;
 The project should be completed within allocated budget and time
schedule;
 The clients are satisfied with the developed system and performance;
 Appropriate communication tools and safety procedure needs to be
followed during the project development;
Technical
Requirements
The technical requirement for the development of the computerized
accounting system includes the following:
 The system would be able to eliminate technical failures and manual errors
occurred in the system;
 The system will be implemented using cloud computing technology;

 The system will be able to improve the security concern for the data
stored;
 The software design architecture will be developed using Intel;
APPROVALS
Type Name Signature Date
Project Manager Approval:
Customer/Sponsor Approval:

2. Work Breakdown Structure
Schedule for cloud based
software development
Project initiation
Understanding the
details of cloud
based software
Understanding the
issues of accounting
companies
Feasibility testing
Identifying the
issues with
traditional system
Identification of
risks
Vendor selection
Project kick off
Specification on the
software
requirements
Milestone 1:
Completion of
project initiation
phase
Project planning
Budget estimation
Preparation of
software project
tender
Software
requirement
workshop
specification
Identification of
project stakeholders
Software design
entry
Time estimation for
the project
Adoption of
software
requirement
standard
Milestone 2:
Completion of
project planning
phase
Project development
Understanding the
details of software
architecture
Requirement
elicitation
Understanding
architectural view of
the system
Developing the
design view
Developing design
entity
Development of
quality matter
Development of
functional safety
management
Development of
system architecture
Milestone 3:
Completion of project
development phase
Project testing
Review project
requirement
Development of
Critical design
Developing test
planning
Review operational
activities
Design modeling
Coding
Quality control
User acceptance
criteria testing
Unit testing
Integration testing
Final field testing
Milestone 4:
Completion of
project testing
phase
Project execution
Process refinement
Program
implementation
Considering
options for data
capture resources
Program controlling
Approval process
development
SaaS plan form
incorporation
Milestone 5:
completion of
project execution
phase
Project closure
Stakeholder signoff
Prost project
evaluation
Long term
maintenance
planning
development
Final documentation
Milestone 6:
Completion of
project closure
phase
Figure 1: Work Breakdown Structure
(Source: Created by Author)
2.1. Activities and WBS Code
WBS Task Name
0 Schedule for cloud based software development
1 Project initiation
1.1 Understanding the details of cloud based software
1.2 Understanding the issues of accounting companies
1.3 Feasibility testing
1.4 Identifying the issues with traditional system
1.5 Identification of risks
1.6 Vendor selection
1.7 Project kick off
1.8 Specification on the software requirements
1.9 Milestone 1: Completion of project initiation phase
2 Project planning
2.1 Budget estimation
2.2 Preparation of software project tender
2.3 Software requirement workshop specification
2.4 Identification of project stakeholders

WBS Task Name
2.5 Software design entry
2.6 Time estimation for the project
2.7 Adoption of software requirement standard
2.8 Milestone 2: Completion of project planning phase
3 Project development
3.1 Understanding the details of software architecture
3.2 Requirement elicitation
3.3 Understanding architectural view of the system
3.4 Developing the design view
3.5 Developing design entity
3.6 Development of quality matter
3.7 Development of functional safety management
3.8 Development of system architecture
3.9 Milestone 3: Completion of project development phase
4 Project testing
4.1 Review project requirement
4.2 Development of Critical design
4.3 Developing test planning
4.4 Review operational activities
4.5 Design modeling
4.6 Coding
4.7 Quality control
4.8 User acceptance criteria testing
4.9 Unit testing
4.10 Integration testing
4.11 Final field testing
4.12 Milestone 4: Completion of project testing phase
5 Project execution
5.1 Process refinement
5.2 Program implementation
5.3 Considering options for data capture resources
5.4 Program controlling
5.5 Approval process development
5.6 SaaS plan form incorporation
5.7 Milestone 5: completion of project execution phase
6 Project closure
6.1 Stakeholder signoff
6.2 Prost project evaluation
6.3 Long term maintenance planning development

WBS Task Name
6.4 Final documentation
6.5 Milestone 6: Completion of project closure phase

3. Responsibility Assignment Matrix (RAM)
Ta
sk
ID Task Name
Fin
anc
e
Ma
nag
er
Ope
ratio
n
Man
ager
Pro
ject
Ma
nag
er
Proj
ect
Tea
m
Me
mb
ers
Bus
ines
s
Ana
lyst
Hr
Ma
nag
er
Pro
gra
m
Ana
lyst
Pr
oje
ct
Te
ste
r
Appli
cation
Progr
ammi
ng
Mana
ger
0
Schedule for cloud
based software
development
1 Project initiation
1.1
Understanding the
details of cloud based
software C R
1.2
Understanding the
issues of accounting
companies R
1.3 Feasibility testing R
1.4
Identifying the issues
with traditional system A R
1.5 Identification of risks R A
1.6 Vendor selection R
1.7 Project kick off R
1.8
Specification on the
software requirements C R
1.9
Milestone 1:
Completion of project
initiation phase R
2 Project planning
2.1 Budget estimation R
2.2
Preparation of software
project tender R C
2.3
Software requirement
workshop specification R I
2.4
Identification of project
stakeholders R I
2.5 Software design entry I R
2.6
Time estimation for the
project R
2.7
Adoption of software
requirement standard R C
2.8
Milestone 2:
Completion of project
planning phase R
3 Project development
3.1 Understanding the
details of software
R

Ta
sk
ID Task Name
Fin
anc
e
Ma
nag
er
Ope
ratio
n
Man
ager
Pro
ject
Ma
nag
er
Proj
ect
Tea
m
Me
mb
ers
Bus
ines
s
Ana
lyst
Hr
Ma
nag
er
Pro
gra
m
Ana
lyst
Pr
oje
ct
Te
ste
r
Appli
cation
Progr
ammi
ng
Mana
ger
architecture
3.2 Requirement elicitation R C
3.3
Understanding
architectural view of the
system R C
3.4
Developing the design
view I R
3.5
Developing design
entity R
3.6
Development of quality
matter R
3.7
Development of
functional safety
management R
3.8
Development of
system architecture R I
3.9
Milestone 3:
Completion of project
development phase R
4 Project testing
4.1
Review project
requirement A R
4.2
Development of Critical
design C R
4.3
Developing test
planning I R
4.4
Review operational
activities R C
4.5 Design modeling I R
4.6 Coding R
4.7 Quality control A
4.8
User acceptance
criteria testing R
4.9 Unit testing R
4.1 Integration testing R
4.1
1 Final field testing R
4.1
2
Milestone 4:
Completion of project
testing phase R
5 Project execution
5.1 Process refinement R

Ta
sk
ID Task Name
Fin
anc
e
Ma
nag
er
Ope
ratio
n
Man
ager
Pro
ject
Ma
nag
er
Proj
ect
Tea
m
Me
mb
ers
Bus
ines
s
Ana
lyst
Hr
Ma
nag
er
Pro
gra
m
Ana
lyst
Pr
oje
ct
Te
ste
r
Appli
cation
Progr
ammi
ng
Mana
ger
5.2
Program
implementation R
5.3
Considering options for
data capture resources R
5.4 Program controlling R I C
5.5
Approval process
development R A
5.6
SaaS plan form
incorporation I R
5.7
Milestone 5:
completion of project
execution phase R
6 Project closure
6.1 Stakeholder signoff R C
6.2
Prost project
evaluation R
6.3
Long term
maintenance planning
development R C
6.4 Final documentation R I
6.5
Milestone 6:
Completion of project
closure phase R
In the above RAM matrix, the following indicates R = Responsible; A = Accountable; C =
Consulted; I = Informed.

Bibliography
Browning, T. R. (2014). Managing complex project process models with a process architecture
framework. International Journal of Project Management, 32(2), 229-241.
Fleming, Q. W., & Koppelman, J. M. (2016, December). Earned value project management.
Project Management Institute.
Kerzner, H. (2017). Project management metrics, KPIs, and dashboards: a guide to measuring
and monitoring project performance. John Wiley & Sons.
Kerzner, H., & Saladis, F. P. (2017). Project management workbook and PMP/CAPM exam
study guide. John Wiley & Sons.
Larson, E. W., & Gray, C. (2013). Project Management: The Managerial Process with MS
Project. McGraw-Hill.
Mir, F. A., & Pinnington, A. H. (2014). Exploring the value of project management: linking
project management performance and project success. International journal of project
management, 32(2), 202-217.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.
Sharon, A., & Dori, D. (2015). A Project–product model–based approach to planning work
breakdown structures of complex system projects. IEEE Systems Journal, 9(2), 366-
376.
Snyder, C. S. (2014). A Guide to the Project Management Body of Knowledge: PMBOK (®)
Guide. Project Management Institute.
Too, E. G., & Weaver, P. (2014). The management of project management: A conceptual
framework for project governance. International Journal of Project Management, 32(8),
1382-1394.