Scrum Events allows teams and organizations to iteratively and incrementally deliver valuable products of “Done” working releasable software within a Sprint. Key Scrum Events are Sprint, Sprint Planning, Sprint Goal, Daily Scrum, Sprint Review & Sprint Retrospective. Scrum defines five Scrum Events or Scrum Ceremonies, The Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint […]
Sprint Retrospective is to plan ways to increase quality and effectiveness. It is an opportunity for teams to reflect on their journey, refine their processes, and set the stage for continuous improvement. This blog unravels the significance of the Sprint Retrospective, exploring its purpose, key practices, and the transformative impact it can have on team
Sprint Retrospective – Tips to improve & spice up Read More »
4Ls stands for Liked Learned Lacked Longed and it is a brainstorming technique for collecting feedback on a recently completed project or piece of work. This retrospective highlights the positive (liked & learned) as well as the negative (lacked & longed for). The team has to think mostly from a factual (what happened) perspective, rather
The Sailboat Retrospective is a fun and creative way for teams to reflect on the sprint and identify areas for improvement. It’s called “Sailboat” because the metaphor of a sailboat helps the team visualize their journey, the obstacles they faced, and the direction they want to sail towards in the future. The Sailboat or Speedboat
The Starfish Method for Sprint Retrospectives is an easy way to achieve focus, give a voice to every member, and foster the thinking around practices and the value the team gets from them. It helps teams reflect on varying degrees of actions and activities rather than simply the traditional what went well or what did
A Mad Sad Glad retrospective is a simple and effective way for teams to reflect on their previous sprint. It involves identifying things that made the team feel happy, things that made them feel sad, and things that made them feel angry or frustrated. By focusing on these three areas, the team can identify what
Start Stop and Continue is a great format to focus on the things that are working (CONTINUE), things that are not working (STOP), and things that the team should start doing (START). Its focuses on the past, present, and future at the same time. It is an action-oriented retrospective technique that encourages participants to come
Studying and Dissecting a problem to identify the root cause is called Fact Based Analysis. It also evaluates potential solutions to ensure it is being implemented in the most beneficial way. Below mentioned techniques can be applied during Sprint Retrospectives. The problem-solving process in fact based analysis has six steps: Define the problem Analyze the problem
RAID Analysis is an acronym for Risks, Assumptions, Issues, and Dependencies. All projects large and small have risks, issues, dependencies, and assumptions. Managing them is one of the most time-consuming activities but done well, the effort is paid off by fewer delays and cost over-runs, better-informed stakeholders, more support for the project, and better delivery
RAID Analysis: Risks, Assumptions, Issues, Dependencies Read More »
