Talk: SDLC v1: Difference between revisions

Revision as of 11:24, 26 April 2016

Regarding the split of budget weeks for each SDLC, the current split does not take into account feature collection and prioritization by TSC. I suggest to take it into account in the life cycle. Besides, I suggest to make feature hardening and documentation stay in parallel.

My proposal below:

Call for features and prioritization: 4 weeks
- Explicit Call for features and use cases:
  - Weeks 1-3
  - Input from EUAG and the community to TSC
- Feature prioritization and identification of module requirements:
  - Week 4
  - Prioritization by TSC
  - Identification of module requirements per feature by TSC and MDL
Feature development: 16 weeks
- Design artifacts/blueprints in markdown, as part of the git repo:
  - By MDG Leads and Committers
  - Weeks 5-7
- Acceptance Criteria and Tests (first draft)
  - Weeks 5-7
- Coding:
  - From week 8 or sooner depending on blueprints availability, up to week 20.
Feature hardening and documentation: 5 weeks
- Feature hardening: Weeks 21-25
- Documentation: Weeks 21-25

@@ Line 1: / Line 1: @@
-Regarding the split of budget weeks for each SDLC, I suggest to move from 16 weeks for Feature Development to 20 weeks.
+Regarding the split of budget weeks for each SDLC, the current split does not take into account feature collection and prioritization by TSC. I suggest to take it into account in the life cycle. Besides, I suggest to make feature hardening and documentation stay in parallel.
-Regarding the workflow for the design phase, it was suggested:
+My proposal below:
-*Key Scope / Themes identified in first 2 weeks (eg. 80% of the scope for the release)
+*'''Call for features and prioritization: 4 weeks'''
-*Some idea of Demo Scenarios in first 2 weeks
+**Explicit Call for features and use cases:
-*Key Architecture / Design artifacts delivered in the first 4 weeks, in markdown, as part of the git repo
+***Weeks 1-3
-*Key Acceptance Criteria and Tests (first draft) delivered in first 4 weeks (think TDD)
+***Input from EUAG and the community to TSC
+**Feature prioritization and identification of module requirements:
-That workflow does not take into account feature collection and prioritization by TSC. I suggest to take it into account in the life cycle:
+***Week 4
-*Explicit Call for features and use cases:
+***Prioritization by TSC
-**Weeks 1-3
+***Identification of module requirements per feature by TSC and MDL
-**Input from EUAG and the community to TSC
+*'''Feature development: 16 weeks'''
-*Feature prioritization and identification of module requirements:
+**Design artifacts/blueprints in markdown, as part of the git repo:
-**Week 4
+***By MDG Leads and Committers
-**Prioritization by TSC
+***Weeks 5-7
-**Identification of module requirements per feature by TSC and MDL
+**Acceptance Criteria and Tests (first draft)
-*Design artifacts/blueprints in markdown, as part of the git repo:
+***Weeks 5-7
-**By MDG Leads and Committers
+**Coding:
-**Weeks 5-7
+***From week 8 or sooner depending on blueprints availability, up to week 20.
-*Acceptance Criteria and Tests (first draft)
+*'''Feature hardening and documentation: 5 weeks'''
-**Weeks 5-7
+**Feature hardening: Weeks 21-25
-*Coding:
+**Documentation: Weeks 21-25
-**From week 8 or sooner depending on blueprints availability, up to week 20.
-*Feature hardening
-**Weeks 21-25
-*Documentation
-**Weeks 21-25