Project Management Plan Development

This assignment delves into the creation of a comprehensive project management plan. It outlines key elements such as project scope definition, task identification and sequencing, scheduling techniques, risk management strategies, and an evaluation plan to assess project success. The document emphasizes utilizing computer-aided tools for effective management and control.

Running head: PROJECT MANAGEMENT METHODOLOGIES
Project Management Methodologies: Assessment 3
Name of the Student
Name of the University
Author’s Note

1PROJECT MANAGEMENT METHODOLOGIES
Table of Contents
1. Part One: MOV – Measurable Organizational Value..................................................................2
2. Part Two: Scope and Scope Management Plan...........................................................................3
3. Part Three: Activity Scheduling..................................................................................................5
4. Part Four: Project Risk Analysis and Plan.................................................................................11
5. Part Five: Quality Management Plan.........................................................................................12
6. Part Six: Annotated Bibliography: Closure and Evaluation......................................................13
6.1 Annotated Bibliography.......................................................................................................13
6.2 Closure checklist..................................................................................................................14
6.3 Evaluation Plan....................................................................................................................14
Bibliography..............................................................................................................................15

2PROJECT MANAGEMENT METHODOLOGIES
1. Part One: MOV – Measurable Organizational Value
The Measurable Organizational Value is the study for the various areas of impact for the
development of the project of RALS for the factors of strategy, customer, financial, operational,
and social. The online ticket system is helpful for forming the analysis of the project for these
factors.
Ran
k
Factor Description Time
Frame
1st Financial The project of RALS includes the formation of the appropriate
development factor for forming the inclusion of the effective and
appropriate management of the project in terms of money and
development.
54 days
2nd Customer The influence of the customers is very significant for the
continuation of the project operations. The RALS project would
be helpful for continuing the development of the appropriate and
significant development of the project operations.
89 days
3rd Strategy The strategic development of the RALS project would comprise
of forming the analysis of the significant development of the
system integration and development.
73 days
4th Operational The operational development would be implied for forming the
analysis of the effective and improved operations. The project of
RALS would be implied for forming the development of the
effective processing methods.
115
days
5th Social The social support for the project of RALS would be helpful for
developing the effective processing of the operations and
communication.
140
days
Table 1: MOV analysis
(Source: Created by the Author)
Summary MOV: In view of RALS perspective and Globex prerequisites, the
undertaking is relied upon to bring better and speedier incentive for the association. The
customer required to enhance the current ticket deal process with executing on the web ticket
deal process. Besides, the customer requires speedier and more effectiveness in ticket deals with
swarm administration without postponing the tickets.The venture will be fruitful if each partner
can accomplish 110% of workload in every month, complete work before arranged date and

3PROJECT MANAGEMENT METHODOLOGIES
following a half year, if the result gives over 70% ROI; the undertaking has wanted region of
enthusiasm as Operational, Customer, Social, Strategy, and Financial and it can bring 'better' and
'quicker' esteem for the association.
2. Part Two: Scope and Scope Management Plan
Scope of the project: Scope of the project is to grow new online ticket booking and deal
process with the goal that postponement in lines, swarm administration issues can be settled. The
online ticket deal framework ought to be operational to perform robotized ticketing framework.
In Scope Out Scope
Project Plan
Risk Management
System Design
System Implementation Plan
Cost Analysis
Transportation
Raw Materials
Contractor activities
Table 2: In scope and Out Scope items
(Source: Created by the Author)
Resources of the project: The resources of the project is given in the table below,
Human Resource Name Role Initials
Sainath Project manager PM
Santosh Reddy Sripaathi Business analyst BA
Surya Teja Penugonda Technical lead TL
Vinay Reddy Developer 1 D1
Victor Janes Developer 2 D2
Emily Stark Frontend developer FD
Jonathan Pete Lead analyst LA

4PROJECT MANAGEMENT METHODOLOGIES
Grace Haslam Tester T
Table 3: Human Resources of the project
(Source: Created by the Author)
Resource Usage
Resource Name Work Duration
Sainath (Project Manager) Resource Accumulation 40 hrs
Signing off the documents 8 hrs
Review of plan 16 hrs
Kick off meeting 8 hrs
Stakeholder Management 32 hrs
Signing off the documents 8 hrs
Project is closed 8 hrs
Santosh Reddy Sripaathi (Business Analyst) Requirement Analysis 24 hrs
Budgeting 16 hrs
Plan outline 24 hrs
Plan completion 40 hrs
Surya Teja Penugonda (Technical Lead) Implementing the design 56 hrs
Functional Design 120 hrs
Quality Assessment 48 hrs
Vinay Reddy (Developer 1) Administration management 32 hrs
User Interface is designed 80 hrs
Victor Janes (Developer 2) Coding and Programming the
system 160 hrs
System Modification 96 hrs
Emily Stark (Frontend developer) Charter Development 24 hrs

