...
- identifying features for possible inclusion in VIVO. This is done through every VIVO community mechanism – listservs, events such as Implementation Fest and Conference, personal discussions, working group meetings, task forces, steering and leadership group meetings.
- Refinement of the feature definitions – what is meant by each? Are two features rather similar and should be combined? I a single feature actually more than one and the feature description should be split apart?
- Discussion of features and the value and enthusiasm for each. How does the feature improve our ability to generate value for scholarship and scholarly discovery? How enthusiastic is the community for donating their time and effort to work on a feature?
- The community expresses its preferences for the features and in particular indicates willingness to contribute effort to development
- A draft roadmap is developed by a task force using using community feedback, knowledge of the software and techniques needed to efficiently develop features, and strategic concepts
- Aligning the roadmap with community interests and the strategic plan to insure that high value features of community interest are on the roadmap
- Creation of sprints to develop features on the roadmap. Release planning and sprints organize development effort into chunks that can be delivered as releases.
- The roadmap process is always open. We always are listening for ideas related to improving VIVO. Refinement of the roadmap occurs naturally – as features are completed, as effort is contributed, as needs and interests and strategic opportunity changes. Periodic revision of the roadmap is expected.
Roadmap Process
Roadmap Features
...