Resignation Triggers Graphic
I saw this on LinkedIn and it resonated so much with me I had to steal it.
Lead Time to Value: The Metric That Actually Matters
Introduction In the relentless pursuit of faster delivery, many engineering organisations obsess over velocity, sprint completion rates, and deployment frequency. Yet teams often find themselves moving faster whilst delivering less value. The critical metric that bridges this gap is Lead Time to Value (LTTV) – the elapsed time from when work is requested until it
Cycle Time: A Complete Guide for Agile Teams
What is Cycle Time? Cycle Time is one of the most critical metrics in agile software development, representing the elapsed time from when work begins on a feature, user story, or task until it’s completed and delivered to the customer. Unlike Lead Time, which measures from the moment work is requested, Cycle Time focuses specifically
Kanban vs Scrum: Choosing the Right Agile Framework for Your Team
Agile methodologies have revolutionised software development and project management, offering flexible approaches to delivering value incrementally. Among the most popular frameworks are Kanban and Scrum, each with distinct philosophies and practices. Understanding their differences, strengths, and weaknesses is crucial for teams seeking to optimise their workflow and productivity. Understanding Kanban Kanban, derived from the Japanese
Performance Reviews – Forcing a Bell Curve?
Forcing a bell curve in performance reviews creates several significant problems: Artificial scarcity of high performance – A bell curve assumes that only a fixed percentage of employees can be top performers, regardless of actual performance levels. If you have a strong team where most people are genuinely performing well, you’re forced to artificially label
Why Annual Performance Reviews Are Failing Software Engineers and Scrum Teams
Annual performance reviews have become a corporate ritual that many organisations cling to, despite mounting evidence that they’re particularly ill-suited to the world of software development. For software engineers and scrum teams, these yearly assessments create more problems than they solve, undermining the very principles of agility, continuous improvement, and collaborative development that drive successful
Distributed Agile Teams Discussion
This is quite a useful discussion/presentation to watch if you’ve got remote members in your agile teams or you’ve got multiple agile teams spread across different geographies.It’s by Professional Scrum Trainer Punit Doshi. The main presentation starts at 8:07 so I’d skip to there if I were you.It discusses non-collocated teams and teams with members
The Daily Scrum
The Daily Scrum is a vital part of the agile framework. It is an opportunity for the development team to review progress and highlight issues or impediments that are preventing them from progressing effectively. Who attends the Daily Scrum? The only mandatory attendees are the development team; this is important to remember as it helps
Recent Comments