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?
No comments:
Post a Comment