| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Goals | Due Date | Q1 Status | Q2 Status | Q3 Status | Q4 Status | Status Notes | |||||||||||||||||||
2 | Objective 1.1 | Increase number of OpenMRS Platform users by 5 percent in CY 16 | Dec-2016 | |||||||||||||||||||||||
3 | Objective 1.1 | Increase percentage of new feature tickets in the current CY platform release that went through the platform road map process | Dec-2016 | |||||||||||||||||||||||
4 | Objective 1.1 | Document platform road map contributions made by at least two community members in 2016 who had not previously contributed to the platform road map. | Dec-2016 | |||||||||||||||||||||||
5 | Objective 1.1 | Platform Archtectyre Review Board mets at least two times during CY 2016 | Dec-2016 | |||||||||||||||||||||||
6 | Objective 1.2 | Platform release schedule published and release done on time | Apr-2016 | progress w/ issues | progress w/ issues | |||||||||||||||||||||
7 | Objective 1.2 | Identify release manager at least eight weeks prior to the planned release | Dec-2016 | in progress | done | |||||||||||||||||||||
8 | Objective 1.3 | Document number of concurrent users supported given specific (average) server specifications. | May-2016 | blocker/contingency | planning | |||||||||||||||||||||
9 | Objective 1.3 | Document number of rows before performance issues or bottlenecks uncovered for primary resources (patients, encounters, obs, concepts). | Aug-2016 | blocker/contingency | blocker/contingency | |||||||||||||||||||||
10 | Objective 1.3 | Integration testing includes automated deployment. [next test cycle] | blocker/contingency | blocker/contingency | ||||||||||||||||||||||
11 | Objective 1.3 | Integration testing includes automated upgrade testing. [next test cycle] | blocker/contingency | blocker/contingency | ||||||||||||||||||||||
12 | Objective 1.3 | availability of automated tools for system monitoring and performance (down time, response time) | progress w/ issues | progress w/ issues | ||||||||||||||||||||||
13 | Objective 1.4 | Develop and publish technology strategy document for showcasing/highlighting new web and UI technology use | Jul-2016 | blocker/contingency | early planning | |||||||||||||||||||||
14 | Objective 1.4 | FHIR and OWA support in the Platform | Jun-2016 | done | ||||||||||||||||||||||
15 | Objective 1.4 | One or more modules are added to the platform. | Dec-2016 | in progress | done | |||||||||||||||||||||
16 | Objective 1.5 | Identify full time technical project manager | Jun-2016 | blocker/contingency | blocker/contingency | |||||||||||||||||||||
17 | Objective 1.5 | Identify BA(s) | Jun-2016 | progress w/ issues | progress w/ issues | |||||||||||||||||||||
18 | Objective 1.5 | Product owners and SMEs identified, listed, and involved in at least 80% of platform design meetings | Dec-2016 | blocker/contingency | blocker/contingency | |||||||||||||||||||||
19 | Objective 1.5 | Identify technical documenter | Dec-2016 | progress w/ issues | progress w/ issues | |||||||||||||||||||||
20 | Objective 1.5 | Number of unvetted Platform tickets is shrinking. | Dec-2016 | blocker/contingency | blocker/contingency | |||||||||||||||||||||
21 | Objective 1.5 | New Platform tickets get a response within 3 working days. [October basline] | Dec-2016 | blocker/contingency | blocker/contingency | |||||||||||||||||||||
22 | Objective 1.5 | Pull requests are reviewed within a decreasing amount of time [reviewed monthly] | Dec-2016 | progress w/ issues | progress w/ issues | |||||||||||||||||||||
23 | Objective 1.6 | Automated or semi-automated regular metrics contributing to a dashboard of community contributions in GitHub | May-2016 | in progress | in progress | |||||||||||||||||||||
24 | Objective 1.6 | Publish updated developers guide | Aug-2016 | blocker/contingency | done | |||||||||||||||||||||
25 | Objective 1.6 | External review of architecture and documentation done | Oct-2016 | blocker/contingency | blocker/contingency | |||||||||||||||||||||
26 | Objective 1.6 | A new, naive developer can create a running Hello World module within one hour | Dec-2016 | progress w/ issues | progress w/ issues | |||||||||||||||||||||
27 | Objective 1.6 | Number of people doing code review is growing [≥4 by 4/16, ≥7 by 8/16, ≥10] | Dec-2016 | blocker/contingency | blocker/contingency | |||||||||||||||||||||
28 | Objective 1.6 | ≥10 active* /dev/5s | Dec-2016 | progress w/ issues | nine | |||||||||||||||||||||
29 | Objective 1.6 | One or more lieutenants named | Oct-2016 | progress w/ issues | done | |||||||||||||||||||||
30 | Objective 2.1 | Published RefApp road map | Apr-2016 | progress w/ issues | ||||||||||||||||||||||
31 | Objective 2.1 | Published RefApp functional architecture for minimom feature set for HIV services | May-2016 | progress w/ issues | ||||||||||||||||||||||
32 | Objective 2.2 | Published concept note of Ref App vision and community accepted direction | May-2016 | progress w/ issues | ||||||||||||||||||||||
33 | Objective 2.2 | Develop and Publish Technologies strategy document for showcasing/highlighting new web and UI technology use (1.4) | May-2016 | in progress | ||||||||||||||||||||||
34 | Objective 2.2 | Architecture planning document with specifications for platform use and beyond | Jun-2016 | blocker/contingency | ||||||||||||||||||||||
35 | Objective 2.2 | Concept dictionary extension needs outlined and planned | Sep-2016 | in progress | partial for HIV care | |||||||||||||||||||||
36 | Objective 2.3 | document release process | Apr-2016 | done | ||||||||||||||||||||||
37 | Objective 2.3 | identify QA lead | Apr-2016 | blocker/contingency | ||||||||||||||||||||||
38 | Objective 2.3 | Platform release schedule published and release done on time [published release based on release schedule] | Jun-2016 | progress w/ issues | delayed | |||||||||||||||||||||
39 | Objective 2.3 | published QA process ( distinct from test process) | Jun-2016 | blocker/contingency | in process | |||||||||||||||||||||
40 | Objective 2.3 | Identify release manager at least eight weeks prior to each planned release[ each release] | in progress | done | ||||||||||||||||||||||
41 | Objective 2.3 | perform QA process for each release [each release] | in progress | |||||||||||||||||||||||
42 | Objective 2.4 | Engage at least 2 implementations in the requirements definition process | Jun-2016 | in progress | ||||||||||||||||||||||
43 | Objective 2.4 | At least 1 partnership of developers | Jun-2016 | done | ||||||||||||||||||||||
44 | Objective 2.4 | >50% of roadmap prioritized and scheduled into release schedules and purposeful backlog | Jun-2016 | blocker/contingency | ||||||||||||||||||||||
45 | Objective 2.4 | Identification of development team for each release cycle | Dec-2016 | progress w/ issues | ||||||||||||||||||||||
46 | Objective 2.4 | 2 definitive release cycles completed, including published tasks, schedule, and release | Dec-2016 | in progress | ||||||||||||||||||||||
47 | Objective 3.1 | Published definition of distribution (OpenMRS criteria) and community accepted categorizations | Apr-2016 | in progress | draft done | done | done | |||||||||||||||||||
48 | Objective 3.1 | 3 Distributions promoted in the OpenMRS community (1st in Q2, 2nd in Q3, 3rd in Q4) | Jun-2016 | not started | done | done | ||||||||||||||||||||
49 | Objective 3.1 | Identified gaps in use cases | Sep-2016 | progress w/ issues | ||||||||||||||||||||||
50 | Objective 3.2 | Team identified and managing process | Apr-2016 | done | done | |||||||||||||||||||||
51 | Objective 3.2 | Published defined objective criteria for OpenMRS endorsement of a distribution | Jun-2016 | progress w/ issues | done | |||||||||||||||||||||
52 | Objective 3.2 | 1 endorsed distribution | Sep-2016 | progress w/ issues | ||||||||||||||||||||||
53 | Objective 3.3 | Published method to identify best practices in distributions, modules, implementers, etc | Jun-2016 | progress w/ issues | ||||||||||||||||||||||
54 | Objective 3.3 | 1 review performed to identify interesting work | Dec-2016 | in progress | done | |||||||||||||||||||||
55 | Objective 3.3 | 2 features from distributions added to product road maps EOY | Dec-2016 | |||||||||||||||||||||||
56 | Objective 3.3 | 1 feature collaborated on by 2 distributions | Dec-2016 | progress w/ issues | progress w/ issues | |||||||||||||||||||||
57 | Objective 3.4 | Documented process for reaching out to distributions on a regular basis to keep them engaged, updated, and involved | Apr-2016 | in progress | ||||||||||||||||||||||
58 | Objective 3.4 | Documented process for on-boarding new distributions into the community | Apr-2016 | blocker/contingency | ||||||||||||||||||||||
59 | Objective 3.4 | 2 recorded video distribution showcases [1st by 6/16, 2nd by EOY] | Jun-2016 | progress w/ issues | ||||||||||||||||||||||
60 | Objective 3.4 | 3 Talk channels for distributions- CROSS CUTTING [1st by 6/16, 2nd by 9/16, 3rd by EOY] | Jun-2016 | done | done | |||||||||||||||||||||
61 | Objective 3.4 | 1 new distribution team engaged in community | Dec-2016 | in progress | done | |||||||||||||||||||||
62 | Objective 3.4 | 1 distribution lead actively participating in Advisory Committee discussions | Dec-2016 | progress w/ issues | progress w/ issues | |||||||||||||||||||||
63 | Objective 4.1 | publish resources currently available to train on OpenMRS | Apr-2016 | blocker/contingency | new training wiki | |||||||||||||||||||||
64 | Objective 4.1 | develop and publish curriculum for at least three different classes of users | Jun-2016 | blocker/contingency | ||||||||||||||||||||||
65 | Objective 4.2 | content manager ranking system developed, published and in use | Apr-2016 | blocker/contingency | ||||||||||||||||||||||
66 | Objective 4.2 | publish final specifications for training, testing and certification program | Apr-2016 | blocker/contingency | ||||||||||||||||||||||
67 | Objective 4.2 | increase retention of developers at dev level by 10% for CY 16 - CROSS CUTTING | Dec-2016 | progress w/ issues | ||||||||||||||||||||||
68 | Objective 4.3 | market one MOOC course with full training content | Jul-2016 | blocker/contingency | ||||||||||||||||||||||
69 | Objective 4.3 | obtain external grant funding for curriculum development | Oct-2016 | blocker/contingency | ||||||||||||||||||||||
70 | Objective 4.4 | increased diversity in GSOC with at least 10% increase in female participants ( CROSS CUTTING) | Aug-2016 | progress w/ issues | ||||||||||||||||||||||
71 | Objective 4.4 | at least five new developers participate in one training module | Dec-2016 | blocker/contingency | ||||||||||||||||||||||
72 | Objective 4.4 | at least two new implementers participate in one training module | Dec-2016 | blocker/contingency | ||||||||||||||||||||||
73 | Objective 4.4 | at least 20 number of implementers/developers will be certified in OpenMRS training | Dec-2016 | blocker/contingency | ||||||||||||||||||||||
74 | Objective 4.4 | develop a toolkit that can be used to guide and evaluate: the developement and integration of specific usability principles, process of updating a form / etc (timese / efficiency measure), impact of sftware tools (as opposed to software) being deployed, integration and experience of end use with system | Dec-2016 | blocker/contingency | ||||||||||||||||||||||
75 | Objective 5.1 | Published definition of “service provider” (OpenMRS criteria) | Apr-2016 | progress w/ issues | dondondone | |||||||||||||||||||||
76 | Objective 5.1 | Service Provider Talk channel created and introductory discussion began | Apr-2016 | progress w/ issues | ||||||||||||||||||||||
77 | Objective 5.1 | Published plan for service provider engagement | Jul-2016 | progress w/ issues | ||||||||||||||||||||||
78 | Objective 5.1 | Publicly available service provider marketplace | Dec-2016 | |||||||||||||||||||||||
79 | Objective 5.2 | Published service provider certification program with community acceptance | Oct-2016 | not started | ||||||||||||||||||||||
80 | Objective 5.2 | 1 service provider certified by OpenMRS | Dec-2016 | |||||||||||||||||||||||
81 | Objective 5.3 | Published guide for service provider engagement | Oct-2016 | not started | ||||||||||||||||||||||
82 | Objective 5.3 | Published toolset for service providers | Oct-2016 | not started | ||||||||||||||||||||||
83 | Objective 5.4 | Published process to field and forward opportunities to providers | Jul-2016 | not started | ||||||||||||||||||||||
84 | Objective 5.4 | actively marketing endorsed service providers | Dec-2016 | |||||||||||||||||||||||
85 | Objective 6.1 | Report updates to the OpenMRS BOD at least quarterly (and develop appropriate format for this reporting) [15 of the month following end of the quarter] | Mar-2016 | in progress | in progress | |||||||||||||||||||||
86 | Objective 6.1 | report updates to the community through talk [15th of the month following the end of the quarter] | Mar-2016 | in progress | in progress | |||||||||||||||||||||
87 | Objective 6.1 | Obtain at least one external funder support | Dec-2016 | blocker | ||||||||||||||||||||||
88 | Objective 6.1 | Meet 50% of timelines in operational plan | Jan-2017 | in progress | progress w/ issues | |||||||||||||||||||||
89 | Objective 6.2 | At least 6 community members are recognized through the volunteer recognition program | Dec-2016 | in progress | in progress | |||||||||||||||||||||
90 | Objective 6.2 | At least one additional woman is identified and participating at a dev 2 level | Dec-2016 | not started | progress w/ issues | |||||||||||||||||||||
91 | Objective 6.3 | establish baseline and increased involvemnt of under-represted group | Dec-2016 | in progress | progress w/ issues | |||||||||||||||||||||
92 | Objective 6.3 | one partnership agreement developed and implemented during CY 16 | Dec-2016 | in progress | progress w/ issues | |||||||||||||||||||||
93 | Objective 6.4 | Identify functional requirements for S&T tooling | Apr-2016 | in progress | done | |||||||||||||||||||||
94 | Objective 6.4 | identify external funding source for essential S&T work | Jun-2016 | in progress | progress w/ issues | |||||||||||||||||||||
95 | Objective 6.4 | develop plan and road map for S&T tools, integration into OpenMRS, content | Jun-2016 | in progress | progress w/ issues | |||||||||||||||||||||
96 | Objective 6.4 | complete core set of S&T content for platform and reference application | Dec-2016 | in progress | progress w/ issues | |||||||||||||||||||||
97 | Objective 6.5 | publish achievements on metrics plan on quarterly basis [ 15th of the month following the end of the quarter] | Mar-2016 | in progress | in progress | |||||||||||||||||||||
98 | Objective 6.5 | develop, endorse and implement metrics plan | Apr-2016 | in progress | done | |||||||||||||||||||||
99 | Objective 6.6 | publish annual report | Mar-2016 | completed | done | |||||||||||||||||||||
100 | Objective 6.6 | an increase in downloads of OpenMRS by 5% | Dec-2016 | in progress | progress w/ issues |