Our Development Process
The Core Data Club process for creating the different parts of the model went far beyond brainstorming fields and tables. We imagined
- an organisation,
- a governance framework,
- how each element of the framework might work
- gathered MI definitions and examples which aligned to the proposed model components.
This collaboration began with volunteers contributing to node development. This was followed by other volunteers who reviewed the initial work.
The detailed steps were as follows:
- Define an organisation example to enable modelling
- Brainstorm an outline governance framework
- Identify the key nodes and linkages in and around P4M
- Derive the definitions for ‘Accountability Nodes’
- Develop assumptions about how each node works; their scope, agendas and high-level MI needs to support the agendas.
- For each ‘Accountability Node’ collate MI examples / designs to support the agendas.
- Generate a core data definition by consulting the document and report examples offered in Praxis superimposing a simple planning data model derived from a planning tool.
- Go through each Accountability Node and extend the core data definition to enable the MI examples collated.
- Design a simple generic way to enable organisations to localise the data model without needing to change fundamental structures.
- Generate example data and create a proof of concept cloud-based data model to test the core data definition.
- Revise the core data definition and proof of concept cloud-based data model to generate examples of the MI examples designs to demonstrate achievability.
This is the process any organisation can follow to create a BIG Model for their own needs. But of course, a group of experts creating a model form their experience does not have to deal with the realities of engaging stakeholders, fitting into current state and making it work.
The club site has a page on Adoption, but also one for Partners who can provide expertise in getting BIG from the page to your desktops.