Scrum Ceremonies

Scrum defines several events (sometimes called ceremonies) that occur inside and outside each sprint:

1) Product Backlog Grooming:

Backlog grooming is the only ceremony in scrum that doesn’t have a defined time box or even a frequency.

It is, however, a critical responsibility of the product owner with the help of their team to add new items to the list and order them based on their priority.

At the same time, outdated, redundant or non-valuable items should be removed from the backlog to keep it clean, valuable and actionable.

We call this as Release plan meeting happens quarterly once.

Action taken from grooming meeting:

1) Estimate user stories

2) Insert new user stories

3) Re-Prioritize user stories

4) Refine user stories

5) Remove user stories

2) Sprint Planning:

A sprint planning meeting is when the team (including the Scrum Master, Scrum Product Manager, and Scrum Team) meets to determine which backlog items will be handled in the next sprint.

The sprint planning Scrum ceremony is a collaborative process that allows team members to have a say in when work happens.

3) Daily Scrum:

During this meeting, each team member should briefly provide the answers of the following three questions:

1) What has he/she accomplished since the last daily Scrum meeting?

2) What is he/she is going to accomplish until the next Scrum meeting?

3) What are the impediments that prevent him/her from accomplishing his/her tasks?

4) Sprint Review:

Sprint reviews focus on the product being developed, specifically on the potentially shippable product increment created during the sprint.

During a sprint review, the scrum team invites stakeholders to discuss what was completed during the sprint.

They adapt the product backlog as needed based on this feedback. The product owner has the option to release any of the completed functionality.

Though a demo might be part of this meeting, the primary purpose of the sprint review is the inspect and adapt capability provided by the discussion.

5) Sprint Retrospective:

The sprint retrospective is a recurring meeting held at the end of a sprint used to discuss

1) what went well during the previous sprint cycle?

2) what went wrong during the previous sprint cycle?

3) what can be improved for the next sprint?

The Agile sprint retrospective is an essential part of the Scrum framework for developing, delivering, and managing complex projects.

Comments

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics, Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - archite

Lessons learned from sprint retrospective meeting

Scenario: Team Missed Sprint Goals Challenge: A development team consistently missed its sprint goals, leading to frustration and a drop in morale. Team members felt overwhelmed by the workload and struggled to communicate effectively. Retrospective Insights: During the retrospective, team members openly discussed their challenges and frustrations. They identified bottlenecks in communication, unclear priorities, and unrealistic expectations. The team realized that individual workloads were not evenly distributed, causing burnout for some members. Lessons Learned: Effective Communication Matters: The team recognized the importance of clear communication. They committed to regular stand-up meetings, where everyone shared progress, blockers, and priorities. Balancing Workloads: The retrospective highlighted the need to distribute tasks more evenly. They decided to monitor workloads and adjust assignments accordingly. Setting Realistic Goals: The team acknowledged that setting achievable

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir

High-Tech Yuga

Search This Blog