The page is intended to summarize all the requirements for Guilin Release.
Candidate requirement proposals were frozen on May 28, 2020 TSC 2020-05-28
These requirements have been prioritized by the TSC to realistically fit within the Guilin Release
...
on June 25th, 2020.
The Release Scope
...
was finalized during the M1 Release Planning milestone on
...
July 16th, 2020
Note: we will no longer be using a Confluence table to track requirements. More information here.
Associated integration test tasks may be found here: 2: Guilin Release Integration Testing Status
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 OR Not yet Reviewed by TSC – items not approved for various reasons
...
Use Cases
Release 6 (Guilin) proposed use cases and functional requirements
M1 Scorecard:
...
...
Architecture:
- Pink - NO GO
- Purple - GO
- Green - Considered OK not requiring architecture review
- Black - Architecture not yet performed
...
numberOfFixedRows | 1 |
---|---|
numberOfFixedColumns | 4 |
decimalMark | . (point) |
...
JIRA link (REQ)
One issue per requirement.
...
M1
Scorecard
...
T-Shirt Size
...
...
Committed (C)/ Partially Committed (P) or not (N) per impacted project
including non functional contribution
...
Company
Engagement
...
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.
Requirements
...
Milestone Scorecard (except M1)
- Green:
...
- On Track
- Yellow:
...
Architecture:
- Pink - NO GO
- Purple - GO
- Green- Considered OK not requiring architecture review
- Black - Architecture not yet performed
...
numberOfFixedRows | 1 |
---|---|
numberOfFixedColumns | 4 |
decimalMark | . (point) |
...
JIRA link (REQ)
One issue per requirement.
...
Committed (C)/Partially Committed (P) or not (N) per Impacted projects
including non functional contribution
...
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.
POC / Experimentation
...
numberOfFixedRows | 1 |
---|---|
numberOfFixedColumns | 4 |
decimalMark | . (point) |
- 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 Guilin 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 Guilin release.
Guilin Use Cases
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Guilin Requirements
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Guilin Non-Functional Requirements
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Guilin PoC
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
...