(Feedback from ONS, 2 October, 2017)
Describe issue or need | Analyse Phase is too output-oriented. Maybe call it ‘primary analysis’ or ‘estimation’…. 1) This makes it not generic enough (it ignores analysis that could relate to insight on earlier phases) 2) Assumes "data files" have been finalised 3) Forces GSBPM to be linear (i.e., Analyse can only happen after Process) |
Phases impacted | 6 - Analyse |
Suggested Improvement | Suggest the scope of Analyse Phase should be increased to include initial exploration of a new or existing data source (for example, activities related to "playing with" or using a "sandpit" in order to understand a big data source) as well as ongoing analysis of data during processing or derivation of analytical insights during operations. In practice, this creates two Analyse streams:
This change would make it easier to mix processing and analysis activities as well: sequences such as (integrate data, analyse integrated data, process, analyse results, process, analyse and explain, publish) become feasible. Analysis in this case also becomes an activity that can support the Design phase by allowing prototyping and generation of designs. |
1 Comment
InKyung Choi
Revision Group Meeting 24 April, 2018