Shifting to operational and maintenance focus - prioritization
Various risks have come up:
Testing with End users causes weird scheduling delays with development cycles
Unity/MDPS Solutions Engineer role: As use case dev ramps up, and interactions with ASIPS, EMIT, HECC, more interactions and feedback will increase to the dev teams. There is a balance in supporting these teams while doing dev
These boil down to the shift from new feature development to support and prioritization of user needs. the structure of our team focuses on 3 month planning to enable strategic and tactical changes on a shorter timeline, but this may not be enough. We need to determine a mechanism for 'critical' changes- much like we have to do with MCP security issues.
Actions
[ ] Determine how to communicate requested/desired updates/changes and their priority- in what venues (e.g. github, service desk, weekly meetings) and their cadence?
Shifting to operational and maintenance focus - prioritization
Various risks have come up:
These boil down to the shift from new feature development to support and prioritization of user needs. the structure of our team focuses on 3 month planning to enable strategic and tactical changes on a shorter timeline, but this may not be enough. We need to determine a mechanism for 'critical' changes- much like we have to do with MCP security issues.
Actions
Associated Objectives