Difference between Agile Scrum and Kanban

(Q). Difference between Agile Scrum and Kanban?

Scrum is an agile process that helps to deliver the business value in the shortest time. It rapidly and repeatedly inspects actual working software. It emphasizes on teamwork and iterative progress of the software. Its goal is to deliver new software every 2-4 weeks.

Kanban is a visual system for managing work. It visualizes both the process and the actual work passing through that process. The main objective of implementing Kanban is to identify potential bottlenecks in the process and fix them. Kanban goal is that work flow should proceed smoothly at an optimal speed.

	Kanban	Scrum
Role and Responsibilities	There are no pre-defined roles for a team. Although there may still be a Project Manager, the team is encouraged to collaborate and chip in when any one person becomes overwhelmed.	Each team member has a predefined role, where the Scrum master dictates timelines, Product owner defines goals and objectives and team members execute the work.
Due Dates / Delivery Timelines	Products and processes are delivered continuously on an as-needed basis (with due dates determined by the business as needed).	Deliverable are determined by sprints or set periods of time in which a set of work must be completed and ready for review.
Why Use?	Kanban methodology is designed to meet minimal resistance. So, it allows continuous small incremental and evolutionary changes to the current process. It also helps to achieve improvements regarding throughput, lead time and quality.	Scrum methodology can offer project management for every business, and even across life in general. By using Scrum, the development team becomes more Agile and discovering how to react quickly and respond to the sudden changes.
When to use?	Kanban boards allow visual management of software development project work. This helps team members to see work in progress. It also helps them to understand complex information like processes and risks associated to complete work on time.	Scrum methodology is used in a project where the requirement is rapidly changing. It works on a self-organizing, cross-functional team principle. The Scrum Framework usually deal with the fact that the conditions are likely to change quickly or most of the time not known at the start of the project.
Modifications / Changes	Allows for changes to be made to a project mid-stream, allowing for iterations and continuous improvement prior to the completion of a project.	Changes during the sprint are strongly discouraged.

Roles in agile scrum

(Q). What are the Roles in agile scrum?
The roles in Scrum are quite different from the traditional software methods. Clearly defined roles and expectations help individuals perform their tasks efficiently. In Scrum,there are mainly three roles Product Owner, Development Team, and Scrum Master.

Product Owner: 

• A Product Owner owns the Product backlog and writes user stories and acceptance criteria. 
• A Product Owner is responsible for prioritizing the Product Backlog is prioritized and decides the release date and the content. 
• A Product Owner accepts or rejects product backlog item.
• A Product Owner has the power to cancel the Sprint, if he thinks the Sprint goal is redundant.
• A Product Owner is the one who is responsible for the Return on Investment of the product.

Scrum Master: 

• A Scrum Master is not typically a manager or lead, but he is an influential leader and coach who does not do direct command and control. 
• A Scrum Master is a facilitator and Servant Leader who encourages and demands self-organization from the development team.
• A Scrum Master enables close cooperation across all roles and functions, addresses resource issue and disobedience of scrum practices. 
• A Scrum Master protects the team from external and internal distractions.        

Development Team:

• The Development Team is self-organizing, with a very high degree of autonomy and accountability.
• The Development Team decides how many items to build in a Sprint, and how best to accomplish that goal.
• The Development Team is a cross functional, small and self-organizing team which owns the collective responsibility of developing, testing and releasing the Product increment.
• The Development Team may not appoint any team lead since decisions are taken collectively by the team.

Ceremonies in Agile scrum

(Q). What are the ceremonies in Agile scrum?

Agile methodology is a practice that helps continuous iteration of development and testing in the SDLC process. Agile breaks the product into smaller builds. In this methodology, development and testing activities are concurrent, unlike other software development methodologies. It also encourages teamwork and face-to-face communication. Business, stakeholders, and developers and clients must work together to develop a product.

Agile Ceremonies in a Scrum

Scrum is a framework that helps teams work together. The Scrum Framework usually deals with the fact that the requirements are likely to change or most of the time not known at the start of the project. Each Scrum Project could have multiple Release Cycles and each release could have multiple sprints. There are a number of repeating sequence of meetings, to be held before, within and after the sprint cycle. There are some agile ceremonies below:

1. Sprint: A Sprint is a defined time period for developing features for a product. Within a Sprint, planned amount of work has to be completed by the team and made ready for review.
2. Refinement Meeting: The purpose of the backlog refinement meeting is to decompose the highest priority items in the product backlog into user stories which are suitable for inclusion in the next sprint.
3. Sprint Planning: It is done after refinement meeting. In this meeting product owner, scrum master, development team, QA team, come together and decides which user stories are need to complete in coming sprint.
4. Retrospective: In this sprint team reviews their work, identifying what they did well and what didn’t go as planned, so they can make the next sprint better.
5. Review: Goal of the review: showcase the work completed and receive feedback from the Product Owner and relevant stakeholders. Review done at the end of each sprint.
6. Stand-Up Meeting: Stand-Up meeting is daily meeting about what did you complete yesterday,
What will you work on today.