MMIS 621 Assignment 4 Information Systems Project
Management Plan
ERP system implementation
MMIS 621: Information Systems Project Management
Fall 2015
Click Link Below To Buy:
Contact Us:
Hwcoursehelp@gmail.com
Purpose:
The purpose of
this paper is to give you an opportunity to apply and demonstrate your
understanding of the tools and principles covered in the class to a project of
your choice.
Section 1: Project Definition (5-6
pages)
Define the Project
Scope: Use
the scope statement template to develop a 2-3 page scope statement for your
project. See a snapshot example on page 105.
Establish Project
Priorities:
As a project manager, you will need to manage the trade-offs
among time, cost, and performance. Create a priority matrix (See figure 4.2 on page 107) to determine
which criterion (i.e., time, performance, and cost) are constrained, enhanced,
and accepted. Provide a brief explanation about your decisions to accompany the
matrix.
Create a Work
Breakdown Structure (WBS) or Process Breakdown Structure (PBS) and Cost and/or
Time Estimates:
Once you have completed your scope statement including the identification of
your deliverables and the project priorities, you will create either a work
breakdown structure (WBS) or Process Breakdown Structure (PBS) to delineate the
tasks. Refer to pages 108-113 and the WBS/PBS template to prepare a WBS or PBS
for your project. Estimate the project costs and/or time and explain how you
went about achieving your estimates.
Section 2: Project Communication
(1-2 pages)
Create a
Responsibility Matrix:
In order to ensure good communication among the project team, create a
responsibility matrix (see Figure 4.7 on page 118 for an example).
Create a
Power/Interest Map:
This is part of the stakeholder analysis. Who are your stakeholders (e.g.,
customer, sponsor, project team, etc.). See Figure 4.9 on page 120. (Letters on
the map represent various stakeholders. Make sure to include a key with your
map.) You will address stakeholder analysis again later on in Section 6.
Section 3: Project Plan (1-2
pages)
Develop a Project
Network: From
your WBS, develop an activity-on-node (AON) project network. Apply the eight
basic rules listed on page 164 for constructing a project network. Remember the
AON method uses nodes (boxes) for activities and arrows for dependencies.
Section 4: Project Risk
Management (1-2 pages)
Develop a Risk Assessment
and Risk Response Matrix:
Identify and describe at least five potential risks associated with your
project. Use a risk assessment form to analyze your risks (See Figure 7.6 on
page 212 for an example). Develop a risk response matrix similar to Figure 7.8
to outline how you would deal with each of the risks.
Section 5: Project Change Control
Management (1-2 pages)
Document Change: Controlling project changes is
very important to project managers. It is a major element in managing risk. If
your project is new, create a hypothetical change. If you are documenting a
past or existing project, identify on major change that has occurred. Use the
Change Request Form template to document the change.
Section 6: Project Leadership
(1-2 pages)
Stakeholder
Analysis – Mapping Dependencies:
Refer to pages 347-349. Create a dependencies diagram by identifying the
stakeholders on whom your project depends for success. Think about the
following questions:
1.
Whose
cooperation will we need?
2.
Whose
agreement or approval will we need?
3.
Whose
opposition would keep us from accomplishing the project?
Keys to Success: Identify
potential management issues (e.g., motivation problems, conflicts) that are
likely to arise in completing this project. What should you, as the project
manager, look out for in managing this project? What are the keys to success?
Guidelines and Suggestions for
Creating Your Project Management Plan
1.
Your
AON project network should include at least 15 and no more than 25 activities
to keep the paper manageable.
2.
Each
section must include a 1-2 paragraph introduction that explains what you are
presenting and its relevance to your plan. Your paper must tell a story!
Explain the managerial implications of each section. The narrative is as
important as your application of the tools and systems of the course to your
project.
3.
Pick
a project that allows you to demonstrate the principles covered in the course.
4.
Think
ahead to the resources that will be used. The project should involved more
than two people.
5.
Submit
only one file that includes your full plan (preferably in MSWord). You may
insert screen captures from work you did in other programs (e.g., MSProject,
MindView, Excel, etc.). Assume that top management is reviewing this report.
Time is precious, so organize your report so that it is easy to comprehend and
follow. Embed figures and tables into the text.
6.
Constructing
patios, garages, pools, and trivial projects are not valid projects for this
course. Aim to identify a project within your present or future profession.
7.
Be
realistic and create a project scenario that is either cost restrained, scope
constrained and/or time constrained.
8.
Your
goal is to demonstrate your understanding of the systems, tools, and concepts
discussed in the class through your project narrative.
9.
Templates
for the project scope statement, work breakdown structure/process breakdown
structure, risk assessment matrix, risk response matrix, and change request
form are provided at the end of this document. References are from the course
textbook, Larson and Gray (2013).
Scope
Statement for [Project Name]
|
Project Title:
Prepared by:
Date:
Version:
|
|
Project Objective:
.
|
|
Deliverables:
1.
2.
3.
4.
|
|
Milestones
1.
2.
3.
4.
|
|
Technical Requirements:
1.
2.
3.
4.
|
|
Limits and Exclusions:
1.
2.
3.
4.
|
|
Customer Review:
|
Work
Breakdown Structure for [Project Name]
Prepared
by: Date:
1.0 Main category 1
1.1
Subcategory
1.2
Subcategory
1.2.1 Sub-subcategory
1.2.2 Sub-subcategory
1.3
Subcategory
1.4
Subcategory
2.0 Main category 2
2.1
Subcategory
2.2
Subcategory
2.2.1 Sub-subcategory
2.2.2 Sub-subcategory
2.3
Subcategory
2.4
Subcategory
3.0 Main category 3
3.1 Subcategory
3.2 Subcategory
3.2.1
Sub-subcategory
3.2.2
Sub-subcategory
3.3 Subcategory
3.4 Subcategory
4.0 Main category 4
4.1 Subcategory
4.2 Subcategory
4.2.1
Sub-subcategory
4.2.2
Sub-subcategory
4.3 Subcategory
4.4 Subcategory
Risk
Assessment Matrix
List of
Prioritized Risks for [Project Name]
Prepared
by: Date:
|
Risk
Event
|
Likelihood
|
Impact
|
Detection
Difficulty
|
When
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Risk
Response Matrix for [Project Name]
Prepared
by: Date:
|
Risk
Event
|
Response
|
Contingency
Plan
|
Trigger
|
Who
is Responsible
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Change
Request Form for [Project Name]
Project
Name:
Date
Request Submitted:
Title
of Change Request
Change
Order Number:
Submitted
by: (name and
contact information)
Change Category: Scope Schedule Cost Technology Other
Description of change requested:
Events that made this change
necessary or desirable:
Justification for the change/why
it is needed/desired to continue/complete the project:
Impact of the proposed change on:
Scope:
Schedule:
Cost:
Staffing:
Risk:
Other:
Suggested implementation if the change
request is approved:
Required approvals:
|
Name/Title
|
Date
|
Approve/Reject
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
No comments:
Post a Comment