Scrum Framework

1

JIRA is a popular project management and issue-tracking tool primarily used for agile software development. Here's how it works, including the terms you mentioned:

1. Core Concepts in JIRA

  • Projects: A container for all issues, tasks, and workflows. Each project represents a specific initiative or team.

  • Issues: Generic term for any task, bug, enhancement, or project work in JIRA. Issues are categorized as different types (e.g., Epics, Stories, Tasks, Bugs).

2. Key Agile Terms in JIRA

Epic

  • Definition: A large piece of work that can be broken down into smaller, more manageable tasks (Stories, Tasks, or Bugs).

  • Purpose: Used to group related work and represent a high-level objective.

  • Example: "Implement a User Login System" could be an Epic with Stories for front-end design, back-end logic, and API integration.

Story

  • Definition: A user-centric requirement or feature, often written as a user story (e.g., "As a user, I want to reset my password so I can regain access to my account").

  • Purpose: Captures specific functionality or a piece of work tied to user needs.

  • Relationship to Epic: Stories are children of Epics.

Story Points

  • Definition: A unit of measurement used to estimate the effort and complexity of a Story.

  • Purpose: Helps teams predict how much work they can complete in a Sprint. Often based on Fibonacci numbers (e.g., 1, 2, 3, 5, 8).

  • Determination: Teams assign story points based on the relative size, complexity, and effort required.

Task

  • Definition: A smaller piece of work, often technical or administrative, that may not directly relate to a user story.

  • Purpose: Tracks specific actions or assignments.

  • Difference from Stories: Stories focus on user outcomes, whereas tasks focus on the steps to achieve them.

Bug

  • Definition: An issue reported in the system, often related to defects in code or functionality.

  • Purpose: Ensures defects are tracked, prioritized, and resolved.

3. Agile Processes in JIRA

Sprint

  • Definition: A time-boxed period (usually 1-4 weeks) during which a team works on a set of tasks or stories.

  • How It Works:

    1. Planning: Teams select issues from the backlog to include in the Sprint.

    2. Execution: Teams work on completing the Sprint tasks.

    3. Review: The Sprint ends with a demonstration of the completed work (Sprint Review).

Scrum

  • Definition: A popular agile framework for managing complex work. JIRA's Scrum board visualizes the progress of work items.

  • Key Elements in Scrum:

    • Product Backlog: A prioritized list of work (Epics, Stories, Bugs) to be completed.

    • Sprint Planning: Meeting to decide the scope of the upcoming Sprint.

    • Daily Standups: Short meetings to discuss progress, blockers, and plans for the day.

    • Sprint Review: Presentation of completed work to stakeholders.

    • Sprint Retrospective: Team reflection to identify improvements for future Sprints.

Retrospective

  • Definition: A dedicated meeting at the end of a Sprint to evaluate what went well, what didn’t, and what can be improved.

  • Purpose: Drives continuous improvement by addressing team dynamics, workflows, or technical challenges.

  • Common Techniques: "Start, Stop, Continue" or "What Went Well, What Could Be Better, What Actions Can We Take?"

How Teams Use JIRA

  1. Creating Backlogs: Teams use the backlog to plan and prioritize work.

  2. Planning Sprints: Selected items from the backlog are moved into an active Sprint.

  3. Tracking Progress: Scrum or Kanban boards visually represent work progress (e.g., "To Do," "In Progress," "Done").

  4. Logging Time: Developers log time against tasks to track effort.

  5. Reviewing Reports: JIRA offers analytics like burndown charts, velocity charts, and Sprint reports for performance tracking.

Summary Workflow in JIRA:

  1. Create an Epic for high-level goals.

  2. Break down the Epic into Stories and Tasks.

  3. Assign Story Points to estimate effort.

  4. Plan and execute work in Sprints using the Scrum framework.

  5. Fix issues identified as Bugs.

  6. Reflect and improve in a Retrospective.

2

Scrum vs Kanban

What is Kanban?

Kanban is a visual workflow management methodology used to optimize processes, improve efficiency, and increase team collaboration. Originating from lean manufacturing, it is now widely used in software development and other industries for agile project management.

Kanban focuses on managing work-in-progress (WIP) and delivering continuous value without fixed iterations, making it highly flexible.

Core Principles of Kanban

  1. Visualize Work

    • Use a Kanban board to represent the workflow and tasks visually. Tasks are represented as "cards" that move across columns representing stages of work (e.g., "To Do," "In Progress," "Done").

  2. Limit Work-In-Progress (WIP)

    • Set WIP limits for each workflow stage to prevent overloading and ensure focus on completing existing tasks before starting new ones.

  3. Focus on Flow

    • Continuously monitor how work progresses through the system, identifying bottlenecks and inefficiencies.

  4. Continuous Improvement

    • Use metrics and team feedback to make incremental improvements over time.

  5. Make Process Policies Explicit

    • Clearly define how work is done at each stage and establish transparent guidelines for managing the workflow.

How Kanban Works

  1. Kanban Board

    • A Kanban board is the primary tool for implementing Kanban. It consists of:

      • Columns: Represent stages in the workflow (e.g., "Backlog," "In Progress," "Testing," "Done").

      • Cards: Represent individual tasks, features, or bugs. Each card contains details about the task, such as description, assignee, priority, and deadlines.

  2. Workflow Stages

    • Work items move across the columns as they progress through the workflow.

    • Typical stages might include:

      • To Do: Tasks waiting to be started.

      • In Progress: Tasks currently being worked on.

      • Review/Testing: Tasks undergoing review or testing.

      • Done: Completed tasks.

  3. WIP Limits

    • Define the maximum number of tasks allowed in each stage to prevent bottlenecks. For example:

      • "In Progress" may have a WIP limit of 3 to ensure focus and prevent multitasking.

  4. Pull System

    • Work is "pulled" from one stage to the next only when there is capacity, rather than "pushed" by deadlines or external pressure.

