support@chatgptassignment.com

Qso 640 Pm

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:

  1. Project Planning
    1. Determine the business requirements for the successful development of the project. Justify your choices.
    2. Establish who will provide the business requirements. What approach will be used to solicit the requirements from the subject matter experts?
    3. Categorize and organize the business requirements in a standard requirements template.
    4. Explain why the format for capturing requirements is important to the overall success of the project. Why would we consider requirements’ traceability?
    5. Leveraging the business requirements, translate these requirements into a project schedule using project management software through the provided template.
    6. Estimate the duration of project tasks using common business knowledge, and assign resources to complete each task.
    7. Refine your estimate of the project cost based on the duration of tasks and resources needed.
  2. Project Execution
    1. Determine the best implementation approach—agile or waterfall project—for the organization based on its organizational structure. Provide examples to support your rationale.
    2. Explain how the project schedule can be resource leveled, fast-tracked, or crashed if needed based upon execution results.
    3. 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

CriteriaProficient (100%)Needs Improvement (75%)Not Evident (0%)ValueProject Planning: Business RequirementsDetermines the business requirements for the successful development of the case study project and justifies choicesDetermines the business requirements for the successful development of the case study project, but does not justify choices, or determination contains inaccuraciesDoes not determine the business requirements for the successful development of the case study project8Project Planning: Subject Matter ExpertsEstablishes who will provide the requirements and what approach will be used to solicit the requirements from the subject matter expertsEstablishes who will provide the requirements, but does not establish what approach will be used or selection is illogicalDoes not establish who will provide the requirements8Project Planning: Standard Requirements TemplateCategorizes and organizes the business requirements in a standard requirements templateCategorizes and organizes the business requirements in a standard requirements template, but approach is illogical or lacks detailDoes not categorize and organize the business requirements in a standard requirements template8Project Planning: FormatExplains why the format for capturing requirements is important to the overall success of the project, including traceabilityExplains why the format for capturing requirements is important to the overall success of the project, but response lacks traceability, contains inaccuracies, or is cursoryDoes not explain why the format for capturing requirements is important to the overall success of the project8Project Planning: Project ScheduleTranslates the requirements into a project schedule that contains appropriate and logical predecessor relationships using project management software through the provided templateTranslates the requirements into a project schedule using project management software through the provided template, but relationships are inappropriate or illogicalDoes not translate the requirements into a project schedule using project management software through the provided template10Project Planning: EstimateEstimates the duration of the project tasks using common business knowledge and assigns resources to complete each taskEstimates the duration of the project tasks using common business knowledge and assigns resources to complete each task, but estimation is inaccurate or overgeneralizedDoes not estimate the duration of the project tasks10Project Planning: Refine EstimateRefines estimate of the project based on the duration of the tasks and resources neededRefines estimate of the project, but estimate is inaccurateDoes not refine estimate of the project10Project Execution: Implementation ApproachDetermines which implementation approach is the best for the organization, using examples to support rationaleDetermines an implementation approach for the organization, but response lacks examples that support rationale or is cursoryDoes not determine an implementation approach10Project Execution: Project ScheduleExplains how the project schedule can be resource leveled, fast-tracked, or crashed if needed based upon execution resultsExplains how the project schedule can be resource leveled, fast-tracked, or crashed, but response is inaccurate or overgeneralizedDoes not explain how the project schedule can be resource leveled, fast-tracked, or crashed10Project Execution: Keep Leadership ApprisedProposes communication approaches and frequency to keep leadership apprised of the project execution, using examples to support claimsProposes communication approaches and frequency to keep leadership apprised of the project execution, but response lacks examples that support claims or is inappropriateDoes not propose communication approaches and frequency to keep leadership apprised10Articulation of ResponseSubmission has no major errors related to citations, grammar, spelling, syntax, or organizationSubmission has major errors related to citations, grammar, spelling, syntax, or organization that negatively impact readability and articulation of main ideasSubmission has critical errors related to citations, grammar, spelling, syntax, or organization that prevent understanding of ideas8Total:100%