Here, I'll explore the intriguing concept of priority inversion in Agile software development and strategies for navigating it effectively.
While the term sprint planning is widely recognized, it is also a concept that is frequently misunderstood.
Here is how joining a rowing team has made me a better Delivery Lead. Disclaimer: I am not an expert in either domain. Yet.
By enabling parallel sprints in Jira and following these tips, teams can manage their projects within a single Jira software project.
A spiking phase lets everybody working on the project gain a greater understanding of the system as a whole.
Sizing up a team has many challenges, including managing the flow of standups. Here's a collection of ideas to keep things moving.
Whether starting a new software project or simply transitioning to agile project management, your team will need to pick a length for upcoming sprints.
I propose that we stop measuring throughput or velocity. Instead, companies should empower software teams to make value estimates on individual work items.
In this third part of my Rethinking Agile series, instead of adding practices, I recommend something for you to remove. That is, stop estimating effort!
In Part 1 of this series, I suggested adding a “deload” period into your agile practices. In Part 2, another suggestion in the same vein: the Stand Down.
After sustained intense exercise, a deload gives your mind and nerves a chance to reset. I think it's time to bring this concept into software development.
Spikes are great for exploring and de-risking problems. I'll outline three steps I take to make sure that spikes have lasting value for a software project.