RALS Project Management Plan

The provided text describes a structured approach to developing a project management plan for an RALS (likely Real-time Application Logging System) project. It emphasizes key evaluation criteria such as budget adherence, system design alignment with client requirements, feasible operations, and successful test results. The document includes references to relevant project management literature and outlines steps for analysis, planning, and implementation.

Running head: PROJECT MANAGEMENT
Project Management
Name of the Student:
Student ID:
Name of the University:
Author’s note:

1PROJECT MANAGEMENT
Table of Contents
1. Part One: MOV - Measurable Organisational Value...................................................................2
2. Part Two: Define Scope and produce a Scope Management Plan...............................................4
3. Part Three: Project Plan...............................................................................................................7
4. Part Four: Risk Analysis and Management Plan for RALS........................................................9
5. Part 5: Quality Management Plan..............................................................................................10
6. Project Closure...........................................................................................................................10
Bibliography..................................................................................................................................12

2PROJECT MANAGEMENT
1. Part One: MOV - Measurable Organisational Value
The MOV or Measurable Organisational Value is the analysis of the various factors like strategy,
financial, social, operational, and customers.
Rank Impact Description Metrics Timeframe
1 Financial The analysis of the financial
aspects would be implied for the
development factor for critical
evaluation of the transactions and
methods in RALS and Globex.
Revenue,
Annual
Turnover, and
Net Profit
13 weeks
2 Customer The organization has been helpful
for forming the development of the
operations with the support and
consideration of customers. It is
important for forming the
development of the improved
customer experience and
formation.
Feedbacks from
the customers
8 weeks
3 Operational The operations of the RALS
project would have to be included
for forming the analysis of the
functions and operations.
Management
Plan of
operations
14 weeks

3PROJECT MANAGEMENT
4 Strategy The strategies of the business
organization have been largely
helpful for the consideration of the
effective and smart functions.
Strategic
Analysis
Matrix
9 weeks
5 Social The deployment of the social and
influential management operations
would help in forming the
development of process flow
operations and organization.
Local Support
and
Government
help
7 weeks
 Better the system of ticketing for the RALS show would help in developing the
improved functions and development of the effective and improved operations.
 Faster the operations of RALS would be more efficient and it would tend to increase
the working speed with the help of ticketing system
 Cheaper the cost efficiency of the project is formed as the complete database is
integrated over a single network and it would help in forming the effective flow of
operations for the project
 Do more the system of ticketing developed would also serve the method of
communication for the RALS and Globex

4PROJECT MANAGEMENT
2. Part Two: Scope Evaluation and Plan Development for Scope Management
Scope Definition: The project scope is to imply the use of the project management skills and
process for developing the ticketing system for RALS or Riverina Agricultural and Lifestyle
Show and Globex.
Requirements:
Human Requirements Material Requirements
Project Manager
Investment Manager
Project Sponsor
System Analyst
System Developer
Risk Analyser
Business Analyst
System Tester
Computer Devices
Storage Media
Network Components
Raw Materials
Routers For Network Connection
Infrastructure

5PROJECT MANAGEMENT
In-scope and out of scope items of the project:
In-scope Out of scope
Project Plan
Budget Allocation
System Design
Implementation Plan
Change Management Schemes
Transportation Plan
Communication Plan
Deliverables of the project
The deliverables for the project include Budget Planning, Planning Schedule, System Design,
Complete System, Implementation, Equipments, Test Plan and result, Risk Assessment and
register, and Final Project report.
Acceptance Criteria
 Completion of the project in estimated budget and schedule
 System and its design as per client’s requirement
 Feasible Project Operations
 Expected test results
List of resources:

6PROJECT MANAGEMENT
Resource Usage
Project
Manager Investment
Manager Project
Sponsor System
Analyst System
Developer Risk
Analyzer Business
Analyst System
Tester
$0.00
$20,000.00
$40,000.00
$60,000.00
$80,000.00
$100,000.00
$120,000.00
$140,000.00
$160,000.00
$180,000.00
$153,600.00
$4,000.00 $18,240.00
$82,800.00
$52,800.00
$19,440.00 $15,200.00 $27,520.00
Cost
Cost

