Beyond Cycle Time: Introducing Flow Style and Mileage for Agile Teams
Flow Style and Mileage. Understand team dynamics, pinpoint inefficiencies, and elevate your Agile processes for superior performance.
Flow Style and Mileage. Understand team dynamics, pinpoint inefficiencies, and elevate your Agile processes for superior performance.
The Flaws of Using Sub-Tasks to Organize Work in Agile Software Development and Why Moving Stories is the Key to Success
A collection of real user story examples for you to copy & paste. Useful for teams new to Agile ways of working.
This is your Jira best practices guide to setting up Jira for highly productive software development teams. Packed full of tricks and tips.
In this article we share our experiences of how these 7 Agile metrics can help you to understand how your system of work is performing.
An in-depth guide to writing Agile user stories. We share 19 tips for writing better user stories collated from hundreds of Agile teams.
Nine straightforward tips to make your daily stand-ups shorter, more focused and more useful for the whole team.
Agile Resource Management is significantly easier than more traditional resourcing models. We show you exactly how resource management works in Agile.
An honest look at whether combining the Product Owner and Scrum Master roles is ever a good idea — and what usually goes wrong when teams try it.
In this checklist of activities for an Agile Coach, we explore the daily / weekly / quarterly activities of an Agile Coach.
For successful Agile delivery you require 4 critical principles; deliver the right thing, deliver it right, deliver it fast enough and deliver it safely.
How to implement Kanban for your team in 3 easy steps. Go beyond what Kanban is and understand how to implement it effectively.
A Kanban Board is a visual representation of your Kanban system. They are extremely useful for communicating status, progress and issues.
The Kanban vs Scrum debate is a completely pointless argument. Each solves a set of problems. The problems they solve are complementary.
Kanban focuses on work visualisation to identify bottlenecks, limiting work in progress to reduce multitasking, and focuses on end-to-end delivery.