1. Release 2: Work Items best practices Group Name: TP15 Source: Scarrone Enrico, Telecom Italia Meeting Date: 2015-01-19

2. Recall: Why oneM2M has WI? Assure that there is a sufficient member support for a specific technical activity (that’s why there is a minimum number of supporting companies) Assure that the proposed work is relevant for oneM2M and there is consensus to develop it in oneM2M (that’s why consensus is required to approve it ) © 2014 oneM2M Partners 2

3. Recall: Why oneM2M has WI? Assure that a clear-as-possible common understanding of the work to be developed and the related timeframe (that’s why description and objectives are very important) Trace the progress of oneM2M technical work. There is a strict relation between the Work Items and the Work Program. © 2014 oneM2M Partners 3

4. WI: What are about The Working Procedures and the Method of Work give a relevant flexibility (not exhaustive list): a WI can be a new specification, a set of new specifications A CR to a specification, a set of CR to one or more specifications. The specifications targeted by a single WI may pertain to one or more WG. «Rules are for the wise people to be used not for the fools to be abused» © 2014 oneM2M Partners 4

5. WI: What are about The Working Procedures and the Method of Work give a relevant flexibility (not exhaustive list): a WI can be a new specification, a set of new specifications A CR to a specification, a set of CR to one or more specifications. The specifications targeted by a single WI may pertain to one or more WG. «Rules are for the wise people to be used not for the fools to be abused» © 2014 oneM2M Partners 5

6. CR process The CR process foresees that only changes needs to be approved to specification after first approval of a specification. So a new version of a specification implementing approved CRs is automatically approved. CR are associated to WI to keep a link among the changes related to a specific feature, for tracing and rollback purposes. © 2014 oneM2M Partners 6

7. Best practices: specification life cycle Existing specifications and new releases need: Maintenance of past releases versions (correction) Correction and refinement of the technical document in the new release Addition of new technical content in the new release The Work Program traces the new technical content development © 2014 oneM2M Partners 7

8. So for Release 2……. A set of WI are required to maintain each specification: 1 for Maintenance of Release 1 version 1 for correction and minor technical enhancements in Release 2 version. Minor means something that have a very small technical impact and can be done typically in one CR focalized on a specific existing technical feature © 2014 oneM2M Partners 8

9. Plus….a set of new R2 Work Items A new work item for each new feature/functionality and for each major enhancement of a new feature/functionality These WI are focalized on the feature, so are typically targeting CRs to a specification or to the set of specifications impacted by the feature (potentially engaging typically more WGs) The work program trace the development of the feature, not the development of the specification © 2014 oneM2M Partners 9