![]() ![]() We aim to respond to each feature request within 3-5 business days and aim to assign a business analyst to aid requirements drafting within 5-7 business days. Potential to collaborate to develop featureįeatures can be recommended via the following methods:.New features at a minimum it must meet the following criteria: ![]() What you need to become a Business Analyst can be found here Provide a guiding document for executing the strategy Get internal stakeholders in alignment Facilitate discussion of options and scenario planning Help. What you need to become a release manager can be found here We especially welcome Business Analysts, Designers or volunteers who can serve as release managers. Our hope is that through simply participating in the community (primarily via OpenMRS Talk), your voice will be heard and will help improve our roadmap. How do I participate in the Technical OpenMRS Road Map Planning process? Objective Lead: Burke Mamlin Co Lead: TBDĬompletion of Release Process & Application Launch Platform 2.3 features validation can be found here Platform Roadmap Planning Process: At the completion of the survey period, a prioritization meeting is held during one of the PM calls to finalize the list of features. Review how modules are moving along with OpenMRS releaseĪ survey will be circulated on talk presenting features that have been compiled for validation by the community.Any modules that should become core modules or absorbed into core?.Tickets that are likely to be punted for third time should be considered for "wontfix" or moved to OpenMRS Someday Visualize your product or project roadmap easily to create a clear vision enhance communication and improve execution. What Executives care about: High-level strategy & vision Progress.Review tickets assigned to next two releases A project roadmap is a macro overview of the deliverables, milestones, and goals for a specific project (for example, an event your organization is planning).Features for the immediate next release are determined by :.How do we determine features for the next release? Implementer's monthly call ( to be established).Continuous review of competitor applications both open and proprietary systems.Review of current functionality of current ref and platform apps to identify features that could be improved.Features requests within the issue tracker.Several sources are considered in determining which features get added to OpenMRS, including: Our Road Map planning group failed to get enough momentum, so we fell into a those-who-are-able-and-willing-do-their-best-at-creating-a-straw-man-and-let-people-react-to-and-shape-the-roadmap-as-needed approach. We also created a Roadmap Planning Mailing List for discussions focused on designing/improving/feeding our road map. By 2012, we found that a purely road map-focused process was not meeting the needs of our implementations, so we formed a Roadmap Planning Group to help coordinate and continuously review/improve our road map process. By release 1.5, we had developed the beginning of a Release Process. When OpenMRS started, we didn't have a formal roadmap and stumbled through version releases. We are constantly working on improving our roadmap planning process. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |