1
Project Plan Development Memo
Donald J. Noordt
CPMGT/311
July 23rd, 2018
Jeffrey Messinger
2
Project Plan Development Memo
To: Chief Information Officer
From: Project Manager
Date: 7/21/18
Subject: Project Plan Development
Statement of Scope
The project for this paper is training management software. Due to stiff competition in
the business environment today, companies are trying to gain a competitive edge in the market
and subsequently hold a substantive market share. With training management software, the
company can efficiently and effectively run internal training. Furthermore, with this software,
the company can deal with its administrative tasks. Other benefits the company will enjoy with
the training management software include active training tracking and reporting and financial
management (Rubin, 2013).
The primary objective of the project is to develop useful employee training software.
After designing and implementing the training management software, the organization will be
able to train its new and current employees effectively. In other words, the goal of the project is
to design, develop, implement, and evaluate useful training management software within 14
months. Moreover, some of the deliverables of the project will include a project charter, project
plan, training software manual, progress report, and system maintenance plan (Rubin, 2013).
One of the critical assumptions of the project is that the project team will access the available
resources during the development and implementation of the software. These resources include
3
financial, physical, and human resources. Furthermore, the assumption is that all essential
stakeholders will be involved in the decision-making process. Moreover, another fundamental
premise is that the project will conclude within the set duration and predetermined budget.
Nonetheless, there are some limitations imposed on the project. One of the constraints of the
project is the resources will be limited, and therefore the project team must work with the
provided resources. Additionally, scope creep might happen to the project, and this will increase
the cost, time, and resources and possibly reduce the quality of the project. Another constraint of
the project is that not all stakeholders will support the development and implementation of the
training management software (Ali, Rehman, Anjum, 2017).
Users
The users of the project will be primarily the organizational employees. Since the training
management software will be used to manage and enhance the training and development of
employees, the new and current employees will be the primary users of the project. In addition to
the employees, the organizational management will also be the users of the project. The software
will be used by the organization’s human resource department to conduct internal training for all
employees.
Project Requirements Gathering Process and User Stories
The project requirements gathering process used in the project is prototyping. With this
approach, the team members will conduct some requirements collection and then go to work to
produce preliminary project deliverables. There will then be a presentation of the deliverables to
the clients who will evaluate them and identify the prototype’s flaws. The project team will later
fix the flaws based on the users’ evaluation. Prototyping is an essential project requirement
4
gathering process because it will enhance the quality of the final project at the same time
encourages contact between the project team and the client/users (Alexandros, Sakas, Vlachos,
Dimitrios, 2017).
A user story is typically a device in Agile software development to obtain a portrayal of a
software feature from an end-user viewpoint. Essentially, the user story outlines the type of users
and what they want from the project. In the development and implementation of the training
management software, user stories will assist in developing a compelling depiction of a
requirement. The project team will incorporate user stories to create software that fits the
description and needs of the users. In other words, the design of the software features is in a
manner that aligns with the description portrayed by the users. The project manager will depend
on user story mapping. The project manager and team members will picture how to achieve user
stories within a sprint (Rubin, 2013).
Product Features
One of the features of the training management software is centralized training data. This
feature will enable the users and other relevant stakeholders to access and manage course
catalogs efficiently and effectively in a centralized location. Another feature of the software is
tracking systems. To warrant that the training programs used per the organization’s policy, it is
crucial to follow which training has completed. Therefore, the tracking systems will assist in
monitoring the completed and overdue training. Another feature of the training management
software is reporting systems. The software will provide reports, dashboards, and metrics to
assist in monitoring individual and organizational employee performance.
Estimates and Velocity
5
The expectation is that the project will take 14 months to complete. Furthermore, the
estimated cost of the project is $50,000. This cost will spread throughout the four phases of the
project management. These phases are projected initiation, planning, implementation, and project
evaluation and control. Moreover, the expected velocity of the project is 40 points per sprint.
This value is derived because the project team estimates 160 points over four sprints (Mousaei,
Gandomani, 2018).
6
References
Alexandros, N. K., Sakas, D. P., Vlachos, D. S., & Dimitrios, N. K. (2017). Comparing Scrum and
XP Agile Methodologies Using Dynamic Simulation Modeling. In Strategic Innovative
Marketing (pp. 391-397). Springer, Cham.
Ali, A., Rehman, M., & Anjum, M. (2017). Framework for Applicability of Agile Scrum
Methodology: A Perspective of Software Industry. INTERNATIONAL JOURNAL OF
ADVANCED COMPUTER SCIENCE AND APPLICATIONS, 8(9), 225-232.
Mousaei, M., & Gandomani, T. J. (2018). A New Project Risk Management Model based on
Scrum Framework and Prince2 Methodology. INTERNATIONAL JOURNAL OF
ADVANCED COMPUTER SCIENCE AND APPLICATIONS, 9(4), 442-449.
Rubin, K.S. (2013) Essential scrum: A practical guide to the most popular agile process. Upper
Saddle River, NJ: Pearson.
Project Plan Team Roles Memo Grading
Guide
CPMGT/311 Version 1
Agile Project Management with Scrum Methodology
Copyright
Copyright © 2016 by University of Phoenix. All rights reserved.
University of Phoenix® is a registered trademark of Apollo Group, Inc. in the United States and/or other countries.
Microsoft®, Windows®, and Windows NT® are registered trademarks of Microsoft Corporation in the United States and/or other countries. All
other company and product names are trademarks or registered trademarks of their respective companies. Use of these marks is not intended
to imply endorsement, sponsorship, or affiliation.
Project Plan Team Roles Memo
Grading Guide
CPMGT/311 Version 1
Edited in accordance with University of Phoenix® editorial standards and practices.
2
Project Plan Team Roles Memo
Grading Guide
CPMGT/311 Version 1
Individual Assignment: Project Plan Team Roles Memo
Purpose of Assignment
Week 3 is focused on project human resources and the roles and responsibilities of key actors in the
agile/Scrum environment. The assignment continues the use of the course-length project identified in Week 2
individual assignment. Students are asked to identify and analyze roles and responsibilities for a variety of agile
project leaders, mangers, and other stakeholders.
Grading Guide
Content
Met
Partially
Met
Not Met
Total
Available
Total
Earned
7
#/7
The student writes a memo to staff identifying
the resources, roles, and responsibilities for
key project leaders.
The student provides roles and
responsibilities for the Product Owner.
The student provides roles and
responsibilities for the Scrum Master.
The student provides roles and
responsibilities for the development team.
The student provides roles and
responsibilities for the managers.
The student provides roles and
responsibilities for the stakeholders.
The student includes the resources used and
determines who will be responsible for them.
The student compares the responsibilities of
the project sponsor, product owner, and the
product manager.
The student discusses a plan to empower
team members.
The student uses at least three references.
The paper is 700 to 1,050 words in length.
Comments:
3
Project Plan Team Roles Memo
Grading Guide
CPMGT/311 Version 1
Writing Guidelines
Met
Partially
Met
Not Met
Total
Available
Total
Earned
3
#/3
10
#/10
The paper—including tables and graphs,
headings, title page, and reference page—is
consistent with APA formatting guidelines and
meets course-level requirements.
Intellectual property is recognized with in-text
citations and a reference page.
Paragraph and sentence transitions are
present, logical, and maintain the flow
throughout the paper.
Sentences are complete, clear, and concise.
Rules of grammar and usage are followed
including spelling and punctuation.
Assignment Total
Additional comments:
#
Comments:
4
Purchase answer to see full
attachment