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

• 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

T-Shirt Size

• XS - <4 Man/Weeks;

• S - ~6 Man/Weeks;

• M - ~8 Man/Weeks;

• L - ~12 Man/Weeks;

• XL - > 12 Man/Weeks.

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

Guilin Requirements

Guilin Non-Functional Requirements

Guilin PoC