5PROJECT MANAGEMENT METHODOLOGIES
Project Initiation Documents 32 hrs
Submission of documents 16 hrs
Contract Development 24 hrs
Submission of documents 8 hrs
Jonathan Pete (Lead Analyst) Scope Determination 32 hrs
Selection of plan methodology 24 hrs
Cost Management 16 hrs
Final Documentation 56 hrs
Performance Appraisal 40 hrs
Grace Haslam (Tester) Black box testing 40 hrs
White box testing 40 hrs
UX testing 40 hrs
Prototype Testing 40 hrs
Testing results are formed 24 hrs
Table 4: Resource Usage
(Source: Created by the Author)
3. Part Three: Activity Scheduling
The System Development for RALS project has been scheduled as following,
WBS Task Name Duration Start Finish Predecessor
s Resource Names
0 System Development for
RALS project
159
days
Thu
2/1/18
Tue
9/11/18
1 Initialization Phase 22 days Thu
2/1/18
Fri
3/2/18
1.1 Charter Development 3 days Thu
2/1/18
Mon
2/5/18 Emily Stark

6PROJECT MANAGEMENT METHODOLOGIES
1.2 Scope Determination 4 days Tue
2/6/18 Fri 2/9/18 2 Jonathan Pete
1.3 Resource Accumulation 5 days Mon
2/12/18
Fri
2/16/18 3 Sainath
1.4 Requirement Analysis 3 days Mon
2/19/18
Wed
2/21/18 4 Santosh Reddy
Sripaathi
1.5 Project Initiation
Documents 4 days Thu
2/22/18
Tue
2/27/18 5 Emily Stark
1.6 Submission of
documents 2 days Wed
2/28/18
Thu
3/1/18 6 Emily Stark
1.7 Signing off the
documents 1 day Fri 3/2/18 Fri 3/2/18 7 Sainath
2 Plan Phase 17 days Mon
3/5/18
Tue
3/27/18
2.1 Selection of plan
methodology 3 days Mon
3/5/18
Wed
3/7/18 8 Jonathan Pete
2.2 Cost Management 2 days Thu
3/8/18 Fri 3/9/18 10 Jonathan Pete
2.3 Budgeting 2 days Mon
3/12/18
Tue
3/13/18 11 Santosh Reddy
Sripaathi
2.4 Plan outline 3 days Wed
3/14/18
Fri
3/16/18 12 Santosh Reddy
Sripaathi
2.5 Review of plan 2 days Mon
3/19/18
Tue
3/20/18 13 Sainath
2.6 Plan completion 5 days Wed
3/21/18
Tue
3/27/18 14 Santosh Reddy
Sripaathi
3 Implementation Phase 75 days Wed
3/28/18
Tue
7/10/18
3.1 Implementing the design 7 days Wed
3/28/18
Thu
4/5/18 15 Surya Teja
Penugonda
3.2 Kick off meeting 1 day Fri 4/6/18 Fri 4/6/18 17 Sainath
3.3 Administration 4 days Mon Thu 18 Vinay Reddy

7PROJECT MANAGEMENT METHODOLOGIES
management 4/9/18 4/12/18
3.4 User Interface is
designed 10 days Fri
4/13/18
Thu
4/26/18 19 Vinay Reddy
3.5 Functional Design 15 days Fri
4/27/18
Thu
5/17/18 20 Surya Teja
Penugonda
3.6 Coding and
Programming the system 20 days Fri
5/18/18
Thu
6/14/18 21 Victor Janes
3.7 System Modification 12 days Fri
6/15/18
Mon
7/2/18 22 Victor Janes
3.8 Quality Assessment 6 days Tue
7/3/18
Tue
7/10/18 23 Surya Teja
Penugonda
4 Testing Phase 23 days Wed
7/11/18
Fri
8/10/18
4.1 Black box testing 5 days Wed
7/11/18
Tue
7/17/18 24 Grace Haslam
4.2 White box testing 5 days Wed
7/18/18
Tue
7/24/18 26 Grace Haslam
4.3 UX testing 5 days Wed
7/25/18
Tue
7/31/18 27 Grace Haslam
4.4 Prototype Testing 5 days Wed
8/1/18
Tue
8/7/18 28 Grace Haslam
4.5 Testing results are
formed 3 days Wed
8/8/18
Fri
8/10/18 29 Grace Haslam
5 Project Closure Phase 22 days Mon
8/13/18
Tue
9/11/18
5.1 Final Documentation 7 days Mon
8/13/18
Tue
8/21/18 30 Jonathan Pete
5.2 Stakeholder Management 4 days Wed
8/22/18
Mon
8/27/18 32 Sainath
5.3 Contract Development 3 days Tue
8/28/18
Thu
8/30/18 33 Emily Stark
5.4 Performance Appraisal 5 days Fri Thu 34 Jonathan Pete

