Dependencies in Software Development have been an issue since decades and lots of practices have been built to “manage” them, creating an environment that becomes more complicated with longer time-to-market times as dependencies grow (or the product/solution grows).
This is creating an illusion and no dependency management is alwys the only answer! Coordination to remove dependencies is usually a more sustainable outcome with less management.
The end of the year is nearby, time for some New Year’s resolutions! As I experienced a lot of stress within the role of Scrum Product Owner, and as I know you’re busy, I’m going to help you get started…
Here are 20 New Year’s resolutions to get you started:
Wether you do a lessons learned, retrospective or kaizen event, the actions from there should be executed as soon as possible by the team. But sometimes problems that arise from these events are beyond the team's circle of influence.
This blog is different from many others as the author is not really the author at all. We do not see value in telling a customer story by ourselves and as such we let them do it for us, let them explain why LeSS, what challenges and what succesthey see being about 1 year into the adoption.
This leads to a lot of misunderstandings in organisations that are considering one of the Agile flavors as a new way of working, especially when they are used to document a lot. Quite often we need to start explaining that Agile does not mean "no documentation" but that we will handle it differently. And that's exactly what this article is all about: