OnlineNursingOwl
← All nursing posts

Management · Studypool

Project Scope & Time Management

Post ID: 3461208

please use microsoft project

Deliverable 2: Project Scope & Time Management

Project Scope Management

Tasks:

  • Draft a scope statement based on stakeholder needs.
  • Define and document a detailed project and product description.
  • Create a Work Breakdown Structure (WBS) with at least 4 levels, reflecting both traditional and agile components.
  • Verify scope and formalize acceptance criteria.
  • Define a scope change management plan incorporating agile sprint reviews and backlog refinement.

Project Time Management

Tasks:

  • Define, sequence, and estimate activities, resources, and durations.
  • Create a hybrid Gantt Chart (MS Project or GanttProject) showing milestones, dependencies, and critical path.
  • Explicitly identify schedule slack (total and free).
  • Document the WBS and schedule in MS Project or GanttProject.
  • Add Agile sprint cycles or iterations in parallel with the traditional plan.

Assessment Formatting Guidelines

Word Count

  • Maximum: 3,000 words (excluding title page, references, and appendices).

Document Structure

  • Title Page: Include assessment title, your name, student ID, course/module name, and date.
  • Table of Contents: Include if required.
  • Main Body: Organize using clear headings and subheadings.
  • Conclusion: Summarize key points and findings.
  • References: Full reference list in APA style.
  • Appendices: Optional; use only for supporting materials.

Formatting Style

  • Font: Times New Roman or Arial.
  • Font Size: 12 pt for body text, 14 pt bold for main headings.
  • Line Spacing: 1.5 throughout (single spacing for reference list).
  • Margins: 2.5 cm (1 inch) on all sides.
  • Alignment: Justified text.
  • Page Numbers: Bottom-right corner, starting from the introduction page.

Referencing

  • Use APA Style.
  • All in-text citations must match the reference list.
  • Reference list should begin on a new page.

Figures and Tables

  • Label all figures and tables (e.g., Figure 1: Title, Table 1: Title).
  • Place as close as possible to the relevant text.
  • Always cite the source if not original.

Rubric

Linked CLOs:

  • CLO 2 (Deliverables)
  • CLO 4 (Critical path/time management)
  • CLO 1 (Organizational factors)
Criteria A (90–100) A-, B+, B (80–89) B-, C+, C (70–79) C-, D+, D (60–69) F (0–59) Linked CLOs
Scope Statement & Description (10%) Scope is comprehensive, precise, and validated with stakeholders; includes detailed acceptance criteria and aligns with organizational/cultural context. Demonstrates deep critical thinking about stakeholder conflicts and scope creep. Scope is clear and structured, includes most details and acceptance criteria, but minor weaknesses in validation or alignment. Basic scope provided, limited detail or vague acceptance criteria. Weak scope statement; fails to reflect actual stakeholder needs. Missing or irrelevant. CLO 2
Work Breakdown Structure (WBS) (30%) WBS is highly detailed with 4+ levels, integrates both traditional and Agile elements (e.g., sprints, backlog items). Logical hierarchy with deliverables, tasks, and subtasks that demonstrate understanding of hybrid PM. WBS is clear with 4 levels, mostly logical, some attempt to include Agile. WBS is adequate but shallow, missing Agile or logical flow. Minimal or inconsistent WBS with missing levels. No WBS. CLO 2
Schedule (Gantt, Dependencies, Slack, Critical Path) (30%) Schedule is comprehensive: hybrid Gantt chart shows milestones, dependencies, critical path, total/free slack, Agile sprints alongside waterfall phases. Demonstrates mastery of scheduling tools. Good Gantt chart, clear dependencies, includes milestones, some attempt to show slack or Agile cycles. Adequate schedule but lacks critical path analysis, slack, or Agile components. Minimal schedule, poorly sequenced. No schedule submitted. CLO 4
Scope Change Management Plan (30%) Highly detailed change management plan: incorporates Agile sprint reviews, backlog refinement, stakeholder approval processes. Anticipates risks of scope creep and offers solutions. Clear change plan with Agile elements, but not fully detailed. Some scope change process mentioned, but weak or limited to traditional approach. Minimal and unclear plan. No change management approach. CLO 1, CLO 2, CLO 4

I will provide more hint and answer to follow.