Innovation Sprint Planning

How to fail in #agile interview Topic: Retrospective ---------------- How to Fail 😒 ---------------- 👸 Interviewer: "How do you typically run a sprint retrospective with your team?" 👨🦱 Candidate: "We usually ask what went well and what didn’t, then discuss how to improve." 👸 Interviewer: "That’s a basic format. But what if the team is disengaged, and you notice the same issues coming up in every retrospective?" 👨🦱 Candidate: "Well, I’d try to motivate them to speak up more." 👸 Interviewer: "Let’s get more specific. Suppose the team feels retrospectives aren’t useful and sees no real changes after their input. How would you handle this?" 👨🦱 Candidate: "I’d probably bring it up with the team during the next retrospective and see why they feel that way." 👸 Interviewer: "And if this lack of engagement affects continuous improvement, causing the same issues to repeat every sprint, what would you do?" 👨🦱 Candidate: "Maybe we’d focus on smaller changes to make things easier for them." ----------------- How to Pass 😊 ----------------- 👸 Interviewer: "How do you typically run a sprint retrospective with your team?" 👨🦱 Candidate: "I use different formats based on the team’s needs. Sometimes it’s ‘What went well, what didn’t,’ but I like to switch it up with activities like Start-Stop-Continue or using data-driven insights to stimulate discussions. My goal is to create an open, constructive environment where the team feels safe to discuss both successes and areas for growth." 👸 Interviewer: "What if the team is disengaged and the same issues keep surfacing?" 👨🦱 Candidate: "That signals we’re not addressing the root cause. I’d use techniques like the ‘5 Whys’ to drill deeper and focus on actionable items. If disengagement continues, I’d have one-on-one conversations to understand their concerns and re-energize retrospectives by varying the format or focusing on quick wins." 👸 Interviewer: "The team feels retrospectives aren't driving real change. How do you handle that?" 👨🦱 Candidate: "First, I’d check if we’re tracking action items and following up. If improvements aren’t visible, it’s often because we’re not holding ourselves accountable. I’d help the team create smaller, more tangible actions and make sure we review progress in the next sprint." 👸 Interviewer: "What if the same problems persist after implementing changes?" 👨🦱 Candidate: "If the issues persist, I’d revisit the changes and work with the team to measure their impact. Maybe the solution isn’t effective, or the problem was misunderstood. It’s also important to look at broader system-level challenges or external blockers and address those with the help of stakeholders." 💡 Key Takeaway: Effective #retrospectives require: ✍️ Engaging the team, ✍️ Addressing root causes, and ✍️ Ensuring actionable feedback drives change.

Mukta, can you handle this release all by yourself? My manager asked. I took a deep breath and said, Okay, Yes, I’ll do it. This wasn’t just about getting the release out — it was about owning the entire cycle in an Agile/Scrum setup. Here's what it really looked like to me when I started working on it: Analyzing incomplete or ambiguous user stories — had to go back to the PO and stakeholders several times to clarify acceptance criteria Estimating story points with the team, balancing technical effort with business expectations but focusing more on qa efforts. Daily or when required, syncs with developers to unblock issues, prioritize bugs, and adjust scope as needed Managing cross-functional discussions — sometimes it was the PO, other times it was UX or even the solution architect when flows weren’t aligned,things weren't proper. Coordinating bug fixes and regression testing- under tight deadlines, especially when defects came late in the sprint Chasing last-minute changes— scope creep happens even when it's not supposed to, and I had to push back while staying collaborative Juggling between QA ownership and Scrum responsibilities— attending all ceremonies, tracking progress on the board, and ensuring nothing slipped through It was hectic. Not everything went smoothly. But I learned more from this one release than from several previous sprints combined. Key takeaways: Don’t assume stories are ready just because they’re in the backlog — deep dive early strong communication with devs, PO, and designers is everything stay flexible — priorities shift, but quality shouldn’t. agree? Own the outcome — not just your tasks This experience pushed me outside my comfort zone — but that's exactly where the real growth happens, I believe. If you've led a release end-to-end in Agile/Scrum, what’s the biggest challenge you faced? Would love to learn from your experiences too. #releasetime #sprintownership #Scrumenvironment #AgileTesting

