“Decades of research have consistently shown that brainstorming groups think of far fewer ideas than the same number of people who work alone and later pool their ideas.”
Keith Sawyer
Without realising the statistics/quote above, taken from this page on NewYorker.com, I’ve always preferred to build a plan for all variants of OSS projects using WBS techniques alone before then brainstorming ideas with others.
OSS projects are too diverse for one person to have all the answers, so pooling ideas and skill-sets is essential. The same is true for project planning across businesses – a shared pool of knowledge from the vendor/integrator and the CSP/customer should produce a more broadly considered plan.
What methods do you use to plan out all the elements of your OSS?
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.
