Comments
-
Thanks for sharing, Jimi, Very interesting points!
-
The 'intentional customization' vs. 'unmanaged sprawl' line is the one that stuck with me too, and I think Zoltan's extension of it is where a lot of the real cost hides. Platform sprawl at least looks like debt: you can see the 400 workflows. The team-practice version is invisible, which is what makes it more expensive.…
-
"Kills recency bias". That's one of our goals, moving away from the "who yelled the loudest yesterday" dynamic and toward actual historical evidence. To answer your question directly: right now, our tooling is primarily focused on planning, estimation, and process data. We don't natively ingest raw CI/CD telemetry (like…
-
This maps closely to how I've come to think about it: a retro isn't just a session, it's a signal; and an estimate is really calibration data. But most teams never get to actually query any of it. Your flow-to-theme correlation is the sharpest example of the payoff ("unclear requirements" -> cycle time +40%, escaped…
-
Really enjoyed this, Mary. For transparency, I also work on agile-ceremony tooling in the Marketplace, so I'll keep this app-agnostic. At Catapult Labs, we've been experimenting with Agents too. We're focusing on providing value around Agile ceremonies. Some pre, and post session work that needs to be done, and that is…
-
"Proximity problem" is why so much institutional knowledge just disappears into thin air. You are highlighting this through the lens of architectural and product decisions, but I want to add that we see the exact same breakdown happen with team process and sprint planning. As a Marketplace Partner (co-founder at Catapult…
-
A 60-minute standup is not a stand-up anymore, that's a status report already. It is incredibly frustrating, especially when there is no dedicated Scrum Master to rein in the scope. When a team hits 10 people, the math of synchronous standups completely breaks. If everyone takes just 5 minutes to explain their tickets, the…
-
@Syed Majid Hassan -Exalate- , this case study highlights a silent sprint-killers: invisible work. When customer escalations are trapped in Salesforce, the engineering team ends up planning their sprint based on fiction. They allocate 100% of their capacity to feature work, and then get completely derailed by mid-sprint…
-
I think is the status report what should be eliminated so the actual standup can survive. 12.5 weeks lost to bad meetings is a tragedy. But, the problem isn't Agile, and it isn't the core concept of the standup. The problem is how teams allow a 15-minute blocker-check to mutate into a 45-minute status report, live demo,…
-
Great use case for Rovo, for a massive pain point: sprint health data is way too fragmented in native Jira. To answer your question at the end; the question we see taking Scrum Masters the most time to answer is the qualitative "Why?" Your Sprint Reviewer Pro (and the Rovo agent) solves the "What happened?" by pulling all…
-
Hi Zoltan, this is a fantastic discussion. The "Retrospective Black Hole": where great ideas go to die a few sprints later. This is a universal pain point, trust me. I completely agree with the points Davit and Nigel brought up. Davit’s concept of "invisible work" is also right; If an action item doesn't have capacity…
-
"Agile in name only." You both hit on the exact same underlying issue: when the ceremony is disconnected from the actual work system, everything degrades into shadow IT (Slack DMs, hidden trade-offs, and ignored action items). To your point about "Retros that produce action items nobody follows through on", the reason…
-
Martin’s point about keeping a "human-in-the-loop" culture rings a bell, because AI is fundamentally shifting where the bottlenecks in software development live. To answer your question about Ceremonies: As a Marketplace Partner (co-founder of Catapult Labs), we spend our days building Agile ceremony tools natively inside…
-
"Operating discipline precedes tool deployment", that is the absolute truth when it comes to scaling. "Establishing data hygiene rules," is one of the biggest gaps we see at the enterprise level. If a Release Train is using Jira Align to track features, but the individual squads are still leaving their Retrospective action…
-
"AI without context is noise." You can buy tokens all day, but if the LLM doesn't understand the organizational reality of why things are happening, the output is just generic. As a Marketplace Partner (co-founder at Catapult Labs), the announcement I am most excited about is the Teamwork Graph MCP tools. We build apps…
-
"Sprint planning stops being strategic and starts being triage." 🎯 This is the exact reality for so many MSPs. At Catapult Labs, we see teams abandon their Agile ceremonies entirely because their shared Jira boards are too polluted with cross-client noise. Separating the instances and using a smart integration layer to…
-
Hey everyone! Excited to officially being back into the Agile Community Group. I’m Luis, co-founder of Catapult Labs. We are a Platinum Atlassian Marketplace Partner, and we spend our days building Agile collaboration apps natively inside Jira and Confluence (like Agile Retrospectives and Scrum Poker). My Agile Philosophy:…
-
HI, Sinead! Just making sure you don't miss my response: I'm Luis, with the Catapult Labs team. Agile Retros for Jira, just as any other marketplace add-on, is billed based on the number of users active in a Jira instance. The fact is, that is how all of Atlassian-billed apps are billed this way. We know this may not be…
-
I've used the Scaled Agile Framework (SAFe): SAFe is Designed to extend Agile practices beyond individual teams, and managing multiple interdependent projects. It uses elements of Scrum, Kanban, and Lean principles to align strategy and execution across multiple teams. I've found this is really helpful for large…
-
@Kelsey Van Scoy I noticed other partner features are published by you, by I didn't see any indication of where to send it, so I went ahead and published it.
-
This looks like a great addition to Confluence! 🙌 I t’s so true that effective collaboration isn’t just about sharing information—it’s about engaging with content in a way that drives action and continuous improvement. For distributed Agile teams, seamless collaboration between Jira and Confluence can make or break…
-
This is such an important conversation, especially with so many Agile teams working remotely! 🌍 Async estimations and clear communication are game-changers for keeping work moving without adding meeting fatigue. One thing we at Catapult Labs have seen in the last 7 years working with distributed teams is that clarity…
-
It’s always exciting to see how teams can optimize their Agile workflows by leveraging clear, actionable sprint reports. One thing that really stands out is how visibility into time spent helps teams not just track progress but also identify patterns—whether it’s recurring bottlenecks, scope creep, or tasks taking longer…
-
One thing that really resonates is the emphasis on turning data into action rather than just tracking metrics for the sake of it. In our experience at Catapult Labs, one of the most impactful ways to close the loop between insight and improvement is by integrating data-driven discussions into Agile ceremonies, especially…
-
Great insights! 📊 Understanding cycle time and other Kanban analytics is crucial for teams looking to optimize their workflow and identify bottlenecks before they become major blockers. One key takeaway we’ve seen is that raw data alone isn’t enough—teams get the most value when these insights feed directly into continuous…
-
It’s all too common for teams to get stuck in reporting loops—tweaking dashboards, fixing data mismatches, or trying to make sense of overwhelming amounts of information. One of the biggest gaps I’ve seen isn’t just in how reports are built, but how teams act on them. Reports that only show what happened but don’t help…
-
Metrics should be a tool for growth, not a mechanism for fear or control. We’ve seen firsthand how the wrong approach to metrics can lead to unintended consequences—teams optimizing for velocity alone, focusing on output over impact, or even feeling pressured to "game the system" to meet arbitrary targets. One of the most…
-
I usually play and old scholl rock & roll song and let the algorithm take the wheel. Usually with some great finds on the way. Some Howlin' Wolf, John Lee Hooker, or Chuck Berry will get the ball rolling really good. Great topic! Taking notes :)
-
👋 Hi everyone! Excited to be part of this group! I’m with Catapult Labs, an Atlassian Marketplace Partner, where we’ve spent nearly seven years building tools to enhance Agile ceremonies—from retrospectives to estimation and stand-ups. Working closely with Agile teams across different industries has given us a front-row…
-
Great guide! A well-structured Jira dashboard is key to keeping teams aligned and making data-driven decisions. One thing we've found especially impactful is integrating retrospective insights directly into dashboards. For teams running Agile Retrospectives in Jira, surfacing key metrics—such as action item completion…