Project Planning and Project Execution

Johath3

PLEASE READ THE INSTRUCTION COMPLETELY:

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 create a project schedule using the provided template, and evaluate the project manager’s management of team members, resources, conflict, and engagement with project stakeholders.

Prompt: The goal of this milestone is to delve more deeply into the project planning and project execution areas of project management. Use the ECO-Trans case study (in MindEdge) as you 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 approachagile or waterfall projectfor 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.

page1image17744

Rubric
Guidelines for Submission: Your draft of the Project Planning and Project Execution portions of your final project should adhere to the following formatting

requirements: 34 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.

Instructor Feedback: This activity uses an integrated rubric in Blackboard. Students can view instructor feedback in the Grade Center. For more information, review these instructions.

page2image6072
page2image6232
page2image6656
page2image6816
page2image6976
page2image7136
page2image7296
page2image7720
page2image7880
page2image8040
page2image8200
page2image8624
page2image8784
page2image8944
page2image9104
page2image9264
page2image9424

Critical Elements

Proficient (100%)

Needs Improvement (75%)

Not Evident (0%)

Value

page2image12064
page2image12224
page2image12384
page2image12544
page2image12704
page2image12864
page2image13288
page2image13448
page2image13608
page2image13768
page2image13928
page2image14088
page2image14248
page2image14408
page2image14568
page2image14728

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

page2image20600
page2image20760
page2image20920
page2image21080
page2image21240
page2image21400
page2image21560
page2image21720
page2image21880
page2image22040
page2image22200
page2image22360
page2image22520
page2image22680
page2image22840
page2image23000
page2image23160

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 the requirements

provide

8

page2image28968
page2image29128
page2image29288
page2image29448
page2image29608
page2image29768
page2image29928
page2image30088
page2image30248
page2image30408
page2image30568
page2image30728
page2image30888
page2image31048
page2image31208
page2image31368
page2image31528

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

page2image36688
page2image36848
page2image37008
page2image37168
page2image37328
page2image37488
page2image37912
page2image38072
page2image38232
page2image38392
page2image38552
page2image38712
page2image38872
page2image39032
page2image39192
page2image39352

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

page2image45192
page2image45352
page2image45512
page2image45672
page2image45832
page2image45992
page2image46416
page2image46576
page2image46736
page2image46896
page2image47056
page2image47216
page2image47376
page2image47536
page2image47696
page2image47856

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

page2image54008
page2image54432
page2image54592
page2image54752
page2image54912
page2image55072
page2image55232
page2image55392
page2image55552
page2image55712
page2image55872

 

page3image1568
page3image1736
page3image2160
page3image2320
page3image2480
page3image2640
page3image2800
page3image2960
page3image3120
page3image3280
page3image3440
page3image3864
page3image4024
page3image4184
page3image4344
page3image4504
page3image4664

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 dura the project tasks

tion of

10

page3image10448
page3image10608
page3image10768
page3image10928
page3image11088
page3image11248
page3image11672
page3image11832
page3image11992
page3image12152
page3image12312
page3image12472
page3image12632
page3image12792
page3image12952
page3image13112

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

page3image17272
page3image17432
page3image17592
page3image17752
page3image17912
page3image18072
page3image18232
page3image18392
page3image18552
page3image18712
page3image18872
page3image19032
page3image19192
page3image19352
page3image19512
page3image19672
page3image19832

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

page3image24688
page3image24848
page3image25008
page3image25168
page3image25328
page3image25488
page3image25648
page3image25808
page3image25968
page3image26128
page3image26288
page3image26448
page3image26608
page3image26768
page3image26928
page3image27088
page3image27248

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

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 explain how the project schedule can be resource leveled, fast-tracked, or crashed

Does not propose communication approaches and frequency to keep leadership apprised

10

page3image35488
page3image35648
page3image35808
page3image35968
page3image36128
page3image36288
page3image36712
page3image36872
page3image37032
page3image37192
page3image37352
page3image37512
page3image37672
page3image37832
page3image37992
page3image38152

Project Execution: Keep Leadership Apprised

Proposes communication approaches and frequency to keep leadership apprised of the project execution, using examples to support claims

10

page3image41120
page3image41280
page3image41440
page3image41600
page3image41760
page3image41920
page3image42344
page3image42504
page3image42664
page3image42824
page3image42984
page3image43144
page3image43304
page3image43464
page3image43624
page3image43784

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

page3image49224
page3image49384
page3image49544
page3image49704
page3image49864
page3image50456
page3image50616
page3image50776
page3image50936
page3image51096
page3image51256
page3image51416

Total

100%

page3image52472
page3image52896
page3image53056
  • 9 years ago
  • 25
Answer(1)

Purchase the answer to view it

NOT RATED
  • project_planning_and_project_execution.docx