Talk:SDLC v1

Regarding the split of budget weeks for each SDLC, I suggest to move from 16 weeks for Feature Development to 20 weeks.

Regarding the workflow for the design phase, it was suggested:

• 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)

That workflow does not take into account feature collection and prioritization by TSC. I suggest to take it into account in the life cycle:

• 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
• 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
  • Weeks 21-25
• Documentation
  • Weeks 21-25