Agile Methodology

Product Cheatsheet

What is Agile? Scrum Kanban

Agile is an iterative approach to project management Overview
and software development that helps teams deliver Kanban is a lean and JIT
(just-in-time) development
value to their customers faster.
methodology adopted in the
A quick recap on why the development moved manufacturing sectors for a
long time now and
towards Agile:
originated from Japan.

Point Reasoning Kanban Process

A Kanban dashboard is used to track work progress
No one can chart out requirements perfectly In this methodology, each person would be performing a single task at a time
Changing
on day-1 and once done it would be moved to the next person
requirements
Requirements keeps changing There are no defined roles and timeline-like sprints
Overview Focuses on "Work-in-progress" items
Developing and testing at the end was Helps teams work together and encourages to improve continuously Tasks will be pushed to live continuously and/or as per the team’s discretion
Better project overwhelming Break the work and complete the work in sprints after completion
control Any issues can be corrected before entire Sprint is a time-boxed iteration which lasts from 1 week to 4 weeks Any change requests would be included immediately
project completes 3 roles: Product Owner, Development team, Scrum Master This method is ideal for projects that are in maintenance mode with minor
developments
Waterfall method: customers weren’t aware Product Owner
until project is delivered Gets the input from executives, stakeholders, customers, users and prepares
Customer
Agile methodology: customer can get few the product backlog Scrumban
Satisfaction
features of project for usage even before Product backlog is an ordered list of product requirements that a scrum team Overview
project is half-done maintains for a product
Scrumban is an Agile development
Sprint planning: a plan made before starting of the sprint with all members
As client is given few features of product to methodology, it combines the
use, real-time feedback can be received structure of Scrum with the flow-
Reduced Risks
Development Team
Product can be launched phase-wise based methods of Kanban.
Core team that develops the product
Product can be altered before it is fully ready
This takes the best of both Scrum
Scrum Master
Based on real-time feedback and iterations, and Kanban
High product Takes development items from the product backlog, conducts daily standup
company always gives product with high Scrum + Kanban = Scrumban
quality meeting and maintains the sprint burn-down chart
quality Daily scrum: stand up meeting for discussing yesterday’s work, today’s plan,
Kanban Process
and difficulties
This method uses roles and fixed length sprints like Scrum
How do I implement Agile? Sprint burndown chart: Publicly displayed chart showing remaining work in
the sprint backlog. Days in sprint vs Work remaining in each day
Focusses on "Work-In-Progress" like Kanban
Tasks for development are prioritized ahead of the sprint and shared with the
Following are the most commonly used frameworks to
stakeholders
implement the Agile methodology: Note
Priority Changes would be included in the sprint and other planned tasks would
Sprint Retrospective is done at the end of each sprint for stakeholders to
Scrum understand how the product is getting shaped and feedback is given at the
be moved to the next sprint, maintaining the work-in-progress tasks
Includes the change in requirements within the sprint
Kanban initial stage itself
Can be preferred when the project is in maintenance mode and major
Any changes in the backlog will be handled in the next sprint
Scrumban developments are under process.