The goal of this project is to address JIRA items and provide maintenance and support for LexEVS 6.0. Our process is to review the LexEVS JIRA items to determine priority and status. We assign issues to releases (e.g. 6.0.2, 6.0.3) and create estimates as to the effort to complete each issue. Additionally we use a MS project plan to map out each item, the resource assignment along with resource availability, and dependencies in order to plan out the timeline of each release. Depending on whether the release can be a patch or needs a tier deployment we may package the release as a full build and place out on the VKC or we will provide a jar file to NCI developers to place in their Development environment for testing purposes. We have deployed releases to the VKC for customer needs. We also are deploying 6.0.3 through the NCI tiers with an estimated date in Production by May 20, 2012.
On an issue basis, the developers at Mayo and NCI work back and forth to investigate, share information, and test each issue. As much as possible we strive to capture this in the JIRA issue as comments. Once an item is fixed we mark it as Resolved. NCI developers test and confirm whether the item is indeed fixed and if the issue can be closed. If so we then mark the item as closed. This process will be refined as needed throughout the project lifecycle.
Additional documentation for the project will be added throughout the lifecycle of the project. Refer also to LexEVS Guides and Training.
Monthly Status Reports
Each month a technical status report is sent to SAIC-F and CBIIT management. Please see the status reports below. If you have any questions please contact Traci St.Martin or Craig Stancl.
- Monthly Report_LexEVS_December2011.doc
- Monthly Report_LexEVS_January2012.doc
- Monthly Report_LexEVS_February2012.doc
- Monthly Report_LexEVS_March2012.doc
- Monthly Report_LexEVS_April2012.doc
Weekly Meeting Notes
NCI/Mayo Weekly Technical calls are held every Wednesday from 2-3pm EDT. The meeting notes are attached below. If you have any questions please contact Traci St.Martin at firstname.lastname@example.org