Scrum in a non-IT context: What does the Product Owner own?
Why the Sprint Goal is not an artifact in Scrum
Leveraging Scrum in a Non-IT context has challenges, as the origin of Scrum is developing software products and IT systems. In a previous post I’ve explored the definition of Increment in a Police context. In this post I would like to explore the role of the Product Owner in a non-IT context. Specifically, to answer […]
The art of re-estimating undone work in Scrum
After reading fellow PST Piyush’s blog on the Sprint Goal and why he believes it is not defined as an artifact, I shared my own insights in a comment. Re-reading my own words, they seem potentially valuable as a seperate publication. So below is that comment, as a Blog. The Sprint Goal is not an […]
Too big to fail – are you heading for disaster?
There is an art to dealing with undone work in Scrum. Many questions that pop up in Scrum Teams with undone work relate to estimation: “Should we re-estimate undone work in Scrum?” “If we do, how do we get credit for the work done previously? “If we don’t how do we account for new insights […]
Is Scrum hurting your agility?
“Too big to fail” is a phrase used for large organisations for a few main reasons: If this organisation fails, the whole economy will ‘fail’. Think of large banks that had to be rescued by the government in various countries. If any initiative in this organisation fails, we can keep it afloat by burning up […]
Scrum Masters & Agile Coaches, stop team coaching!
By Chris Lukassen & Sjoerd Kranendonk By now, most organisations are using Scrum, however, many of them feel like the agility of their organisation has degraded, and they might be right! Often, using Scrum starts out as a way to improve development efforts coordinated within an IT division or department, but that is not the […]
Simplifying CapEx & OpEx in Scrum
Why do I think team coaching is a bad idea? Dont get me wrong, I believe team coaching can have a great amount of added value. It’s just that I often find that teams receive coaching while they actually should not even be a team.
The difference between the ‘forecast’ and the ‘Sprint Backlog’ in Scrum
A really simple approach to CapEx & OpEx financial accounting with Scrum. Why is this needed? The apparent mismatch between standard financial accounting practices and agile ways of working. Specifically CapEx and OpEx accounting, which is often a very important practice in (larger) organizations. This distinction seems to be at odds with having a more […]
Agile Coaches: helping or hindering?
There is a difference between the forecast and the Sprint Backlog in Scrum. Exactly what this difference is, has eluded me for some time, and it may very well be unclear to you too. The difference may seem subtle, but can have real practical benefits as you will learn below. The way I used […]
The Purpose of Scrum is rarely realized – a path to better feedback
Note: this was not intended as an article, but the linkedin update character limit forced my hand. Below is not as polished as I would like. If this content helps you in any way shape or form, please leave a comment to share your learning! Previously posted on linkedin here. As Mike writes in his […]
The purpose of Scrum is to deliver Increments of releasable functionality . So at each Sprint Review, a “Done” Increment is required to make transparent the progress made by the team. Releasing it opens the gate to market validation to Inspect and Adapt based on market feedback (i.e. actual use). The only feedback that counts […]