Wie können Sie sicherstellen, dass Ihr Team mit Scrum-Zeremonien einen Mehrwert liefert?

Vision plays a major role and it is the first step to start working on any product. Always have a vision, have it aligned with the customers' needs, business goals and the market opportunities. Your vision should also be accessible to everyone involved in the project.

Consistency is always the key. To ensure your team consistently delivers value with Scrum ceremonies, it's crucial to focus on collaboration, communication, and continuous improvement. For instance, during Sprint Planning, encourage the team to define and understand the value behind each user story. This sets the foundation for meaningful contributions.

First thing first, Scrum is not a ceremony. The objective of scrum is tagged with removing the blocker and accelerating the speed to achieve the goal faster by establishing a clear vision and path for the team. Second, Scrum is not one person's job and ownership is always on the entire team else the team will always end up with confusion and underdelivery. It is vital for the entire team to be involved in each step of the scrum and show ownership. Third, the team bandwidth should be rightly aligned to make the agreement achievable considering resource constraints. Avoiding over-commitment is a must. Fourth, retrospect shouldn't end up like a blaming session. Instead, the team should focus on answering 3W - Why, What, How to improve

- Define a rough vision for the product before going into scrum meetings. - This vision aligns them with client needs and business objectives, and acts as a guide for the team. - For example, by clearly articulating our product vision at the beginning in one of our projects, our team remained focused and motivated during Scrum meetings, consistently delivering value

To ensure our team delivers value with Scrum ceremonies, we prioritize efficiency and collaboration. During sprint planning, we set clear objectives and prioritize tasks based on their impact. Daily stand-ups keep everyone aligned and focused on our goals, while also highlighting any roadblocks. Sprint reviews allow us to showcase our progress and gather feedback from stakeholders, ensuring we're on track to deliver value. Retrospectives provide a space for reflection and improvement, helping us refine our processes for future sprints. By actively engaging in each ceremony and leveraging them to drive collaboration and alignment, we ensure our team consistently delivers value to our customers.

My opinion on refining the backlog is to occasionally allow team members to choose which items they want to work on. This can boost motivation and innovation, as people tend to be more committed and creative when they work on tasks they're passionate about. While it challenges traditional prioritization, it can lead to unexpected value and team empowerment.

As part of the refinement for the backlog, I always use the RICE framework. The framework has served me well in the past and continues to. The RICE framework is a method used to prioritize Features, stories, and projects. It focuses on four key factors: Reach, Impact, Confidence, and Effort. Reach assesses the number of people impacted within a specific timeframe. Impact measures the effect of the project quantitatively or qualitatively. Confidence reflects the certainty in estimates. Effort quantifies the resources needed to complete the initiative. By combining these factors, product managers can assign a score to each idea, aiding in decision-making and roadmap prioritization.

What should be the frequency of backlog refinement? Do you often ask this question to yourself? In my experience, it's always good to spend 15-30 mins per day to go through the backlog. It might be about: 1. Writing new user stories. 2. Setting priorities for features/user stories. 3. Shuffling items in backlog as per the Priority and Impact. 4. Answering questions from Backlog refinement sessions. The more you focus through your backlog, The more you address open questions. The more you uncover unknowns. The more you are confident about your backlog. When it comes to refining the backlog with the team. I believe 2 a week is a good frequency. I prefer two 45 mins sessions every week. It works better than 1 long session.

Planning the sprint is an Important task it should be rigid enough so as to no further changes can affect the plan but it should also be flexible enough to accommodate any last minute critical feature requests. Few steps the teams can follow are: Plan from the backlog Take inputs from the senior/exec teams Take inputs from the customer support/sales teams Inputs from the data/RCA New/unique features/product ideas Mix and matching and combining these according to the needs to make a sprint plan leads to efficient allocation of resources

Daily Standups should foster open communication, emphasizing blockers and progress. By addressing impediments promptly, the team stays on track. Sprint Review meetings should involve stakeholders actively, ensuring their expectations align with the delivered value. This iterative feedback loop is vital for refining product increments.

Ensure these 5 things in Sprint Planning for success: 1. Consider resource capacity(Ensure holidays and leaves are taken care of) 2. All stories taken in sprint are refined and the team understands the requirements clearly. 3. Team should create small tasks for each stories for better tracking and estimation. 4. Identify Dev and QA ETAs. 5. Ensure any external dependencies related items are well planned to be unblocked by the dependencies. Often teams end up committing more than possible leading to spillovers. Above points can help teams with better sprint planning.

It's essential to call out successes or contributions instrumental in delivering the product update. This keeps the team morale high and increases the sense of camaraderie. Also, collect feedback in terms of what we PM or any other stakeholder can do to make the sprint better.

Always end your Retrospective on a high note. It sets the tone for the next Sprint and gets the team excited to collaborate again. Empower through responsibility and encourage the growth mindset.

Retrospectives are opportunities for the team to reflect on process improvements. Implementing action items from retrospectives ensures a commitment to continuous enhancement. By instilling a culture of value-driven collaboration across all Scrum ceremonies, you create a framework that not only meets deadlines but consistently delivers impactful outcomes.

Types of Communication in Agile Sprints: - Daily Stand-up Meetings: These short meetings are held daily to discuss progress, challenges, and plans for the day. Each team member shares their updates, fostering collaboration and identifying any roadblocks. Sprint Review Meetings: At the end of each sprint, a review meeting is conducted to showcase completed work to stakeholders. This promotes feedback and ensures that the product meets expectations. Examples of Communication Used: - Email Updates: Sending regular email updates to team members and stakeholders about progress, blockers, and upcoming tasks. - Slack Messages: Using Slack to communicate in real-time with team members, share quick updates, or seeking clarification on tasks.

One - Stop calling 'ceremonies', are you running a cult? Two - You can't ensure anything except your own actions. You do your best for the team to deliver value by reducing uncertainty. Three - The goal isn't scrum. The team drives Scrum. You as a Product Manager, you ensure the stakeholders are still aligned with what the teams build and know when to pivot.

⏹ Stop using the term "ceremonies". That's outdated and harmful. ⏹ You can have the best facilitation and still be failing. ⏹ Scrum may help solve complex problems, but please don't consider Scrum events a magic formula that can alone cure all your product and value delivery problems. ⏹ The primary measure of success is delivering value to customers. → You achieve that by: - Building a team that has the right level of self-management and ability to improve their cross-functional skills. - Consistently achieving goals that contribute towards product vision. - Adopting an empirical mindset and way of working. - Providing the right level of transparency, inspection, and adaptation.

I agree with Eddi regarding “ceremonies” Every Scrum event circles around only two aspects - 1. How do I maximise the value delivery 2. How do I maximise my team’s performance towards maximising the value delivery So ensure you keep these two in mind!

In Agile methodology, iteration is fundamental for breaking down projects into manageable tasks and continuously improving them. Measuring the success of released features is equally vital in Agile. In a recent project our team applied iterative practices to develop a new software feature. We meticulously broke down the project into smaller tasks and iterated through them to achieve our desired outcomes. Throughout this process, we actively sought feedback from users to gauge the product's performance and alignment with their needs. By analyzing data metrics alongside user input, we identified areas for improvement and promptly implemented changes to enhance the feature's functionality.