Key Metrics in Kanban

  1. Cycle Time

    • The time it takes for a task to move from start to completion. Shorter cycle times indicate a smoother workflow.

  2. Lead Time

    • The total time from when a task is added to the backlog to when it is completed.

  3. Throughput

    • The number of tasks completed over a specific period, reflecting productivity.

Kanban vs. Scrum

Feature

Kanban

Scrum

Iterations

Continuous delivery, no fixed iterations

Time-boxed Sprints (e.g., 1-4 weeks)

WIP Management

WIP limits at each stage

Sprint backlog defines scope

Board Type

Simple columns with WIP limits

Scrum board with Sprint and backlog focus

Roles

No predefined roles

Defined roles: Product Owner, Scrum Master, Team

Flexibility

Highly flexible, adaptive

Structured, iterative

When to Use Kanban

  • You need a flexible workflow without strict deadlines.

  • Work arrives continuously, rather than in predefined batches (e.g., support tickets).

  • Teams want to focus on flow and manage tasks efficiently.

3

How Scrum works?

The Scrum framework is an agile methodology designed to help teams deliver value incrementally and iteratively. It emphasizes collaboration, flexibility, and continuous improvement through defined roles, events, and artifacts.

Core Elements of Scrum

  1. Roles

  2. Artifacts

  3. Events

1. Roles in Scrum

Scrum defines three roles to ensure accountability and collaboration:

a. Product Owner

  • Responsibilities:

    • Owns the Product Backlog and ensures it is well-organized and prioritized.

    • Represents the customer’s or stakeholders’ interests.

    • Defines the product vision and goals.

    • Ensures the team is building the right product by providing clear requirements.

b. Scrum Master

  • Responsibilities:

    • Serves as a facilitator and coach for the Scrum team.

    • Removes impediments to ensure smooth progress.

    • Guides the team on Scrum practices and principles.

    • Shields the team from distractions and external interferences.

c. Development Team

  • Responsibilities:

    • Self-organizing professionals who execute the work.

    • Responsible for delivering a “Done” product increment at the end of each Sprint.

    • Collaborates closely to achieve Sprint goals.

2. Artifacts in Scrum

a. Product Backlog

  • A prioritized list of everything that might be needed in the product.

  • Items include Epics, Stories, Tasks, and Bugs.

  • Continuously refined (groomed) by the Product Owner.

b. Sprint Backlog

  • A subset of Product Backlog items selected for the current Sprint.

  • Includes tasks the team plans to work on during the Sprint and the plan for achieving the Sprint Goal.

c. Increment

  • The sum of all completed Product Backlog items during a Sprint.

  • Represents the latest version of the product and must meet the Definition of Done (DoD).

3. Events in Scrum

Scrum events (or ceremonies) provide structure and regular opportunities for inspection and adaptation:

a. Sprint

  • Definition: A fixed-length time-box (usually 1–4 weeks) where the team works to complete a set of backlog items.

  • Goal: Deliver a potentially shippable product increment.

  • Important Notes:

    • No changes are made to the Sprint scope after it starts.

    • Each Sprint is followed by a review and retrospective.

b. Sprint Planning

  • Purpose: Define what can be delivered in the Sprint and how the work will be achieved.

  • Participants: Entire Scrum team.

  • Outputs:

    • A Sprint Goal: A concise objective for the Sprint.

    • A Sprint Backlog: Selected tasks for the Sprint and the plan to complete them.

c. Daily Scrum (Stand-up)

  • Purpose: A short, time-boxed meeting (15 minutes) for the Development Team to:

    • Inspect progress toward the Sprint Goal.

    • Identify blockers.

    • Plan work for the day.

  • Typical Questions:

    1. What did I do yesterday?

    2. What will I do today?

    3. Are there any impediments?

d. Sprint Review

  • Purpose: Present the completed work to stakeholders at the end of the Sprint for feedback.

  • Participants: Scrum Team and stakeholders.

  • Outcome: Updated Product Backlog with new ideas and priorities.

e. Sprint Retrospective

  • Purpose: Reflect on the Sprint to identify:

    • What went well.

    • What didn’t go well.

    • What can be improved in future Sprints.

  • Outcome: An actionable plan for continuous improvement.

Scrum Workflow

  1. Backlog Refinement: Product Owner ensures the backlog is up-to-date and prioritized.

  2. Sprint Planning: Scrum Team selects work items for the Sprint Backlog.

  3. Execution: Development Team works on backlog items, updating the Scrum board and attending daily stand-ups.

  4. Sprint Review: Team demonstrates completed work to stakeholders.

  5. Retrospective: Team identifies and plans improvements for the next Sprint.

  6. Repeat: Begin the next Sprint cycle.

Key Characteristics of Scrum

  • Empirical Process Control: Scrum is built on transparency, inspection, and adaptation.

  • Time-boxing: All events and activities are strictly time-limited.

  • Focus on Incremental Delivery: Deliver small, valuable increments of the product frequently.

  • Self-Organizing Teams: Teams decide how to accomplish their work without external direction.

When to Use Scrum

  • When requirements are complex or likely to change.

  • For projects requiring frequent feedback and continuous delivery.

  • When collaboration across cross-functional teams is critical.

Would you like to discuss how to implement Scrum in your specific project or team?

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

PreviousGLiNERNextSQLAlchemy and Alembic

Last updated