Scrum

Scrum is an agile project management framework that helps teams organize and manage their work through roles, practices, and principles. It is popular in software development but is applicable to any team setting.

Scrum Core Components

1. Sprint

• A time-boxed period (typically 1-4 weeks) where the team focuses on completing specific tasks.

• Sprint Planning: The product backlog is created, and tasks are prioritized.

• Work Process: No new tasks are added during the sprint unless urgent. Daily stand-up meetings ensure focus.

2. Roles in Scrum

• Product Owner: Responsible for vision, requirements, and managing the backlog.

• Scrum Master: Guides the team and ensures Scrum principles are followed.

• Development Team: Executes tasks and completes sprint goals.

3. Scrum Artifacts

• Product Backlog: A list of all project tasks managed by the product owner.

• Sprint Backlog: Tasks selected for the current sprint.

• Increment: The completed part of the product, ready for use.

Toote Backlog

In Scrum, the Product Backlog is a central artifact where all potential ideas, deliverable tasks, functions, or activities the team will work on are listed. It is prioritized and proactively managed throughout the project's lifecycle.

Sprint Results and Managing Technical Debt

• At the end of a sprint, goal achievement is analyzed. Unfinished tasks return to the backlog as technical debt for the next sprint.

• Managing Technical Debt: Allocate 10% of work time to address technical debt, and use retrospectives for process and communication improvement.

• Task Estimation: Simplifies sprint and daily planning, aiding task and resource allocation.

• Methods: Time-based estimation (hours) and difficulty-based estimation (person-hours).

Scrum Framework Statements:

• True: Scrum teams are cross-functional and collaborate closely to deliver value. They work in short cycles called sprints, meeting daily to discuss progress.

• False: Scrum is not a Waterfall methodology.

Story Points:

• Tasks are estimated relative to each other, starting with simpler tasks before tackling more complex ones.

• Planning Poker is the most effective estimation method, involving the whole team or a subset of it. Planning Poker is a collective way to estimate the effort of tasks in Scrum teams. It uses Fibonacci numbers (0, 1, 2, 3, 5, 8, 13, 20, 40, 100) for story points. Special cards, like a question mark (?), infinity (∞), and coffee cup (☕), are used for uncertainty, complexity, and breaks, respectively.

Scrum Meetings:

1. Sprint Planning: Define tasks and goals.

2. Daily Standup: 15-minute progress check.

3. Sprint Review: Review completed work and gather feedback.

4. Sprint Retrospective: Discuss improvements for future sprints.