| Program Roadmap | Leslie (LH) Eric (ES) Rob Maky (MA) | Program Roadmap - EQRS--3 legacy systems road maps
- Legacy system maintained in conjunction of moving to new system
- mandates
- Reports and analytics
- UI
- Measure calculator—quality score calculator
Communication UX and product planning outside of PI has been very important Who is in empowered to influence the roadmap Portfolio Management ( roadmap example) ask Jeromy
(LH) - Dealing with and showing these roadmaps
They reorged to reports and analytics, SUI, Calculator (quality scores) - Letting teams come up with their own road maps
- Dealing with issues surrounding getting off of old tech
- Bringing features up in the backlogs
Problems with dealing with balancing Agile with the longer-term needs (ES) - Forcing our way into visibility, and framing challenges within business contexts
- Measuring something at PI events?
(RF) - A lot of it boils down to communication
- using SAFE
- how to move the communication up and down teams after the event is over
- helping VIPs come up with the roadmaps and vision
- where the rubber meets the road i.e. product teams
- instead of ux being relegated as a worker bee, they're working arm in arm with the POs PMs etc to help inform and move things forward
(MA) - from HQR
- constant communication between UX and the product teams
(ES) - meeting about changes coming through the API
- mapping user interaction mental models and how they relate to the APIs
- showing the way we're considering end-user needs
(RF) - There isn't visibility for everyone
- if it's not everyone's north star, what to make and how to make it so everyone can access it
(LH) - does anyone have any good examples of high level, long term roadmaps
(MA) - PM3 people may have examples
|