What is Scrum?
•Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible values.
•Scrum is an agile development methodology used in the development of Software based on an iterative and incremental
•Scrum is a framework for project management that emphasizes teamwork, accountability and iterative progress toward a well-defined goal. The framework begins with a simple premise: Start with what can be seen or known. After that, track the progress and tweak, as necessary.
•Scrum is often part of Agile software development. It is named for a rugby formation in which everyone plays a role.
•The primary objective of Scrum is to satisfy the customer’s need through an environment of transparency in communication, collective responsibility and continuous progress.
•Streamlined, no tons of documents, no lots of meeting, only have short and frequent meeting.
SCRUM MASTER
•The Scrum Master is responsible for facilitating the effective implementation of the Scrum framework and ensuring that the team adheres to its principles and practices.
•They act as a servant-leader and coach to the team, enabling their self-organization and promoting continuous improvement.
•The Scrum Master is essential in ensuring the successful implementation of the Scrum framework and maximizing the team’s productivity and effectiveness.
Sprint Planning
What Happens in Sprint Planning?
During sprint planning, the entire scrum team collaborates and discusses the desired high-priority work for the sprint and defines the sprint goal. The scrum master’s role is primarily to facilitate the meeting. The product owner describes the product goal and answers questions from the development team about execution and acceptance criteria of satisfaction. The developers the final say in how much of the high-priority work it can accomplish during the sprint.
Who Attends Sprint Planning?
Sprint planning involves the entire Scrum team: the development team, Product Owner, and Scrum Master.
How Long Should Sprint Planning Last?
Sprint planning is limited to a maximum of eight hours.
The general rule of thumb is to allow two hours of sprint planning for every one week of sprint length. That means teams should timebox sprint planning to four hours for a two-week sprint and eight hours for a one-month sprint.
KANBAN
•The word “kanban” itself is derived from Japanese and can be translated as “visual card” or “signboard.”
•Kanban is a popular framework used to implement Agile and DevOps software development.
•The method utilizes visual cues, typically represented by cards or sticky notes, to represent tasks, work items, or activities.
•These cards are usually arranged on a physical or digital board, which acts as a visual representation of the workflow or process.
WORKING OF KANBAN
1.Make work visible by breaking work down into work items called “cards” and placing them on a “kanban board.”
2.Limit work in progress.
3.Manage the flow of work.
4.Make process policies explicit.
5.Implement feedback loops.
6.Improve Collaboratively, Evolve Experimentally.