Most sprint planning meetings fail for one reason: They focus on tasks… not clarity. Here’s how high-performing Agile teams actually run Sprint Planning 👇 Agile Sprint Planning (Step-by-Step) 1. Define Sprint Goal • Product Owner explains business goal • Align on why this sprint matters 👉 Without a clear goal, sprint becomes a task list 2. Review Product Backlog • Focus on top priority items • Clarify requirements 👉 If stories are unclear, stop here and fix them 3. Capacity Planning • Check team availability • Understand realistic workload 👉 Overcommitment kills sprint success 4. Select User Stories • Pick stories based on priority + capacity 👉 Not everything important fits in one sprint 5. Break into Tasks • Divide stories into small actionable tasks 👉 Smaller tasks = better tracking + fewer surprises 6. Estimate Effort • Use story points • Align as a team 👉 Estimation is about shared understanding, not accuracy 7. Discuss Dependencies & Risks • Identify blockers early • Align on external dependencies 👉 Risks ignored in planning become issues in execution 8. Sprint Commitment • Team commits to delivery 👉 Commitment should be realistic, not optimistic 9. Sprint Starts • Development begins • Daily standups drive progress Business Analyst Role (Critical but underrated) • Clarify requirements • Bridge business and tech • Answer real-time questions • Ensure everyone has the same understanding 👉 Clarity in planning = speed in execution Golden Insight Sprint Planning is not about filling capacity. It’s about creating confidence in delivery. Business Analyst Perspective If your sprint keeps slipping… Don’t blame execution. Fix your planning. What’s the biggest challenge you face during sprint planning?

From Ceremony Manager to Value Driver: My Scrum Master Transformation 📊 I'll never forget my first retrospective as a new Scrum Master – the team was going through the motions, but we had no data to back up our feelings. That moment sparked my journey from simply facilitating ceremonies to truly driving team improvement through meaningful metrics. These KPIs transformed how I coach teams and demonstrate value to stakeholders. Here are the metrics that changed everything: 📈 Sprint Velocity & Burndown: Tracking consistency and predictability in delivery. ⏱ Cycle Time & Lead Time: Measuring flow efficiency from request to delivery. 🐛 Defect Density & Escaped Defects: Focusing on quality and technical excellence. 😊 Team Happiness & Collaboration: Because culture eats strategy for breakfast. 🎯 Sprint Goal Success Rate: Ensuring we're delivering valuable outcomes, not just outputs. These metrics don't just measure performance – they create conversations that drive continuous improvement.

🔄 𝐖𝐡𝐚𝐭 𝐇𝐚𝐩𝐩𝐞𝐧𝐬 𝐖𝐡𝐞𝐧 𝐚 𝐍𝐞𝐰 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭 𝐈𝐬 𝐈𝐧𝐭𝐫𝐨𝐝𝐮𝐜𝐞𝐝 𝐌𝐢𝐝-𝐒𝐩𝐫𝐢𝐧𝐭? A Practical Take from a Business Analyst's Perspective In an ideal Scrum world, sprint scope is locked once planning is complete. But in reality, urgent business needs or regulatory changes can pop up mid-sprint. Here’s how we handled one such scenario👇 𝐂𝐨𝐧𝐭𝐞𝐱𝐭: Midway through Sprint 6, a key stakeholder informed us of a critical compliance update for the eCommerce platform we were enhancing. The update had to go live within 10 days to avoid penalties. As the Business Analyst, my role was to evaluate the request without derailing the sprint. Here's how we handled it collaboratively: 1. 𝐖𝐢𝐭𝐡 𝐭𝐡𝐞 𝐏𝐫𝐨𝐝𝐮𝐜𝐭 𝐎𝐰𝐧𝐞𝐫 (𝐏𝐎) • I conducted a quick impact analysis to understand the effort and dependencies • Shared a cost-benefit assessment to help the PO make an informed decision • PO assessed the priority and confirmed it was indeed a must-have 2. 𝐖𝐢𝐭𝐡 𝐭𝐡𝐞 𝐒𝐜𝐫𝐮𝐦 𝐌𝐚𝐬𝐭𝐞𝐫 • We discussed options—whether to create a spike, handle it as an unplanned backlog item, or defer to the next sprint • Scrum Master helped assess if current sprint commitments could be safely adjusted without harming sprint goals • Agreed to call for a mid-sprint backlog refinement 3. 𝐖𝐢𝐭𝐡 𝐭𝐡𝐞 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 𝐓𝐞𝐚𝐦 • Walked them through the new requirement • Gathered technical insights and estimates • Ensured proper acceptance criteria and test cases were added • Collaborated with QA to plan regression impact 𝐅𝐢𝐧𝐚𝐥 𝐃𝐞𝐜𝐢𝐬𝐢𝐨𝐧: We kept current sprint goals intact but created a time-boxed spike to explore the compliance change. The feature was then added as a top-priority item in the next sprint with clear, validated requirements. 𝐊𝐞𝐲 𝐓𝐚𝐤𝐞𝐚𝐰𝐚𝐲 𝐟𝐨𝐫 𝐁𝐀𝐬: Sprint integrity is vital, but so is responsiveness to business change. A Business Analyst must: ✔️ Facilitate quick impact analysis ✔️ Align business urgency with product priorities ✔️ Enable clear communication between PO, Scrum Master, and Devs ✔️ Balance agility with discipline 🔗 Real agility is not just about speed—it’s about adaptability with purpose. Looking to explore FREE agile resources, check below folder: https://lnkd.in/dxjXYWPk BA Helpline