8PROJECT MANAGEMENT METHODOLOGIES
8/31/18 9/6/18
5.5 Submission of
documents 1 day Fri 9/7/18 Fri 9/7/18 35 Emily Stark
5.6 signing off the
documents 1 day Mon
9/10/18
Mon
9/10/18 36 Sainath
5.7 Project is closed 1 day Tue
9/11/18
Tue
9/11/18 37 Sainath
Table 5: Project Schedule
(Source: Created by the Author)
Gantt chart for the project of System Development for RALS project is given below,

9PROJECT MANAGEMENT METHODOLOGIES
ID Task
Mode
WBS Task Name Duration Start Finish Predecessors
0 0 System Development for RALS project159 days Thu 2/1/18 Tue 9/11/18
1 1 Initialization Phase 22 days Thu 2/1/18 Fri 3/2/18
2 1.1 Charter Development 3 days Thu 2/1/18 Mon 2/5/18
3 1.2 Scope Determination 4 days Tue 2/6/18 Fri 2/9/18 2
4 1.3 Resource Accumulation 5 days Mon 2/12/18 Fri 2/16/18 3
5 1.4 Requirement Analysis 3 days Mon 2/19/18 Wed 2/21/18 4
6 1.5 Project Initiation Documents 4 days Thu 2/22/18 Tue 2/27/18 5
7 1.6 Submission of documents 2 days Wed 2/28/18 Thu 3/1/18 6
8 1.7 Signing off the documents 1 day Fri 3/2/18 Fri 3/2/18 7
9 2 Plan Phase 17 days Mon 3/5/18 Tue 3/27/18
10 2.1 Selection of plan methodology3 days Mon 3/5/18 Wed 3/7/18 8
11 2.2 Cost Management 2 days Thu 3/8/18 Fri 3/9/18 10
12 2.3 Budgeting 2 days Mon 3/12/18 Tue 3/13/18 11
13 2.4 Plan outline 3 days Wed 3/14/18 Fri 3/16/18 12
14 2.5 Review of plan 2 days Mon 3/19/18 Tue 3/20/18 13
15 2.6 Plan completion 5 days Wed 3/21/18 Tue 3/27/18 14
16 3 Implementation Phase 75 days Wed 3/28/18 Tue 7/10/18
17 3.1 Implementing the design 7 days Wed 3/28/18 Thu 4/5/18 15
18 3.2 Kick off meeting 1 day Fri 4/6/18 Fri 4/6/18 17
19 3.3 Administration management 4 days Mon 4/9/18 Thu 4/12/18 18
20 3.4 User Interface is designed 10 days Fri 4/13/18 Thu 4/26/18 19
21 3.5 Functional Design 15 days Fri 4/27/18 Thu 5/17/18 20
22 3.6 Coding and Programming the system20 days Fri 5/18/18 Thu 6/14/18 21
23 3.7 System Modification 12 days Fri 6/15/18 Mon 7/2/18 22
24 3.8 Quality Assessment 6 days Tue 7/3/18 Tue 7/10/18 23
25 4 Testing Phase 23 days Wed 7/11/18 Fri 8/10/18
26 4.1 Black box testing 5 days Wed 7/11/18 Tue 7/17/18 24
27 4.2 White box testing 5 days Wed 7/18/18 Tue 7/24/18 26
28 4.3 UX testing 5 days Wed 7/25/18 Tue 7/31/18 27
29 4.4 Prototype Testing 5 days Wed 8/1/18 Tue 8/7/18 28
30 4.5 Testing results are formed 3 days Wed 8/8/18 Fri 8/10/18 29
31 5 Project Closure Phase 22 days Mon 8/13/18 Tue 9/11/18
32 5.1 Final Documentation 7 days Mon 8/13/18 Tue 8/21/18 30
33 5.2 Stakeholder Management 4 days Wed 8/22/18 Mon 8/27/18 32
34 5.3 Contract Development 3 days Tue 8/28/18 Thu 8/30/18 33
35 5.4 Performance Appraisal 5 days Fri 8/31/18 Thu 9/6/18 34
36 5.5 Submission of documents 1 day Fri 9/7/18 Fri 9/7/18 35
37 5.6 signing off the documents 1 day Mon 9/10/18 Mon 9/10/18 36
38 5.7 Project is closed 1 day Tue 9/11/18 Tue 9/11/18 37
Emily Stark
Jonathan Pete
Sainath
Santosh Reddy Sripaathi
Emily Stark
Emily Stark
Sainath
Jonathan Pete
Jonathan Pete
Santosh Reddy Sripaathi
Santosh Reddy Sripaathi
Sainath
Santosh Reddy Sripaathi
Surya Teja Penugonda
Sainath
Vinay Reddy
Vinay Reddy
Surya Teja Penugonda
Victor Janes
Victor Janes
Surya Teja Penugonda
Grace Haslam
Grace Haslam
Grace Haslam
Grace Haslam
Grace Haslam
Jonathan Pete
Sainath
Emily Stark
Jonathan Pete
Emily Stark
Sainath
Sainath
T S W S T M F T S W S T M F T S W S T M F T S W S T M
Jan 14, '18 Feb 11, '18 Mar 11, '18 Apr 8, '18 May 6, '18 Jun 3, '18 Jul 1, '18 Jul 29, '18 Aug 26, '18 Sep 23, '18 Oct 21, '18
Figure 1: Gantt chart for the project
(Source: Created by author)
Work Breakdown Structure for the project of System Development for RALS project is
given below,

