| WOLFcon De-brief | All | - Maybe if later in conference, we would have had tougher or deeper questions
- Possible format for future session: overview roadmap, then team roadmaps - with representatives from stakeholder teams. Possible with "work we have done" then roadmap plans.
- Do we want prioritization? Do the roadmaps from the teams cover this area? Funded vs non-funded work? implemented libraries vs those not yet implemented? Should have some process, particularly for already implemented libraries and non-funded work. Gaps for libraries with little influence over service providers, self-hosted.
- How to communicate needs to dev teams/PO/SIGs, so priorities can be expressed and openly discussed.
- Define a primary way of determining requirements? For a predictable way to voice needs.
- Information/guidelines for influencing priorities, spec'ing requirements, communicating roadmap plans
Other relevant Roadmap/Prioritization - Architectural roadmap (platform/apps/etc...) - do we have a role in surfacing information about this? The work will impact most or all feature development for some time frame. Perhaps we have a role in communicating impact on feature roadmap.
|