7PROJECT MANAGEMENT
3. Part Three: Project Plan
ID Task
Mode
WBS Task Name Duration Start Finish Predecessors
0 0 Development of Ticketing System for RALS 154 days Mon 1/1/18 Thu 8/2/18
1 1 Conceptuliation and proje ct initialization 29 days Mon 1/1/18 Thu 2/8/18
2 1.1 Developme nt of Project Charter 11 days Mon 1/1/18 Mon 1/15/18
3 1.1.1 Requirement Analysis 3 days Mon 1/1/18 Wed 1/3/18
4 1.1.2 Specification of Project is Evaluated 4 days Thu 1/4/18 Tue 1/9/18 3
5 1.1.3 Project Kick off meeting 4 days Wed 1/10/18 Mon 1/15/18 4
6 1.2 Vendor appointme nt 18 days Tue 1/16/18 Thu 2/8/18
7 1.2.1 Analysis of various vendors 4 days Tue 1/16/18 Fri 1/19/18 5
8 1.2.2 Capability analysis of vendors 5 days Mon 1/22/18 Fri 1/26/18 7
9 1.2.3 Budget Planning 5 days Mon 1/29/18 Fri 2/2/18 8
10 1.2.4 Planning Schedule 4 days Mon 2/5/18 Thu 2/8/18 9
11 1.2.5 Project is Initiated 0 days Thu 2/8/18 Thu 2/8/18 10
12 2 Ticketing system De sign Phase 22 days Fri 2/9/18 Mon 3/12/18
13 2.1 Labour Management is planned 4 days Fri 2/9/18 Wed 2/14/18 11
14 2.2 System Design is made 5 days Thu 2/15/18 Wed 2/21/18 13
15 2.3 Initiation is built 6 days Thu 2/22/18 Thu 3/1/18 14
16 2.4 Milestone Requirements are formed 7 days Fri 3/2/18 Mon 3/12/18 15
17 M1 Mile stone: De sign is complete d of the Ticket System0 days Mon 3/12/18Mon 3/12/1816
18 3 Implementation of the Ticke ting system 36 days Tue 3/13/18 Tue 5/1/18
19 3.1 Implemening system designed 10 days Tue 3/13/18 Mon 3/26/18 17
20 3.2 Implementation Phase modification 8 days Tue 3/27/18 Thu 4/5/18 19
21 3.3 Requirement of design implemented 9 days Fri 4/6/18 Wed 4/18/18 20
22 3.4 Equipments are verified 9 days Thu 4/19/18 Tue 5/1/18 21
23 M2 Mile stone: Impleme ntation is comple ted for Ticke ting Syste m0 days Tue 5/1/18 Tue 5/1/18 22
24 4 Testing phase 30 days Wed 5/2/18 Tue 6/12/18
25 4.1 Initiation of testing phase 5 days Wed 5/2/18 Tue 5/8/18 23
26 4.2 Reporting the testing phase 1 day Wed 5/9/18 Wed 5/9/18 25
27 4.3 Reviewing the testing Phase 8 days Thu 5/10/18 Mon 5/21/18 26
28 4.4 Entire plan is developed 7 days Tue 5/22/18 Wed 5/30/18 27
29 4.5 Test Plan is developed 9 days Thu 5/31/18 Tue 6/12/18 28
30 4.6 Test result in executed 0 days Tue 6/12/18 Tue 6/12/18 29
31 M3 Mile stone: Final test re sults are formed 0 days Tue 6/12/18 Tue 6/12/18 30
32 5 Risk Manageme nt Phase 33 days Wed 6/13/18Fri 7/27/18
33 5.1 Recognition of risk factors 5 days Wed 6/13/18 Tue 6/19/18 31
34 5.2 Risk Assessment 7 days Wed 6/20/18 Thu 6/28/18 33
35 5.3 Risk Mitigation 6 days Fri 6/29/18 Fri 7/6/18 34
36 5.4 Development of risk register 7 days Mon 7/9/18 Tue 7/17/18 35
37 5.5 Risk Impact is modified 8 days Wed 7/18/18 Fri 7/27/18 36
38 M4 Mile stone: Risk Manageme nt Plan is developed 0 days Fri 7/27/18 Fri 7/27/18 37
39 6 Project closure phase 4 days Mon 7/30/18Thu 8/2/18
40 6.1 Success Evaluation of project 2 days Mon 7/30/18 Tue 7/31/18 38
41 6.2 Final Project report is developed 2 days Wed 8/1/18 Thu 8/2/18 40
42 M5 Mile stone: Project is closed 0 days Thu 8/2/18 Thu 8/2/18 41
Project Manager
Business Analyst,Project Manager
Business Analyst,Project Manager,Project Sponsor
Project Manager,System Developer
Business Analyst,Project Manager
Investment Manager,Project Manager,Project Sponsor
Business Analyst,Project Manager
2/8
Project Manager
Project Manager,System Developer
Project Sponsor,System Analyst
Project Manager,System Analyst,System Developer
3/12
Project Manager,System Analyst
System Analyst,System Developer
Project Manager
System Analyst,System Developer,System Tester
5/1
System Developer,System Tester
System Developer,System Tester
System Analyst,System Tester
System Analyst,System Developer
System Developer,System Tester
6/12
6/12
Risk Analyzer,System Developer,System Tester
Project Manager,Risk Analyzer,System Analyst
Project Manager,System Developer,System Tester
Project Manager,Risk Analyzer,System Analyst
Project Manager,Risk Analyzer
7/27
Project Manager,Project Sponsor
Business Analyst,Project Manager,Project Sponsor
8/2
B M E B M E B
October March August January
WBS