I'm often asked which ceremony I think is most important when running Agile. While all of the ceremonies play a key role in success of delivering outcomes, I feel that the retrospective is what makes the Agile team a team! NFL teams dedicate hours to reviewing game film after each game. This practice helps coaches and players break down their performance to identify strengths, weaknesses, and areas for improvement. Some key elements of NFL film analysis include: 1. Reviewing successful plays and strategies to reinforce positive behaviors. 2. Pinpointing errors in execution and decision-making. 3. Strategizing ways to counteract opponents and improve for the next game. Watching film allows players to visualize their actions and receive direct feedback from coaches, much like Agile retrospectives foster open discussions and learning. In Agile software development, the retrospective ceremony is a cornerstone of continuous improvement. It's a time for teams to reflect on what went well, what didn’t, and how they can improve. The main goals of a retrospective include: 1. Recognizing what went well and building on those strengths. 2. Acknowledging obstacles and areas that need improvement. 3. Collaborating on action items to enhance productivity. Teams often follow frameworks like Start-Stop-Continue or the Five Whys technique to dig deeper and create actionable takeaways. The similarities between Agile retrospectives and NFL film study demonstrate a universal truth: consistent reflection and adaptation are key to success, whether you're coding software or running plays. Here are a few ways these practices align: - Both require honest feedback, communication, and alignment on goals. - Just as developers own their contributions, players must take responsibility for their performance. - Success hinges on iterative progress—making small, consistent improvements over time. By following the below, we can have more effective Agile teams. 1. Be Honest and Open: Like NFL players facing their game tape, Agile teams should embrace transparency and feedback. 2. Focus on Actionable Change: Improvement is valuable only if followed by concrete steps. 3. Celebrate the Wins: Recognizing achievements helps maintain morale and reinforces good practices. Whether you're part of an Agile team delivering software or an NFL team chasing a championship, the retrospective process is crucial for growth and success. By embracing lessons learned and continuously striving for improvement, both Agile practitioners and athletes can achieve peak performance.

Scrum Says "Sprint Goal" - Teams Hear "Story Points" We’ve all done it - looked at a sprint plan and said, "That’s too many points. We’re over-committing." I’ve said it. You’ve probably said it. And we usually mean well. It’s a common phrase. But that doesn’t make it right. It’s just a bad habit that’s hard to break. "Over-committing" gets tossed around in Sprint Planning like it means something. It doesn't. It’s usually aimed at teams that plan more points than their average velocity or capacity supports. The implication is they’ve committed to too much work within the timebox. But here’s the problem: Scrum teams don’t commit to work. According to the Scrum Guide, teams commit to a Sprint Goal - not to points or some number or scope of backlog items. Points and velocity aren’t even part of Scrum. Neither are stories. These are common practices, but they’re optional. Ironically, the Sprint Goal - which Scrum actually requires - is often missing. "The Sprint Goal is the single objective for the Sprint… It provides guidance to the Scrum Team on why it is building the Increment." Notice: "Why," not "How much." So when we say a team "over-committed" based on velocity, we’re misusing the term. They didn’t over-commit. They took a risk. Maybe they planned ambitiously or even recklessly - but unless the Sprint Goal is unrealistic, there’s no "over." Why does this misunderstanding persist? Simple. Teams and leadership are obsessed with velocity. It’s easy to track, chart, share, and... misunderstand. Many teams use points religiously but skip Sprint Goals entirely. Sometimes there isn’t even a Product Goal - just a task queue. The Scrum essentials get forgotten. Intent gets replaced with math. Metrics become the mission. Imagine a team with a velocity of 30 points that plans 45. You might think they’re over-committing, but what if the Sprint Goal were clear, focused, and tied to customer value? If the team meets the goal without finishing all the points, that'd be a win disguised as a loss. That’s the problem with this language. It gets teams thinking about outputs, not outcomes. It pushes teams to chase velocity and game the numbers. It discourages responsible and appropriate risk-taking. If the Sprint Goal is unrealistic, that’s a valid concern. But the fix isn’t fewer points - it’s smarter goals and more honest conversations. Velocity isn’t a performance metric, and points aren’t a contract. Treat them like they are, and you’ll turn optional tools into performance targets - and lose the plot. That’s not agility. That’s performance theater. If a team is transparent, focused, and working toward a clear goal, let them stretch. Let them learn. If they miss, that’s what inspection and adaptation are for. Don’t tell them “You’re over-committing” when you really mean “You’re planning more points than I’m comfortable with.” Unless the Sprint Goal is unachievable, the issue isn’t with their over-commitment... it’s with your understanding.

