SDLC v1
From OSM Public Wiki
(Redirected from SDLC 1)
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
- Preference for agile design and development - implies iterative approach, and should be incremental.
- Iterative means a subset of a feature / epic is delivered, feedback received, then continue.
- Incremental means a feature / epic is "done done".
- Preference to follow best practices. Some Examples:
- OpenStack Model - http://docs.openstack.org/project-team-guide/release-management.html
- Ubuntu - Time Based Releases https://wiki.ubuntu.com/TimeBasedReleases
EACH SDLC
- is 6 months .. 25 weeks budget
- Feature Development: 16 weeks ... four milestones boxed to four weeks
- Each MDG to agree on iterative frequency, ideally between 1-2 week iterations
- Key Scope / Themes identified in first 2 weeks (eg. 80% of the scope for the release)
- Some idea of Demo Scenarios in first 2 weeks
- Key Architecture / Design artifacts delivered in the first 4 weeks, in markdown, as part of the git repo
- Key Acceptance Criteria and Tests (first draft) delivered in first 4 weeks (think TDD)
- Each milestone may also include sustaining / support work on the previous release
- Feature Hardening: 4 weeks
- Tackle prioritized bugs, close all high priority bugs for the release
- Feature Release: 4 weeks
- Documentation, etc
- BWTIM: 1 week
- 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.18 - Finalize Process Proposal, place on wiki / portal [owner: Carmine]
- 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:]