Base Company was the third Mobile Operator in Belgium and stayed within the top 3 market leaders, even today now the organisation has gone through a new change. Their IT was part of the technology department that was also responsible for the mobile network, from design to operations. Within the IT organization were a couple of hundred people, a mix of people on the payroll together with externals from several (strategic) partners. Their main integration partner was an Indian company, covered by a managed service contract, working in a strong phase-gate scenario.
If you are not moving at the speed of the marketplace you're already dead - you just haven't stopped breathing yet. - Jack Welch
The organizational structure in which most of us operate today can be quite an obstacle to respond adequately to a fast-changing business environment. In fact, traditional organizational structures are not designed to deal with a Volatile, Uncertain, Complex and Ambiguous (VUCA) world. This leads to employees feeling disengaged from their companies, and to companies being outmanoeuvred by their competition.
Top-down, control based hierarchies discourage individual initiative, lead to slower reaction times, and divert energy to “managing up” or what is called politics. These politics will optimize your organization to CYA (Cover Your Ass), loss of productivity, and an aversion of risk, resulting in a standstill culture.
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.
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:
We get a lot of questions on measuring “productivity” within organisations in relation to Agile or Lean adoptions and today was no different than any other, the big productivity questions came in our direction again. This was the trigger for me to write down some things related to productivity measurements which I find valuable to share. First of all we need to distinguish between “Leading” and “Lagging” indicators on measurements about productivity.