Agile Project Management

by


MGMT 642: Agile Project Management (HBD-SUMMER24-07)

Final Project Submission: Advanced Scrum Project Management

Objective: To expand upon the initial project submitted earlier in the term by applying advanced Scrum practices covered in Chapters 1, 5, 6, 7, 8, 9, and 12 of “Project Management the Agile Way.” This final submission requires comprehensive project management using Scrum principles, documented in JIRA and Confluence, with screenshots demonstrating the completion of each section.

Project Overview: This final project is a continuation and refinement of the initial Scrum project your group submitted in the first half of the term. You will enhance your initial work by incorporating advanced Scrum practices, focusing on refining the product backlog, sprint planning, estimation, team dynamics, governance, and transitioning strategies.

Project Tasks:

  1. Refinement of the Product Backlog (Chapters 1 & 5):
    • A. Review and refine the product backlog from your initial submission. Ensure user stories are clear, concise, and follow the format: “As a [user], I want [functionality], so that [benefit].”
    • B. Prioritize user stories using the MoSCoW method (Must have, Should have, Could have, Won’t have this time). Ensure the product backlog is organized based on business value, risk, and dependencies.
    • **C. Add acceptance criteria to each user story to define the conditions of satisfaction.
    • Document: Record all refined user stories and acceptance criteria in Confluence.
    • Screenshots Required: Updated product backlog from JIRA, showing user stories, priorities, and acceptance criteria.
  2. Sprint Planning and Sprint Backlog Creation (Chapter 6):
    • A. Conduct a sprint planning session to define the sprint goal and select user stories from the product backlog for the upcoming sprint.
    • **B. Break down selected user stories into actionable tasks and create a sprint backlog in JIRA.
    • **C. Estimate tasks using Scrum estimation techniques such as Planning Poker and Story Points.
    • Document: Outline the sprint planning process, sprint goal, selected user stories, and estimated tasks in Confluence.
    • Screenshots Required: Sprint backlog, task board, and estimation details from JIRA.
  3. Burndown Charts and Sprint Reviews (Chapter 7):
    • A. Track progress using a burndown chart in JIRA. Monitor the completion of tasks and user stories throughout the sprint.
    • **B. Conduct a sprint review at the end of each sprint to demonstrate the work completed and gather feedback from stakeholders.
    • Document: Summarize the sprint review outcomes and any feedback received in Confluence.
    • Screenshots Required: Burndown chart and sprint review board from JIRA.
  4. Team Dynamics and Retrospectives (Chapter 8):
    • A. Reflect on team dynamics throughout the project. Assess areas such as trust, collaboration, and communication within the team.
    • **B. Conduct a sprint retrospective at the end of each sprint to identify what went well, what could be improved, and actionable steps for future sprints.
    • Document: Record the findings and action items from each sprint retrospective in Confluence.
    • Screenshots Required: Retrospective board and team performance charts from JIRA.
  5. Governance and Scrum Roles (Chapter 9):
    • A. Define the governance framework for your Scrum project, including the roles of the Product Owner, Scrum Master, and Development Team.
    • **B. Outline the decision-making processes and conflict resolution strategies within the team.
    • **C. Identify key risks to the project and develop a risk mitigation plan using JIRA.
    • Document: Describe the governance framework, roles, and risk management strategies in Confluence.
    • Screenshots Required: Risk register and role assignments in JIRA.
  6. Transition Strategy and Continuous Improvement (Chapter 12):
    • A. Develop a transition strategy for moving from your current project state to a fully Agile Scrum framework, if not already implemented.
    • **B. Outline a plan for continuous improvement, focusing on how your team will regularly assess and adapt Scrum practices.
    • Document: Detail the transition strategy and continuous improvement plan in Confluence.
    • Screenshots Required: Transition plan and improvement strategy board in JIRA.

Submission Requirements:

  • Format: Compile all documentation into a single PDF file, including screenshots from JIRA and Confluence for each section.
  • Screenshots: Ensure all screenshots are clear and demonstrate the completed sections of the project in JIRA and Confluence.

Assessment Criteria:

  1. Completeness and clarity of the refined product backlog and user stories.
  2. Effectiveness of sprint planning and backlog creation.
  3. Accurate use of Scrum estimation techniques and burndown charts.
  4. Insightful analysis of team dynamics and constructive retrospectives.
  5. Robustness of governance framework and defined Scrum roles.
  6. Practicality and effectiveness of the transition strategy and continuous improvement plan.
  7. Proper use of Scrum tools (JIRA and Confluence): Demonstrated through comprehensive screenshots and documentation.

Suggested Resources:

  • JIRA and Confluence tutorials and guides.
  • “Project Management the Agile Way” Chapters 1, 5, 6, 7, 8, 9, and 12.
  • Additional Scrum and Agile resources.