SDLC v1

INTRODUCTION

• We should have a well defined SDLC
• The content below is an early draft
• Anything shockingly bad? email us @ osm_tech@list.etsi.org

PROCESS PROPOSAL

1. Preference for agile design and development - implies iterative approach, and should be incremental.
   1. Iterative means a subset of a feature / epic is delivered, feedback received, then continue.
   2. Incremental means a feature / epic is "done done".
2. Preference to follow best practices. Some Examples:
   1. OpenStack Model - http://docs.openstack.org/project-team-guide/release-management.html
   2. Ubuntu - Time Based Releases https://wiki.ubuntu.com/TimeBasedReleases

EACH SDLC

1. is 6 months .. 25 weeks budget
2. Feature Development: 16 weeks ... four milestones boxed to four weeks
   1. Each MDG to agree on iterative frequency, ideally between 1-2 week iterations
   2. Key Scope / Themes identified in first 2 weeks (eg. 80% of the scope for the release)
   3. Some idea of Demo Scenarios in first 2 weeks
   4. Key Architecture / Design artifacts delivered in the first 4 weeks, in markdown, as part of the git repo
   5. Key Acceptance Criteria and Tests (first draft) delivered in first 4 weeks (think TDD)
   6. Each milestone may also include sustaining / support work on the previous release
3. Feature Hardening: 4 weeks
   1. Tackle prioritized bugs, close all high priority bugs for the release
4. Feature Release: 4 weeks
   1. Documentation, etc
5. BWTIM: 1 week
   1. The weeks should add up to the budget ;-)

TIME BOXED RELEASE DATES

• R0 ends on 2016.05.06
• R1 ... from 2016.05.09 ... 2016.11.04
• R2 ... from 2016.11.14 ... 2017.04.28

IMMEDIATE ACTION ITEMS

• 2016.04.15? - Finalize Process Proposal, place on wiki / portal [owner: ]
• 2016.04.22? - MDG Leads Meeting / Process Review [owner: ]
• 2016.04.22? - Clarify Artifact Locations - Backlog, Release Scope, Release Status, Release Results [owner: ]
• 2016.04.25? - Start CI/CD Pipeline Design [owner: ]
• 2016.05.02? - Start CI/CD Pipeline Buildout [owner: ]
• ?? - Recreated R0 on a new environment [owner: ETSI .. ]
• ?? - Identify a Task Force to help own the setup of CI/CD .. ¿and police it longterm? [owner:]