8PROJECT MANAGEMENT
ID Task
Mode
WBS Task Name
0 0 Development of Ticketing System for RALS
1 1 Conceptuliation and project initialization
2 1.1 Development of Project Charter
3 1.1.1 Requirement Analysis
4 1.1.2 Specification of Project is Evaluated
5 1.1.3 Project Kick off meeting
6 1.2 Vendor appointment
7 1.2.1 Analysis of various vendors
8 1.2.2 Capability analysis of vendors
9 1.2.3 Budget Planning
10 1.2.4 Planning Schedule
11 1.2.5 Project is Initiated
12 2 Ticketing system Design Phase
13 2.1 Labour Management is planned
14 2.2 System Design is made
15 2.3 Initiation is built
16 2.4 Milestone Requirements are formed
17 M1 Milestone: Design is completed of the Ticket System
18 3 Implementation of the Ticketing system
19 3.1 Implemening system designed
20 3.2 Implementation Phase modification
21 3.3 Requirement of design implemented
22 3.4 Equipments are verified
23 M2 Milestone: Implementation is completed for Ticketing System
24 4 Testing phase
25 4.1 Initiation of testing phase
26 4.2 Reporting the testing phase
27 4.3 Reviewing the testing Phase
28 4.4 Entire plan is developed
29 4.5 Test Plan is developed
30 4.6 Test result in executed
31 M3 Milestone: Final test results are formed
32 5 Risk Management Phase
33 5.1 Recognition of risk factors
34 5.2 Risk Assessment
35 5.3 Risk Mitigation
36 5.4 Development of risk register
37 5.5 Risk Impact is modified
38 M4 Milestone: Risk Management Plan is developed
39 6 Project closure phase
40 6.1 Success Evaluation of project
41 6.2 Final Project report is developed
42 M5 Milestone: Project is closed
Project M
Busines
Busine
Projec
Busin
Inves
Busi
2/8
Pro
Pro
Pr
P
E
May

9PROJECT MANAGEMENT
4. Part Four: Risk Analysis and Management Plan for RALS
Risk management plan is developed in the excel sheet

10PROJECT MANAGEMENT
Stage 1: Identification of the quality issues
Stage 5: Reviewing the arrangement
Stage 4: Monitoring the actualized techniques
Stage 3: Development of alleviation techniques
Stage 2: Analysis of the quality issues and their effect on venture
5. Part 5: Quality Management Plan
6. Project Closure
Annotated Bibliography
“Getting it done: Critical success factors for project managers in virtual work settings”
As explained in this article by Verburg, Bosch-Sijtsema and Vartiainen (2013), there are several
factors that have impacted the success of project and it includes the factors like completion of the
project in estimated budget and schedule, system and its design as per client’s requirement,
feasible project operations, and expected test results.
“Information technology project management”

11PROJECT MANAGEMENT
The concept of project management would be helpful for integrating the development of the
project operations. The analysis of the project consideration would help in critical evaluation of
the project integration management. The formation of the processes would help in formation of
the project budget and schedule.
Checklist for RALS project
Evaluation Criteria
 Completion of the project in estimated budget and schedule
 System and its design as per client’s requirement
 Feasible Project Operations
 Expected test results

12PROJECT MANAGEMENT
Bibliography
Amrollahi, A., Ghapanchi, A. H., &Talaei-Khoei, A. (2014). Three decades of research on
strategic information system plan development.Communications of the Association for
Information Systems, 34(1), 84.
Braglia, M., &Frosolini, M. (2014).An integrated approach to implement project management
information systems within the extended enterprise.International Journal of Project
Management, 32(1), 18-29.
Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management.
Cengage Learning.
Galliers, R. D., &Leidner, D. E. (2014). Strategic information management: challenges and
strategies in managing information systems. Routledge.
Garton, C., & McCulloch, E. (2012). Fundamentals of Technology Project Management. MC
Press, LLC.
Goetsch, D. L., & Davis, S. B. (2014). Quality management for organizational
excellence.pearson.
Hubicki, M. (2014). Risk Management Plan.
Kendrick, T. (2015). Identifying and managing project risk: essential tools for failure-proofing
your project. AMACOM Div American Mgmt Assn.
Nanda, V. (2016). Quality management system handbook for product development
companies.CRC Press.

13PROJECT MANAGEMENT
Pritchard, C. L., & PMP, P. R. (2014). Risk management: concepts and guidance. CRC Press.
Schwalbe, K. (2015). Information technology project management.Cengage Learning.
Stark, J. (2015). Product lifecycle management.In Product Lifecycle Management (pp. 1-
29).Springer International Publishing.
Verburg, R. M., Bosch-Sijtsema, P., &Vartiainen, M. (2013).Getting it done: Critical success
factors for project managers in virtual work settings.International Journal of Project
Management, 31(1), 68-79.
Verzuh, E. (2015). The fast forward MBA in project management.John Wiley & Sons.

14PROJECT MANAGEMENT
Appendix I
633800.mpp

15PROJECT MANAGEMENT
Appendix II
633800_risk.xlsx