/
Frankfurt Release Requirements

Frankfurt Release Requirements

May 28, 2020

The page is intended to summarize all the requirements for Frankfurt Release.

These requirements have been prioritized by the TSC to realistically fit within the Frankfurt Release Timeline.

The Release Scope should be finalized during the M1 Release Planning milestone on November 7th, 2019

TSC Prioritization (Ranking)

  • RANK #0  – Special GO - quick wins, fully covered by involved companies

  • RANK #1 – TSC Must Have – Mandatory for the release

  • RANK #2 – Continuity  - Items continued from previous releases

  • RANK #3 – PTL Go – items that PTLs is OK to include since team has bandwidth

  • RANK #4 – NO GO – items not approved for various reasons

Scorecard Key

Release 6 (Frankfurt) proposed use cases and functional requirements

M1 Scorecard:

  • Green: Use Case will be fully implemented and tested

  • Yellow: Use Case will be partially implemented. It is possible to identify capabilities for this use case that can be tested (phasing approach).

  • Red: Use Case can not be partially delivered, min. requirements can not be met in order to define a testing strategy.

Other Milestones:

  • Green: On Track

  • Yellow: Use Case/Requirement not on track but could be mitigated by reducing the current scope and/or fix this issue prior M4. Risks identified and documented under Frankfurt Risks  

  • Red: Use Case/Requirement not on track and issue identified that will prevent from completing the development by M4. Use Case/Requirement should be moved to POC in alignment with the POC definition or de-scoped from the Frankfurt release.

Architecture:

  • Pink - NO  GO

  • Purple - GO

  • Green - Considered OK not requiring architecture review

  • Black - Architecture not yet performed





  • XS - <4 Man/Weeks;

  • S - ~6 Man/Weeks;

  • M - ~8 Man/Weeks;

  • L - ~12 Man/Weeks;

  • XL - > 12 Man/Weeks.

Requirements

M1 Scorecard:

  • Green: The requirement will be fully implemented and tested

  • Yellow:  The requirement will be partially implemented. It is possible to identify capabilities for this functional requirement that can be tested (phasing approach).

  • Red: The requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy



Architecture:

  • Pink - NO  GO

  • Purple - GO

  • Green- Considered OK not requiring architecture review

  • Black - Architecture not yet performed