Creating a Project Schedule
UNIT IV COURSE PROJECT 1
UNIT IV COURSE PROJECT 1
Unit IV Course Project
Student Name
Running head: UNIT IV COURSE PROJECT 1
Institution
Responsibility Assignment Matrix (RAM)
Responsibility Assignment Matrix (RAM) employs the work breakdown structure (WBS) and the organization technique to turn deliverables and functions into resources. Ram gives the real pictorial of the resources necessary for a project and evaluate whether the resources available are enough. In a RAM, deliverables are allocated a responsible person who will look at them and add input and the necessary administrative authority highlighted (Gido, Clements, & Baker, 2018).
Responsibility Assignment Matrix
|
Items |
Stakeholders |
|||||
|
|
Project Manager
|
Advisor
|
Website Designer
|
Software Engineer
|
Tester
|
Accountant
|
|
Identify key stakeholders |
A |
C |
- |
- |
- |
- |
|
Integration management |
R |
C |
- |
- |
- |
- |
|
Scope management |
R |
C |
I |
I |
I |
I |
|
Time management |
|
|
|
|
|
|
|
Cost management |
A |
I |
- |
- |
- |
R |
|
Quality management |
I |
R |
I |
I |
I |
- |
|
Human resource management |
R |
C |
I |
I |
I |
I |
|
Communications management |
A |
I |
R |
R |
R |
R |
|
Risk management |
I |
C |
R |
R |
R |
- |
|
Define requirements |
C |
C |
R |
R |
R |
- |
|
Create web site |
A |
C |
R |
R |
- |
- |
|
Testing |
A |
I |
- |
- |
R |
- |
|
Roll – out |
A |
R |
I |
I |
I |
I |
|
Support |
A |
- |
R |
R |
- |
- |
|
Close-out |
A |
I |
R |
R |
R |
R |
We employed RACI structure
Responsible: owner, the individual who owns the work. Every activity has to have the owner.
Approval: the individual who approved the deliverable (only one individual).
Consulted: the individual who delivers the information needed in work.
Informed: an individual that requires to be informed of the progress of the work.
Project Charter
A project charter is an official project authorization that records the general understanding of project’s scope, development, and objectives while also showing the duties and responsibilities of every member taking part (Maenhout, & Vanhoucke, 2017).
|
Project Charter |
|||
|
Project Name |
|
||
|
Project Sponsor |
ABC organization |
Project Manger |
James Bond |
|
Date of Project Approval |
19 April 2020 |
Last Revision Date |
|
|
Project Description |
Introduction of a new software |
||
|
Scope |
The new software product will be introduced to help the sales team in taking orders and also ensure that no order is missed. Thus, this software is categorically designed for the sales team. |
||
|
Business Case |
To boost the organization sales by at least 30% |
||
|
Constraints (in priority order) |
Time |
Six months |
|
|
|
Budget |
Six developers+ two sales team rep |
|
|
|
Scope |
TBD |
|
|
|
Quality |
Prioritize time & budget over quality |
|
|
Project Deliverables |
The new software will assist the sales team in sales, training, as well as operations within the 1st two months |
||
|
Benefits |
KPI |
Baseline |
Goal |
|
|
Orders per sales person pd |
30 |
34 |
|
|
Unhandled calls pd |
21 |
0 |
|
|
Customer satisfaction |
28 |
38 |
|
Steering committee |
CEO |
|
Sales Representatives |
|
|
|
|
Programmers |
|
|
ICT manager |
|
|
|
|
Sales Director |
|
|
|
Key Stakeholders |
Name |
Success criteria |
|
|
|
|
|
|
|
|
|
|
|
|
Risks |
|
3. Quality Plan
A quality plan is a documentation which highlights quality standards, practices, resources, specifications, as well as the occurrence of the crucial actions in a given project. In this case our quality plan is as follows:
1. Purpose
The purpose of the plan is to define the new software, enhance quality assurance of the organization, define tasks and duties of each member of the team, give the standards and practices employed in carrying out quality assurances activities.
2. Scope
The plan sets quality assurance activities carried out throughout the project life cycle. The plan shows the QA functions is in the process of the project. It shows that the quality assurance team has a reporting channel to the management team that does not depend on the project manager, the project systems and software engineering groups. The aim of the QA program is to ensure that the software meets all the technical requirements
3. Identification
This part involves the configuration items, project processes, products, tools, facilities etc. from the relevant documents to which quality assurance plan will apply or provide list in this section.
4. System Overview
The new software is aimed at improving the sales of our organization. it provides a platform where customers can place orders and the order be processed by the sales team as fast as possible.
5. Document Overview
This document contains crucial information that would be important in carrying out activities related to the project. It contains information such as; quality assurance in design, development, production, execution, as well as maintenance (Steinman, 2017).
References
Gido, J., Clements, J. P., & Baker, R. (2018). Successful project management (7th ed.). Boston, MA: Cengage Learning.
Maenhout, B., & Vanhoucke, M. (2017). A resource type analysis of the integrated project scheduling and personnel staffing problem. Annals of Operations Research, 252(2), 407–433. Retrieved from https://libraryresources.columbiasouthern.edu/login?url=http://search.ebscohost.com/login.aspx?direct=true&db=bsu&AN=122783079&site=ehost-live&scope=site
Steinman, J. (2017). Defining and measuring project quality. Control Engineering, 64(5), 46–48. Retrieved from https://libraryresources.columbiasouthern.edu/login?url=http://search.ebscohost.com/login.aspx?direct=true&db=bsu&AN=123237807&site=ehost-live&scope=site