“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.
Have you ever had an OSS or BSS project that’s impacted by poor data quality? The problem of data integrity gets raised on almost every
“One of my favorite things about designing software is designing the defaults. The defaults define the experience for everyone out of the box. And, therefore,
Have you ever been tasked with mapping out the processes for the telco you work for? Either as a way of documenting current state, or
In the last week alone, I’ve had two potent reminders that the world of OSS is simply (pun intended) too complex. This manifests in many
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.
