Agile_Scrum_ITPM_Lecture_10_08_2024

Agile Scrum Overview

  • Agile Scrum is a framework for IT project management.

  • Focuses on delivering high business value quickly.

Ice Breaker Discussion

  • Question posed: Which Marvel superhero would help you during a busy week?

What is Scrum?

  • Agile process for delivering working software in short iterations (2-3 weeks).

  • Product owner negotiates priorities with the team.

  • Teams self-organize to deliver high priority features.

Principles of Scrum

  • Incremental project completion.

  • Close stakeholder collaboration.

  • Flexible development process.

  • Continuous customer involvement.

  • Reduces risk and enhances transparency.

  • Emphasizes communication.

Characteristics of Scrum

  • Requirements captured in a "product backlog."

  • Self-organizing and cross-functional teams.

  • Products are developed in sprints.

  • Agile environment through generative rules.

The Sprint

  • Time-boxed period (1 month or less).

  • Fixed scope with a clear goal; no changes during the sprint.

  • Quality standards maintained.

Sprint Clarifications

  • Scope can be clarified or re-negotiated.

  • Sprints can be canceled due to market changes or company direction shifts.

Requirement Gathering in Scrum

  • Stakeholder identification and needs assessment.

  • Requirement prioritization and documentation.

  • Feedback cycles for agreement finalization.

Scrum Framework Components

  • Roles: Product Owner, Scrum Master, Scrum Team.

  • Events: Sprint planning, review, and retrospective.

  • Artifacts: Product backlog, sprint backlog, increments.

Scrum Roles

  1. Product Owner:

    • Defines product features and release dates.

    • Responsible for product profitability.

  2. Scrum Master:

    • Ensures adherence to Scrum practices.

    • Removes impediments for the team.

  3. Scrum Team:

    • Cross-functional, self-organizing team (5-9 members).

Change Management Scenario

  • Steps to handle priority changes include discussing with the Product Owner, assessing impact on goals, involving the team, and documenting decisions for retrospectives.

Scrum Events Details

  • Sprint Planning: Team commits to backlog items for the sprint.

  • Sprint Review: Team presents accomplished items through demos.

  • Sprint Retrospective: Reflects on what worked and areas for improvement.

  • Daily Scrum: Stand-up meeting to discuss progress and blockers.

Artifacts in Scrum

  • Product Backlog: Ordered list of requirements.

  • Sprint Backlog: Foreseen functionality for the next increment.

  • Increments: Completed product backlog items demonstrating progress.

Burndown Chart

  • Visual representation of work remaining over time.

  • Tracks progress towards sprint completion.

Real-Life Example

  • A software company utilizing Scrum for e-commerce platforms.

  • Sprint process from planning to review and retrospective.

Advantages of Scrum

  • Enhanced communication and focus on problem resolution.

  • Increases project transparency.

  • Constant focus on quality leads to fewer mistakes.

Disadvantages of Scrum

  • Risk of scope creep.

  • High project failure risk with lack of commitment.

  • Challenging to implement in large teams.

  • Dependency on experienced team members.