It's about the mindset, not the tool!
Sure, until you realize that the tool is influencing the mindset as much as the mindset is influencing the choice of the tool.
»One alternative to using estimates for prioritizing work
is to invest in making experimenting and trying out ideas cheaper in order to sooner bring relevant data that can inform our decisions and reduce uncertainty as to what to prioritize and where to invest.
»Estimating effort in a fully loaded system
is a poor man’s try of achieving predictability while eroding trust and jeopardizing psychological safety.
»If it takes me 5 minutes to rename a method
and 1 hour to get a review and PR approval, that means the wait to processing time ratio is 60/5=12, and flow efficiency is only 7.7%.
»When it comes to the way of working, there's one small difference that can make a huge impact on your teams and organization
With Pull Requests you see just a polished and thought-through end result.
»Do you need to measure wait times and flow efficiency
if everyone that is needed is immediately available to respond (by #mobprogramming for example)?
»If developers in your team have to repeat their asks or even worse beg 🙏
for reviewing their PRs (or any other help they need), your problem is not people not prioritizing other people’s work and lack of “team player spirit”.
»If an organization compensates for ineffectiveness
by hiring more people, don’t be surprised to see the culture of ineffective parts of the organization eat away the culture of effective parts of the org, which doesn’t have a need to scale at such a rate.
»The expectation that senior developers should be able to work independently is killing the team's ability to collaborate
The more they ask for help the less they feel they are meeting that expectation.
»Measuring Accelerate metrics in XP teams is as redundant
as measuring code coverage for a team doing TDD.
»