Description
In the final project, you will develop a complete project plan for a
hypothetical organization. Each milestone assignment will help you
complete portions of the final project. In this milestone,
you will evaluate the project manager’s management of team members,
resources, conflict, and engagement with project stakeholders to further
improve project implementation using a
second case study from your Mindedge resource; the ECO-Trans case study.
If you do not have access to project management software, use the
provided templates below:
Standard Requirements Template (Project Planning Part C)
Project Schedule (Project Planning Part E)
Prompt
The goal of this milestone is to delve more deeply into the project
planning and project execution areas of project management. As mentioned
above, you are to use the ECO-Trans case study
(in MindEdge) to complete this milestone.
Specifically the following critical elements must be addressed:
II. Project Planning
A. Determine the business requirements for the successful development of
the project. Justify your choices.
B. Establish who will provide the business requirements. What approach
will be used to solicit the requirements from the subject matter
experts?
C. Categorize and organize the business requirements in a standard
requirements template.
D. Explain why the format for capturing requirements is important to the
overall success of the project. Why would we consider requirements’
traceability?
E. Leveraging the business requirements, translate these requirements
into a project schedule using project management software through the
provided template.
F. Estimate the duration of project tasks using common business
knowledge, and assign resources to complete each task.
G. Refine your estimate of the project cost based on the duration of
tasks and resources needed.
III. Project Execution
A. Determine the best implementation approach—agile or waterfall
project—for the organization based on its organizational structure.
Provide examples to support your rationale.
B. Explain how the project schedule can be resource leveled,
fast-tracked, or crashed if needed based upon execution results.
C. Propose communication approaches and the frequency that should be
used to keep leadership apprised of the project execution. Include
examples to support your claims.
What to Submit
Your draft of the Project Planning and Project Execution portions of
your final project should adhere to the following formatting
requirements: 3–4 pages, double-spaced, using 12-point Times
New Roman font and one-inch margins. You should use current APA-style
guidelines for your citations and a reference list with a minimum of two
sources.
Milestone Two Rubric
Criteria Proficient (100%) Needs Improvement (75%) Not Evident (0%)
Value
Project Planning: Business
Requirements
Determines the business requirements for
the successful development of the case
study project and justifies choices
Determines the business requirements for
the successful development of the case
study project, but does not justify choices,
or determination contains inaccuracies
Does not determine the business
requirements for the successful
development of the case study project
8
Project Planning: Subject
Matter Experts
Establishes who will provide the
requirements and what approach will be
used to solicit the requirements from the
subject matter experts
Establishes who will provide the
requirements, but does not establish what
approach will be used or selection is
illogical
Does not establish who will provide the
requirements
8
Project Planning: Standard
Requirements Template
Categorizes and organizes the business
requirements in a standard requirements
template
Categorizes and organizes the business
requirements in a standard requirements
template, but approach is illogical or lacks
detail
Does not categorize and organize the
business requirements in a standard
requirements template
8
Project Planning: Format Explains why the format for capturing
requirements is important to the overall
success of the project, including
traceability
Explains why the format for capturing
requirements is important to the overall
success of the project, but response lacks
traceability, contains inaccuracies, or is
cursory
Does not explain why the format for
capturing requirements is important to the
overall success of the project
8
Project Planning: Project
Schedule
Translates the requirements into a project
schedule that contains appropriate and
logical predecessor relationships using
project management software through the
provided template
Translates the requirements into a project
schedule using project management
software through the provided template,
but relationships are inappropriate or
illogical
Does not translate the requirements into a
project schedule using project
management software through the
provided template
10
Project Planning: Estimate Estimates the duration of the project tasks
using common business knowledge and
assigns resources to complete each task
Estimates the duration of the project tasks
using common business knowledge and
assigns resources to complete each task,
but estimation is inaccurate or
overgeneralized
Does not estimate the duration of the
project tasks
10
Unformatted Attachment Preview
Standard Requirements Template
Requirement Number
Requirement Description
Priority (High, Medium, or Low)
Milestone Chart
Activity Activity
Name
Expected
Completion
Date
Predecessor
1st Quarter
Jan
Feb
Mar
2nd Quarter
Apr
May
Jun
3rd Quarter
Jul
1
2
3
= Expected completion date
= Actual completion date
Aug
Sep
4th Quarter
Oct
Nov
Dec
Graded Case Study 2, Part I
The Project
ECO-Trans is a European company providing “driver assist” technology for use in buses, trains, and other mass transit vehicles. Its flagship
product, ECO-Stream, is a small, durable computer screen installed in a driver’s space or an engineer’s cab that provides operators with
targeted suggestions. The ECO-Stream system analyzes the current route of a bus or train, including the scheduled time of arrival, and advises
the operator on techniques (such as gear or notch choice, when to brake or “coast,” etc.) that will realize the greatest fuel savings. These
driving recommendations are based on data collected from the transportation network, including road or track configuration, maximum
timetable speeds, traffic, or other speed restrictions and delays.
In addition to better schedule adherence, the key benefits of ECO-Stream are savings on fuel consumption and reduction in CO2 emissions.
Astrid Varga is a project manager for ECO-Trans. She is currently leading her team’s implementation of ECO-Stream for a major client,
Sunshine Rail Transit (SRT), which operates light rail commuter service between several major cities in the Southeast. SRT’s Operations
Department contracted with ECO-Trans to implement customized ECO-Stream systems in all 53 locomotives in its fleet.
Schedule and Cost
Varga is working with a detailed project plan to manufacture, install, and calibrate the system. The plan essentially spans two key phases: the
first dedicated to the installation and monitoring of trial equipment, and the second dedicated to installing the ECO-Stream modules and
equipment on the entire SRT light rail locomotive fleet. The first phase is critical in helping Varga’s team determine the best way to configure
the system so it provides the most benefits to SRT operations.
The implementation schedule covers a 15-month time frame, with the following summary of key milestones:
Nov 2012: Project initiation
April 2013: Complete system test on North Central line and document results
May 2013: Confirm funding by state transportation authorities and SRT
June 2013: Implement equipment for central control room
Sept 2013: Equip first phase of locomotives with the system
Jan 2014: Equip entire fleet with the system
Feb 2014: Complete end user training
The first four major milestones above were completed smoothly. The implementation of the fleet equipment, however, has run into some
roadblocks that are creating delays. Specifically, the delivery of a key component in the ECO-Stream cab computer terminal has been found to
have defects and must be returned to the supplier.
Varga is under pressure from both her manager and John Schaller, the client’s Project Sponsor, to deliver the system on schedule and within
budget. Schaller has been clear that there is no possibility to allocate additional money (above and beyond the authorized budget) for the
ECO-Stream project.
To consider her options for compressing the schedule, she reviews the network diagram for manufacturing and configuring the ECO-Stream
terminals:
QSO 640: Project Management
Copyright © 2014, %year% MindEdge Inc. All rights reserved. Duplication prohibited. PMP, PMI-ACP, PMI-RMP, PMBOK, and the PMI
Registered Education Provider logo are registered marks of the Project Management Institute, Inc.
The ECO-Stream terminal contains the driver’s interface screen that displays information and video. It also connects to a “communication
box.” The communication box sends and receives data on train speed, energy consumption, GPS location, and arrival and departure times; it
does this by interfacing with multiple devices that collect this data.
The defective component is needed to connect the terminal to the communication box. Delayed connection parts will delay the configuration
of critical incoming and outgoing data interfaces to the driver’s terminal.
Looking at the network diagram, Varga decides that she can use crashing to get the necessary components from an alternate supplier. She
knows that this supplier will charge more per part, especially with expedited delivery, but she cannot think of another way to restore the
terminal manufacturing schedule and meet the client’s installation target.
Before you move on to the next section of the case study, identify the problems and/or issues that you’ll need to include in your analysis.
Document this information, and consider how you will integrate it into your evaluation of the project.
QSO 640: Project Management
Copyright © 2014, %year% MindEdge Inc. All rights reserved. Duplication prohibited. PMP, PMI-ACP, PMI-RMP, PMBOK, and the PMI
Registered Education Provider logo are registered marks of the Project Management Institute, Inc.
QSO 640 Milestone Two Guidelines and Rubric
Overview
In the final project, you will develop a complete project plan for a hypothetical organization. Each milestone assignment will help you complete portions of the final project. In this milestone,
you will evaluate the project manager’s management of team members, resources, conflict, and engagement with project stakeholders to further improve project implementation using a
second case study from your Mindedge resource; the ECO-Trans case study. If you do not have access to project management software, use the provided templates below:
Standard Requirements Template (Project Planning Part C)
Project Schedule (Project Planning Part E)
Prompt
The goal of this milestone is to delve more deeply into the project planning and project execution areas of project management. As mentioned above, you are to use the ECO-Trans case study
(in MindEdge) to complete this milestone.
Specifically the following critical elements must be addressed:
II. Project Planning
A. Determine the business requirements for the successful development of the project. Justify your choices.
B. Establish who will provide the business requirements. What approach will be used to solicit the requirements from the subject matter experts?
C. Categorize and organize the business requirements in a standard requirements template.
D. Explain why the format for capturing requirements is important to the overall success of the project. Why would we consider requirements’ traceability?
E. Leveraging the business requirements, translate these requirements into a project schedule using project management software through the provided template.
F. Estimate the duration of project tasks using common business knowledge, and assign resources to complete each task.
G. Refine your estimate of the project cost based on the duration of tasks and resources needed.
III. Project Execution
A. Determine the best implementation approach—agile or waterfall project—for the organization based on its organizational structure. Provide examples to support your rationale.
B. Explain how the project schedule can be resource leveled, fast-tracked, or crashed if needed based upon execution results.
C. Propose communication approaches and the frequency that should be used to keep leadership apprised of the project execution. Include examples to support your claims.
What to Submit
Your draft of the Project Planning and Project Execution portions of your final project should adhere to the following formatting requirements: 3–4 pages, double-spaced, using 12-point Times
New Roman font and one-inch margins. You should use current APA-style guidelines for your citations and a reference list with a minimum of two sources.
Milestone Two Rubric
Criteria
Proficient (100%)
Needs Improvement (75%)
Project Planning: Business
Requirements
Determines the business requirements for
the successful development of the case
study project and justifies choices
Determines the business requirements for
the successful development of the case
study project, but does not justify choices,
Not Evident (0%)
Value
Does not determine the business
requirements for the successful
development of the case study project
8
Does not establish who will provide the
requirements
8
or determination contains inaccuracies
Project Planning: Subject
Matter Experts
Establishes who will provide the
requirements and what approach will be
Establishes who will provide the
requirements, but does not establish what
used to solicit the requirements from the
subject matter experts
approach will be used or selection is
illogical
Project Planning: Standard
Requirements Template
Categorizes and organizes the business
requirements in a standard requirements
template
Categorizes and organizes the business
requirements in a standard requirements
template, but approach is illogical or lacks
detail
Does not categorize and organize the
business requirements in a standard
requirements template
8
Project Planning: Format
Explains why the format for capturing
requirements is important to the overall
success of the project, including
traceability
Explains why the format for capturing
requirements is important to the overall
success of the project, but response lacks
traceability, contains inaccuracies, or is
cursory
Does not explain why the format for
capturing requirements is important to the
overall success of the project
8
Project Planning: Project
Schedule
Translates the requirements into a project
schedule that contains appropriate and
logical predecessor relationships using
project management software through the
provided template
Translates the requirements into a project
schedule using project management
software through the provided template,
but relationships are inappropriate or
illogical
Does not translate the requirements into a
project schedule using project
management software through the
provided template
10
Project Planning: Estimate
Estimates the duration of the project tasks
using common business knowledge and
assigns resources to complete each task
Estimates the duration of the project tasks
using common business knowledge and
assigns resources to complete each task,
but estimation is inaccurate or
overgeneralized
Does not estimate the duration of the
project tasks
10
Criteria
Proficient (100%)
Needs Improvement (75%)
Not Evident (0%)
Value
Project Planning: Refine
Estimate
Refines estimate of the project based on
the duration of the tasks and resources
needed
Refines estimate of the project, but
estimate is inaccurate
Does not refine estimate of the project
10
Project Execution:
Implementation Approach
Determines which implementation
approach is the best for the organization,
using examples to support rationale
Determines an implementation approach
for the organization, but response lacks
examples that support rationale or is
cursory
Does not determine an implementation
approach
10
Project Execution: Project
Schedule
Explains how the project schedule can be
resource leveled, fast-tracked, or crashed if
needed based upon execution results
Explains how the project schedule can be
resource leveled, fast-tracked, or crashed,
but response is inaccurate or
overgeneralized
Does not explain how the project schedule
can be resource leveled, fast-tracked, or
crashed
10
Project Execution: Keep
Leadership Apprised
Proposes communication approaches and
frequency to keep leadership apprised of
the project execution, using examples to
support claims
Proposes communication approaches and
frequency to keep leadership apprised of
the project execution, but response lacks
examples that support claims or is
inappropriate
Does not propose communication
approaches and frequency to keep
leadership apprised
10
Articulation of Response
Submission has no major errors related to
citations, grammar, spelling, syntax, or
organization
Submission has major errors related to
citations, grammar, spelling, syntax, or
organization that negatively impact
readability and articulation of main ideas
Submission has critical errors related to
citations, grammar, spelling, syntax, or
organization that prevent understanding of
ideas
8
Total:
100%
QSO 640 Final Project Guidelines and Rubric
Overview
Organizations continue to struggle with successful project implementations that support business goals. Strides in project management have been achieved through a consistent approach to
project management as defined by the Project Management Institute (PMI)® A Guide to the Project Management Body of Knowledge, (PMBOK® Guide), Fifth Edition, 2013. Specifically, the
five phases of project management—consisting of initiating, planning, executing, controlling, and closing—provide a framework for achieving business goals through successful project
implementations. At the completion of the course, you will understand the key deliverables and activities within each phase of this framework in order to achieve business goals.
Your final project will be a complete project management plan. The plan will be comprised of standard templates used by organizations across all industries. For milestones one and two, you
will use two different case studies from your Mindedge resource. For your final project, you will be using a third case study from Mindedge, the HighTower Global Solutions case study, as the
foundation for your plan. Each week you will move through the phases of the project management life cycle and develop components of the project management plan to address the
organizational need within each of these different case studies. You will consider stakeholder perspectives and communication needs as well as typical project risks and issues. At the end of
the course, you will have a complete project management plan that supports a typical project for an organization.
The project is divided into two milestones, which will be submitted at various points throughout the course to scaffold learning and ensure quality final submissions. Please note that you will
use different case studies for each Milestone and for your final project in this course, all of which can be found in your Mindedge resource.
Milestone One utilizes the Fabricant Manufacturing Project case study and will be submitted in Module Three.
Milestone Two utilizes the ECO-Trans case study and will be submitted in Module Six.
The final project utilizes the HighTower Global Solutions case study and will be submitted in Module Nine.
In your final project, you will demonstrate your mastery of the following course outcomes:
Develop project charters that illustrate the high-level scope of the project as it aligns to organizational strategic needs
Analyze internal and external stakeholder needs for efficiently navigating organizational structures
Determine proper approaches to defining business requirements for aligning with business strategies
Utilize project management software for effectively developing project management plans
Develop key project management control documents for ensuring effective management plan scope descriptions
Evaluate agile and waterfall methods for successful project execution
Determine approaches for project closure that inform ongoing best practices in project management planning
Prompt
Throughout the course, you have been working through the phases of the project management life cycle to develop components for a project management plan that addresses the
organizational needs of the organization highlighted in two case studies: the Fabricant Manufacturing Project (Milestone One) and the ECO- Trans case study (Milestone Two). Your instructor
and peers have provided feedback for you to consider along the way. Now, you have the background knowledge and the information necessary to complete your project management plan,
which utilizes the HighTower Global Solutions case study, available in MindEdge.
Specifically, the following critical elements must be addressed:
I. Project Initiation
A. Identify the economic, technical, and organizational feasibility of the project. For instance, how is the project a viable fit within the organization?
B. Explain how the project aligns to the organization’s strategic goals utilizing the traceability matrix (in Mindedge).
C. Develop a project charter that includes a high-level scope of what is to be accomplished.
D. Create a high-level timeline and cost estimate to complete the project.
E. Identify the concerns of the internal and external key project stakeholders.
F. Compare the level of support from all key project stakeholders to inform the course of action resulting in success of the project.
G. Complete the stakeholder analysis template.
II. Project Planning
A. Determine the business requirements for the successful development of the project. Justify your choices.
B. Establish who will provide the business requirements. What approach will be used to solicit the requirements from the subject matter experts?
C. Categorize and organize the business requirements in a standard requirements template.
D. Explain why the format for capturing requirements is important to the overall success of the project. Why would we consider requirements’ traceability?
E. Leveraging the business requirements, translate these requirements into a project schedule using project management software through the provided template.
F. Estimate the duration of project tasks using common business knowledge, and assign resources to complete each task.
G. Refine your estimate of the project cost based on the duration of tasks and resources needed.
III. Project Execution
A. Determine the best implementation approach—agile or waterfall project—for the organization based on its organizational structure. Provide examples to support your rationale.
B. Explain how the project schedule can be resource leveled, fast-tracked, or crashed if needed based upon execution results.
C. Propose communication approaches and the frequency that should be used to keep leadership apprised of the project execution. Include examples to support your claims.
IV. Project Control
A. Describe how you will handle changes in scope to your project management plan. What change management process will be used? What key information will be required for change
requests?
B. Describe the risk management process that is the best fit for effective project control over your plan.
C. Explain how you will document issues and what process will be used to manage the issue to completion. Include examples to support your claims.
V. Project Closeout
A. Identify what needs to be done to close your project management plan. Include examples supporting how you will minimize the chances of overlooking a step in the project process.
B. Justify the need for a warranty period and how the project will transition to business
C. Complete a lessons-learned template for the case study project.
Milestones
Milestone One: Project Initiation
In Module Three, you will submit the Project Initiation portion of your final project. Milestone One utilizes the Fabricant Manufacturing Project case study. This milestone will be graded with
the Milestone One Rubric.
Milestone Two: Project Planning and Project Execution
In Module Six, you will submit the Project Planning and Project Execution portions of your final project. Milestone Two utilizes the ECO-Trans case study. This milestone will be graded with the
Milestone Two Rubric.
Final Submission: Project Management Plan
In Module Nine, you will submit your final project, which utilizes the HighTower Global Solutions case study. It should be a complete, polished artifact containing all of the critical elements of
the final product. It should reflect the incorporation of feedback gained throughout the course. This submission will be graded with the Final Project Rubric.
What to Submit
Your project management plan should be between 10 and 12 pages, double-spaced, have one-inch margins, and use 12-point Times New Roman font and the most recent version of APA
format.
Final Project Rubric
Criteria
Exemplary (100%)
Proficient (90%)
Needs Improvement (70%)
Not Evident (0%)
Value
Project Initiation: Feasibility
Meets “Proficient” criteria and
demonstrates nuanced
understanding of the specific
organizational parameters of
feasibility
Identifies the economic,
technical, and organizational
feasibility of the project and
how the project is a viable fit
within the organization
Identifies the economic,
technical, and organizational
feasibility of the project, but
does not discuss how the
project is a viable fit within the
organization or is inaccurate or
cursory
Does not identify the economic,
technical, and organizational
feasibility of the project
3.46
Criteria
Exemplary (100%)
Proficient (90%)
Needs Improvement (70%)
Not Evident (0%)
Value
Project Initiation: Strategic
Goals
Meets “Proficient” criteria and
demonstrates insight into
project alignment with
strategic goals
Explains how the project aligns
to the organization’s strategic
goals
Explains how the project aligns
to the organization’s strategic
goals, but explanation is
inaccurate or cursory
Does not describe how the
project aligns to the
organization’s strategic goals
4.62
Project Initiation: Project
Charter
Meets “Proficient” criteria and
demonstrates nuanced
understanding of what is to be
accomplished
Develops a project charter that
includes a high-level scope of
what is to be accomplished and
is detailed appropriately
Develops a project charter, but
does not include a high-level
scope of what is to be
accomplished
Does not develop a project
charter
4.62
Project Initiation: High-Level
Timeline
Meets “Proficient” criteria and
demonstrates insight into the
complexity of project
Creates a high-level timeline
and estimate of cost to
complete the project
Creates a high-level timeline
and estimate of cost to
complete the project, but
response contains inaccuracies
Does not create a high-level
timeline or estimate of cost to
complete the project
4.62
Project Initiation: Key
Project Stakeholders
Meets “Proficient” criteria and
demonstrates insight into the
different stakeholder concerns
Identifies the concerns of key
project internal and external
stakeholders
Identifies the concerns of key
project internal and external
stakeholders, but response
either contains inaccuracies or
is overgeneralized
Does not identify the concerns
of key project stakeholders
3.46
Project Initiation: Support
Meets “Proficient” criteria and
shows a deep understanding of
how to leverage stakeholders
Compares the level of support
from all key stakeholders to
inform the course of action of
Compares the level of support
from all key stakeholders, but
discussion contains gaps or
Does not compare the level of
support from all key
stakeholders
3.46
for the success of a project
the project
inaccuracies
Project Initiation:
Meets “Proficient” criteria, and
Completes the stakeholder
Completes the stakeholder
Does not complete the
3.46
Stakeholder Analysis
Template
level of detail shows keen
insight into the scope and scale
analysis template
analysis template, but template
contains inaccuracies
stakeholder analysis template
of the project
Project Planning: Business
Meets “Proficient” criteria and
Determines the business
Determines the business
Does not determine the
Requirements
demonstrates insight into the
business requirements
requirements for the successful
development of the case study
requirements for the successful
development of the case study
business requirements for the
successful development of the
necessary for the successful
development of a project
project and justifies choices
project, but does not justify
choices, or determination
case study project
contains inaccuracies
3.46
Criteria
Exemplary (100%)
Project Planning: Subject
Meets “Proficient” criteria and
Establishes who will provide
Establishes who will provide
Does not establish who will
demonstrates insight into
solicitation approaches for
the requirements and what
approach will be used to solicit
the requirements, but does not
establish what approach will be
provide the requirements
subject matter experts
the requirements from the
subject matter experts
used or selection is illogical
Meets “Proficient” criteria and
provides level of detail and
Categorizes and organizes the
business requirements in a
Categorizes and organizes the
business requirements in a
Does not categorize and
organize the business
organization that streamlines
project development
standard requirements
template
standard requirements
template, but approach is
requirements in a standard
requirements template
Matter Experts
Project Planning: Standard
Requirements Template
Proficient (90%)
Needs Improvement (70%)
Not Evident (0%)
Value
3.46
3.46
illogical or lacks detail
Project Planning: Format
Meets “Proficient” criteria and
Explains why the format for
Explains why the format for
Does not explain why the
demonstrates insight into the
connection of traceability
capturing requirements is
important to the overall
capturing requirements is
important to the overall
format for capturing
requirements is important to
throughout project
development
success of the project, including
traceability
success of the project, but
response lacks traceability,
the overall success of the
project
3.46
contains inaccuracies, or is
cursory
Project Planning: Project
Schedule
Project Planning: Estimate
Project Planning: Refine
Estimate
Meets “Proficient” criteria and
demonstrates a complex grasp
Translates the requirements
into a project schedule that
Translates the requirements
into a project schedule using
Does not translate the
requirements into a project
of predecessor relationships
contains appropriate and
logical predecessor
project management software
through the provided template,
schedule using project
management software through
relationships using project
but relationships are
the provided template
management software through
the provided template
inappropriate or illogical
Meets “Proficient” criteria and
demonstrates nuanced
Estimates the duration of the
project tasks using common
Estimates the duration of the
project tasks using common
understanding of business
knowledge and resources in
business knowledge and
assigns resources to complete
business knowledge and
assigns resources to complete
project management
each task
each task, but estimation is
inaccurate or overgeneralized
Meets “Proficient” criteria and
demonstrates deep
Refines estimate of the project
based on the duration of the
Refines estimate of the project,
but estimate is inaccurate
understanding of project costs
tasks and resources needed
4.62
Does not estimate the duration
of the project tasks
4.62
Does not refine estimate of the
project
4.62
Criteria
Exemplary (100%)
Proficient (90%)
Needs Improvement (70%)
Project Execution:
Implementation Approach
Meets “Proficient” criteria and
demonstrates deep
Determines which
implementation approach is the
Determines an implementation
approach for the organization,
understanding of how the
selected implementation
best for the organization, using
examples to support rationale
but response lacks examples
that support rationale or is
approach supports
organizational structure
Project Execution: Project
Schedule
Not Evident (0%)
Value
Does not determine an
implementation approach
4.62
4.62
cursory
Meets “Proficient” criteria and
demonstrates deep
Explains how the project
schedule can be resource
Explains how the project
schedule can be resource
Does not explain how the
project schedule can be
understanding of relationship
leveled, fast-tracked, or
leveled, fast-tracked, or
resource leveled, fast-tracked,
between schedule techniques
and project execution
crashed if needed based upon
execution results
crashed, but response is
inaccurate or overgeneralized
or crashed
Project Execution: Keep
Meets “Proficient” criteria and
Proposes communication
Proposes communication
Does not propose
Leadership Apprised
demonstrates insight into the
approaches and frequency to
approaches and frequency to
communication approaches and
appropriate communication
needed to keep leadership
keep leadership apprised of the
project execution, using
keep leadership apprised of the
project execution, but response
frequency to keep leadership
apprised
apprised
examples to support claims
lacks examples that support
claims or is inappropriate
Meets “Proficient” criteria and
demonstrates nuanced
Describes a change
management process that is the
Describes a change
management process that is the
Does not describe a change
management process that is the
understanding of the change
management process
best fit for the project,
including key information
best fit for the project, but
response lacks key information
best fit for the project
required
or process contains
inaccuracies or gaps
Meets “Proficient” criteria and
demonstrates insight into how
Describes the risk management
process that is the best fit for
Describes the risk management
plan, but description has gaps
risk management positively
impacts project control
effective project control over
the plan
or inaccuracies
Meets “Proficient” criteria, and
process is exceptionally
Explains how issues will be
documented and what process
detailed
Project Control: Change
Management
Project Control: Risk
Management
Project Control: Issues
4.62
4.62
Does not describe the risk
management plan
4.62
Explains how issues will be
documented and the process to
Does not explain how issues
will be documented and the
4.62
will be used to manage the
issue to completion, including
manage the issue, but response
contains inaccuracies or is
process to manage the issue
examples that support claims
cursory
Criteria
Exemplary (100%)
Proficient (90%)
Needs Improvement (70%)
Not Evident (0%)
Value
Project Closeout: Close
Meets “Proficient” criteria and
demonstrates a deep
Identifies what needs to be
done to close the project plan,
Identifies what needs to be
done to close the project plan,
Does not identify what needs to
be done to close the project
4.62
understanding of project plan
closure
including examples to support
how to minimize the chances of
but response contains
inaccuracies, is cursory, or does
plan
overlooking steps
not include examples
Project Closeout: Warranty
Meets “Proficient” criteria, and
Justifies the need for a
Justifies the need for a
Does not justify the need for a
Period
discussion demonstrates
nuanced understanding of the
warranty period and process
for transitioning project to
warranty period and process
for transitioning project to
warranty period and process
for transitioning project to
project transition
business
business, but response contains
inaccuracies or is cursory
business as usual
Meets “Proficient” criteria and
demonstrates nuanced
Completes a lessons-learned
template for the project plan
Completes a lessons-learned
template for the project plan,
Does not complete a lessonslearned template
4.62
3.02
Project Closeout: LessonsLearned Template
understanding of using a
lessons-learned template for
4.62
but template contains
inaccuracies
continuous improvement
Articulation of Response
Submission is free of errors
Submission has no major errors
Submission has major errors
Submission has critical errors
related to citations, grammar,
spelling, syntax, and
related to citations, grammar,
spelling, syntax, or organization
related to citations, grammar,
spelling, syntax, or organization
related to citations, grammar,
spelling, syntax, or organization
organization and is presented
in a professional and easy-to-
that negatively impact
readability and articulation of
that prevent understanding of
ideas
read format
main ideas
Total:
100%
Purchase answer to see full
attachment