10PROJECT MANAGEMENT METHODOLOGIES
0
System Development
for RALS project
1
Initialization Phase
1.1
Charter Development
1.2
Scope Determination
1.3
Resource Accumulation
1.4
Requirement Analysis
1.5
Project Initiation
Documents
1.6
Submission of
documents
1.7
Signing off the
documents
2
Plan Phase
2.1
Selection of plan
methodology
2.2
Cost Management
2.3
Budgeting
2.4
Plan outline
2.5
Review of plan
2.6
Plan completion
3
Implementation Phase
3.1
Implementing the
design
3.2
Kick off meeting
3.3
Administration
management
3.4
User Interface is
designed
3.5
Functional Design
3.6
Coding and
Programming the
system
3.7
System Modification
3.8
Quality Assessment
4
Testing Phase
4.1
Black box testing
4.2
White box testing
4.3
UX testing
4.4
Prototype Testing
4.5
Testing results are
formed
5
Project Closure Phase
5.1
Final Documentation
5.2
Stakeholder
Management
5.3
Contract Development
5.4
Performance Appraisal
5.5
Submission of
documents
5.6
signing off the
documents
5.7
Project is closed
0
1
2345678
9
101112131415
16
1718192021222324
25
2627282930
31
32333435363738
159 days 0%
2/1/18 9/11/18
22 days 0%
2/1/18 3/2/18
3 days 0%
2/1/18 2/5/18
4 days 0%
2/6/18 2/9/18
5 days 0%
2/12/18 2/16/18
3 days 0%
2/19/18 2/21/18
4 days 0%
2/22/18 2/27/18
2 days 0%
2/28/18 3/1/18
1 day 0%
3/2/18 3/2/18
17 days 0%
3/5/18 3/27/18
3 days 0%
3/5/18 3/7/18
2 days 0%
3/8/18 3/9/18
2 days 0%
3/12/18 3/13/18
3 days 0%
3/14/18 3/16/18
2 days 0%
3/19/18 3/20/18
5 days 0%
3/21/18 3/27/18
75 days 0%
3/28/18 7/10/18
7 days 0%
3/28/18 4/5/18
1 day 0%
4/6/18 4/6/18
4 days 0%
4/9/18 4/12/18
10 days 0%
4/13/18 4/26/18
15 days 0%
4/27/18 5/17/18
20 days 0%
5/18/18 6/14/18
12 days 0%
6/15/18 7/2/18
6 days 0%
7/3/18 7/10/18
23 days 0%
7/11/18 8/10/18
5 days 0%
7/11/18 7/17/18
5 days 0%
7/18/18 7/24/18
5 days 0%
7/25/18 7/31/18
5 days 0%
8/1/18 8/7/18
3 days 0%
8/8/18 8/10/18
22 days 0%
8/13/18 9/11/18
7 days 0%
8/13/18 8/21/18
4 days 0%
8/22/18 8/27/18
3 days 0%
8/28/18 8/30/18
5 days 0%
8/31/18 9/6/18
1 day 0%
9/7/18 9/7/18
1 day 0%
9/10/18 9/10/18
1 day 0%
9/11/18 9/11/18
Figure 2: WBS chart for the project
(Source: Created by author)

