Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Once the review process was completed we envision bringing the reports we might generate to others in the community, particularly the TCC, as means to get their input and help in identifying technical strategies and the time/effort that these would require.  This will help us prioritize the plans while also giving us a sense of the resources needed to not just implement the enhancements but also maintain them over time.  This information could then be used to help secure the resource needed for the work.


Phases of Capability Review Process


  • Start Up Phase - This would be an initial period when we would meet with those who are leading the development effort on a tool or capability to have an initial discussion around their thoughts and areas of interest in terms of getting feedback from the T&L group.  We would also use it as a time to communicate out broadly regarding our plans to engage in a capability review as means to get others involved.
  • Phase One: Preliminary Capability Enhancement Ideas - This would be an early stage brainstorming activity that would span a relatively short period (2-3 weeks maybe) that would try and generate as many ideas as possible for both enhancements to existing capabilities, entirely new capabilities and usability (UI/UX) improvements.  We would encourage participation from as many people as possible with the idea that the T&L Group might discuss these as means to develop initial thoughts around prioritization.
  • Phase One: Community Check-In -  This would be a formal period of time when we could pause in adding to our initial list and focus on getting preliminary feedback from those leading development, from the TCC/PMC and institutional decision makers.  In particular, we would be looking for technical folks to surface concerns, issues or challenges that might help us decide which ideas to focus in on.
  • Phase Two: Usability Testing and Capability Reviews - This would be a period when we would engage in the types of work outlined above which might include lightweight usability testing and identify capability enhancements.  We would work to remain in direct contact with tool developers on questions that surface but would also make sure the process was open to all and transparent.
  • Phase Two: Community Check-In - This would be a similar check-in as during phase one but would be more specifically focused on assessing technical issues and scoping the time, effort and resources needed to implement the proposed enhancements.
  • Phase Three: Draft Capability Review Report - We would develop and release a report that would include recommendations for future development work and the resources needed to do this work.
  • Phase Three: Community Check-In - This would be a final check-in period during which people could question and comment on the draft report
  • Phase Three: Release Final Report and Seek Resources - We would release the report broadly and work both at our local institutions but also within the community to engage institutional decision makers as means to secure the resources needed to implement the enhancements.