Discussions
-
Is AI-coding making us faster or just more expensive? Token costs, Rework rates, and PR Cycle time
How do you know that AI-assisted coding is efficient? Because the number of releases increased and often at decent quality? Make sense, but do you know at what cost (how many dollars were spent on feature development) and why, for example, $1,000/month was spent instead of $500? How do you know that in cases involving 1.…
-
“Why is engineering always behind ETAs? Why are there so many bugs? Does anything even get better?”
These are the kinds of questions asked by business owners or sometimes even engineers themselves, but answering them reliably often takes significant effort since quantifiable retrospectives are rare, their results are disconnected from JIRA, and metrics are rarely set and tracked. Multi-team Metrics and…
-
Tracking Individual Velocity and Metrics
Jira's built-in Velocity Report does not support tracking individual or personal velocity, as doing so contradicts Agile and Scrum principles. While this approach is not recommended in traditional Agile environments, many teams still find value in tracking individual metrics for performance analysis or personal…
-
Why your Velocity and Sprint Reports are probably wrong
Have you ever stopped to analyze what work-items are actually counted toward the velocity and how the Velocity and Sprint Reports really work? If not, you likely don’t get reliable reports. Here are four common pitfalls that can seriously distort your Velocity and Sprint Reports - and how my app Multi-team Metrics &…
-
Quantify your retrospectives to unleash the full power
How do you conduct retrospectives in your team? Do you use Confluence or Miro with techniques such as ‘start, stop, continue’ or 4L? How do you quantify whether your team has become better over a time period, whether it’s a year or a quarter? You might track DORA, test pass rate, code coverage, static analysis, or similar…