I used to facilitate retros once a month. Then I realized I was the problem. I’d show up. The team would share blockers. We’d identify actions. I’d leave feeling useful. And nothing would change. Because I was teaching them to wait for me. Monthly facilitation created a rhythm: surface issues, capture actions, wait 30 days, repeat. The team got good at retros. They never got good at improving. The real constraints—the approval chains, conflicting metrics, invisible decision rights—lived in the 29 days between sessions. And I wasn’t there. More importantly, I hadn’t taught them how to handle those without me. So I changed what I was teaching: ▪️ Not just how to run a retro, but how to run it themselves. ▪️ Not just capturing actions, but spotting queues, naming dependencies, and knowing what needed system change. ▪️ Not just logging issues, but advocating upward—translating “this sprint sucked” into “here’s the constraint and here’s what we need.” The shift was from facilitator to capability builder. Now when I work with a team, the questions aren’t: Was it a good retro? They’re: ▪️ Can the team run their own improvement conversations when I’m gone? ▪️ Can they distinguish between a team fix and a system constraint? ▪️ Do they know how to escalate what they can’t solve themselves? ▪️ Are they building relationships with the people who control their constraints? Because continuous improvement doesn’t come from monthly check-ins. It comes from teams who can see their system, own their changes, and advocate for what they can’t change alone. My question for other coaches: How do you keep improvement alive in the 29 days between retros?

I still find Marketing Sprints the best way to run a marketing team. Basically you work in 2-week blocks (like an engineering sprint) and all goals are broken down into 100% doable jobs to be done. Say for example you want to try and get the team on more podcasts as a guest. Ex: Bad sprint item: “Book 10 podcasts this month”. This is a result but not 100% controllable. Good sprint item: “Create three possible pitch options and review with management”, “Send out 100 pitches”, “Create Notion doc of 50 good fit shows and write notes on each so pitches will be personalized” etc. The idea is you need to take big goals and break them down into all the constituent parts needed to execute them. It takes some vision from management and it takes some learning and adjusting as you go. But as a result you get a great 360 on the work of your team. You encourage high tempo output in a creative department. And if you do it right, every item is always accomplishable, so there isn’t this nebulous zone between tried and actually executed. From running this with teams through the years (I think I've done maybe 5-6 workshops now on this), here are some learnings… 1) Most folks pack in too many things initially and only hit ~75% of their tasks. Like completion rate in engineering sprints, it takes some calibrating. An important note, however, is that some jobs won’t get done because of contingencies. “Well I wanted to get this up, but I am still waiting on design”. It’s important contingencies are labeled and planned ahead of time. We did this in JIRA at Bonjoro and I used simple tagging. 2) I find marketing sprints really only work with good management pre- and post-sessions. It is the job of management to give the stamp of approval on the tasks that need to get done to execute towards a goal. It’s collaborative with the team, but management is saying “Yes, this makes sense for X goal”. If the team member hits 100/100 of the tasks and the end goal isn’t made, that is a management/leadership issue. Similarly, with marketing sprints, we take 2-3 days post sprint to review what got done, any results, any trends or blockers, before setting the next agenda. Folks that implement marketing sprints without the post-sessions I find hit problems. 3) Set Micro-KPIs at each leg of the race. Say you want to build a growth engine via top-of-funnel content with app partners. The first sprint is going to be assembling the list of the right fit folks. Here what disqualifies a team? What are the size, audience or fit benchmarks? Next you are going to do a sprint pitching some collaborations. What is success here? Set some KPIs around response rate, or willingness to invest or creative bandwidth to contribute. The idea is you don’t want to spend a quarter pitching and then report back, “Yeah, it seems like folks don’t want to make a podcast or newsletter together”. You want to discover the objections or blockers quickly, then pivot your approach on the next sprint.