“It is easier to act yourself into a new way of thinking, than it is to think yourself into a new way of acting.”
Millard Fuller.
The agile, lean documentation delivery models of today have the huge advantage of gaining momentum on OSS projects. No longer do we have the big-bang cutovers, but we start with barely viable solutions and progressively build on them. It starts out with the Minimum Viable Product (MVP) delivery model.
To Millard Fuller’s point, generating momentum by actions (ie product releases) brings about new ways of thinking and associated operational change – far faster than trying to generate momentum through talking / thinking / documenting OSS transformations.
The caveat on this model though is that somebody on the team has to have the clear understanding of where the product is going. Otherwise there can be the tendency for the agile backlog to drag the team down rabbit-holes.
Over the years, I’ve often referred to The Corkscrew Analogy or Momentum Spiral to describe a mindset of incremental improvement that’s needed to keep an
We’ve embarked on a journey of trying to plan for the future of OSS/BSS, not by predicting the future, but by seeking ways to be
As discussed in the previous article, “Future Scenario Planning: Have you given up on doing an OSS transformation? (part 1)” part of the fun of
Earlier in the week, a friend mentioned he was reading “Alchemy” by Rory Sutherland. It’s not an OSS book per se, but does provide some
Here at Passionate About OSS, we are exactly that – Passionate About OSS (Operational Support Systems). We’re also passionate about BSS, NMS, or any other names you call the tools that help to operationalise your network.