11PROJECT MANAGEMENT METHODOLOGIES
4. Part Four: Project Risk Analysis and Plan
Risk Analysis and Plan for hazard administration approach has been taken for keeping up
chance of alternative moderation process. The risks are distinguished in view of some specific
suppositions;
a. Firstly, the MOV will be affirmed from organization and overseeing expert
b. Secondly, the undertaking will be finished before the arranged date
c. Thirdly, the undertaking will be finished inside designated spending plan
d. Finally, the partners and representatives does not require preparing for working in
new framework
Risk Management Plan: In view of the situation of project sanction, MOV, and
suppositions; a few dangers are distinguished, dissected, and certain relief design is recognized.
The recognized dangers are specified essentially;
Budget risk: The project has some specific possibilities or propensities of invading the
assigned spending plan. Along these lines, the overseeing specialist ought to consider possibility
making arrangements for changing spending plan amid project course of events. This hazard is
considered as having disastrous seriousness however it has high probability. Thusly, the
alleviation design ought to be planned in higher need.
Timeline risk: The project may not be finished before the arranged date; may require
some additional weeks or month. In this way, the undertaking supervisor needs to consider
additional slack for the whole project to finish with all expectations. This hazard is considered as
having medium seriousness however it has medium probability. In this manner, the relief design
ought to be detailed in medium need.

12PROJECT MANAGEMENT METHODOLOGIES
Approval of MOV: The MOV may not be affirmed; it is needy over administration
choice. In the event that they think that its hard to meet MOV prerequisites in light of time, cash
and asset terms; they can deny the MOV. In this circumstance, the project needs to begin once
more with new MOV archive readiness. This hazard is considered as having practically certain
seriousness however it has low probability. Thusly, the moderation design ought to be planned in
low need.
Training requirements: The current partners and representatives in RALS require some
days preparing for working in the new framework. Hence, some additional cost ought to be spent
with respect to this plan. This hazard is considered as having medium seriousness however it has
low probability. Accordingly, the improvement design ought to be defined in low need.
5. Part Five: Quality Management Plan
Quality Management Plan Statement is set up as:
"We therefore pronounce that we planned to create online ticket booking framework for
RALS advisory group and we will give shear quality in all functionalities as gathered and
examined preceding undertaking start stage."
Verification activities are said as following:
1. Ensures that the item is in-accordance with the authoritative approaches and systems
2. Checks about legitimate automation
3. Guarantees about legitimate testing devices
4. Guarantees testing process in standard with booked timetable

13PROJECT MANAGEMENT METHODOLOGIES
Validation activities are specified as following:
A. Distinguishes about insider blemishes, for example, testing bugs
B. Identifies about application usefulness deserts
6. Part Six: Annotated Bibliography: Closure and Evaluation
6.1 Annotated Bibliography
Article 1: A Guide to the Project Management Body of Knowledge: PMBOK (®) Guide
As defined by Synder (2014), the project management provides an ample source of
development and modification for the analysis of the specific methods of project integration and
development. The theories of the project management holds significant for the employment of
the generalized manners of the project integration.
Article 2: Project Management: The Managerial Process with MS Project
Larson and Gray (2013), have defined the concept of the project management as the process of
managing the operations of the project by the help of using Ms-Project as the software support. It
would help in forming the management of the operations and development of the plan by using
computer aided tools.
Article 3: Project management: a systems approach to planning, scheduling, and controlling
According to Kerzner (2013), the project management holds a systematic process of developing
the effective and improved processing of the organization and hence it would comprise of
developing the formation of the improved process integration.

14PROJECT MANAGEMENT METHODOLOGIES
6.2 Closure checklist
The conclusion checklist ought to incorporate some real exercises, for example, partner sign-out,
contract sign-out, assessment design planning, getting ready documentation, and execution
looking into.
6.3 Evaluation Plan
The evaluation plan ought to include some legitimate criteria, for example, execution, meeting
prerequisites, consummation inside time, and accomplishing more elevated amount expectations
with quality.

15PROJECT MANAGEMENT METHODOLOGIES
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.
Kerzner, H. (2013). Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.

16PROJECT MANAGEMENT METHODOLOGIES
Larson, E. W., & Gray, C. (2013). Project Management: The Managerial Process with MS
Project. McGraw-Hill.
Nanda, V. (2016). Quality management system handbook for product development
companies.CRC Press.
Pritchard, C. L., & PMP, P. R. (2014). Risk management: concepts and guidance. CRC Press.
Schwalbe, K. (2015). Information technology project management.Cengage Learning.
Snyder, C. S. (2014). A Guide to the Project Management Body of Knowledge: PMBOK (®)
Guide. Project Management Institute.
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.