Agile, Scrum, Kanban, WIP(Work in Progress)

Agile Frameworks

Scrum

• Iterative and incremental framework for managing and completing complex projects
• Core values: Focus, Commitment, Courage, Openness, Respect
• Three roles:
  • Product Owner: responsible for product backlog and prioritization
  • Scrum Master: facilitates Scrum process and ensures team follows framework
  • Development Team: develops and delivers working product increment
• Three artifacts:
  • Product Backlog: prioritized list of features or requirements
  • Sprint Backlog: set of tasks to be completed during a sprint
  • Increment: sum of all product backlog items completed during a sprint
• Timeboxed sprints: 2-4 weeks, with daily Scrum meetings and sprint reviews

Kanban

• Visual system for managing work, emphasizing continuous flow and limiting WIP
• Core principles:
  • Visualize the workflow
  • Limit WIP
  • Focus on flow
  • Continuously improve
• Key elements:
  • Board: visual representation of workflow
  • Columns: stages of work (e.g., to-do, in-progress, done)
  • Cards: individual tasks or items
  • WIP limits: constraints on the number of tasks in each column
• No predefined roles or ceremonies, unlike Scrum

Work In Progress (WIP)

• Measure of the amount of work being processed at a given time
• Important in Agile frameworks, as it helps teams:
  • Manage workload and capacity
  • Identify bottlenecks and areas for improvement
  • Make informed decisions about prioritization and resource allocation
• WIP limits:
  • Help teams avoid overcommitting and reduce waste
  • Encourage continuous flow and delivery of working products
  • Enable teams to focus on a manageable amount of work at a time

Agile Frameworks

Scrum

• Scrum is an iterative and incremental framework for managing complex projects
• Core values: Focus, Commitment, Courage, Openness, and Respect
• Three roles: Product Owner, Scrum Master, and Development Team
• Product Owner: responsible for product backlog and prioritization
• Scrum Master: facilitates Scrum process and ensures team follows framework
• Development Team: develops and delivers working product increment
• Three artifacts: Product Backlog, Sprint Backlog, and Increment
• Product Backlog: prioritized list of features or requirements
• Sprint Backlog: set of tasks to be completed during a sprint
• Increment: sum of all product backlog items completed during a sprint
• Timeboxed sprints: 2-4 weeks, with daily Scrum meetings and sprint reviews

Kanban

• Kanban is a visual system for managing work, emphasizing continuous flow and limiting WIP
• Core principles: Visualize the workflow, Limit WIP, Focus on flow, and Continuously improve
• Key elements: Board, Columns, Cards, and WIP limits
• Board: visual representation of workflow
• Columns: stages of work (e.g., to-do, in-progress, done)
• Cards: individual tasks or items
• WIP limits: constraints on the number of tasks in each column
• No predefined roles or ceremonies, unlike Scrum

Work In Progress (WIP)

• WIP is a measure of the amount of work being processed at a given time
• Importance of WIP in Agile frameworks:
  • Managing workload and capacity
  • Identifying bottlenecks and areas for improvement
  • Making informed decisions about prioritization and resource allocation
• WIP limits:
  • Help teams avoid overcommitting and reduce waste
  • Encourage continuous flow and delivery of working products
  • Enable teams to focus on a manageable amount of work at a time

Learn about the Scrum framework, its core values, roles, and artifacts in managing complex projects