| | | |
|---|
| Confluence Update | | |
| Updates from Last Week
|
| |
| Epics and feature map | | Sudhakar received EPICs from Tony We now have EPICs from all 4 product lines Sudhakar has begun to map features but many of the EPICs need to be re-written to match the common format that we’re looking for V2X Hub EPICs were structured like features, so there was a lot of overlap that will require adjustment ODE has all EPICs in the spreadsheet.
Tony thinks that the EPIC should be at the higher level and that user stories should line up with features because its difficult to distinguish them in Jirra. Tony walked everyone through the hierarchy in the spreadsheet that explains how our backlog matches up with the national architecture. Everyone has agreed to stop at the feature level within their own Jirra’s and then build out the EPICs separately How do we avoid confusion if multiple teams are working at the same requirement level? How is this spreadsheet going to be useful for us? It allows us to distinguish between situations where there is overlap and situations where the teams are complementary to each other It can lead to a healthy discussion about how to handle overlapping requirements on a case-by-case basis as they’re not black and white
Data distribution system and data security are the two main areas where Sudhakar believes CARMA will have overlap V2X Hub and ODE have overlap possibilities because of hosting data
|
| Milestone Checkup | | |