1 / 5

Coherent Web Sustaining Engineering Plan

Coherent Web Sustaining Engineering Plan. Coherent Web Sustaining Engineering Overview. The Coherent Web team will: Utilize two-week development “sprints” to plan and track implementation activities. Perform weekly reviews of newly submitted NCRs

parson
Download Presentation

Coherent Web Sustaining Engineering Plan

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Coherent Web Sustaining Engineering Plan

  2. Coherent Web Sustaining Engineering Overview • The Coherent Web team will: • Utilize two-week development “sprints” to plan and track implementation activities. • Perform weekly reviews of newly submitted NCRs • NCR priority is assigned based on submitter request and CW Team analysis. • If possible, a target version will be designated. • Categorize NCR into two categories: • “Milestone Activities” – new features that are included in Coherent Web milestones. • “Sustaining Engineering” – internally or externally submitted enhancements and fixes. • As needed, work with the Advisory Group to coordinate schedule and testing • The Coherent Web users will: • Submit enhancement requests or bug reports to the Coherent Web Team • Currently: All items submitted to the Coherent Web Team via email (esdis-cw@lists.nasa.gov) • Future: Items submitted through the Coherent Web Trouble Ticket Tool (Milestone 2) • Include a requested priority (see subsequent slide) with request • Include a need-by date (optional) with request

  3. NCR Priorities • Translating Priority into Development Start Date • Critical CMS items worked immediately • Critical & Severe Content items worked immediately • All other items will be planned in a subsequent Coherent Web sprint. • All enhancements have the same priority • Enhancements will be reviewed to determine if they will be implemented and in which version

  4. Sprint Timeline • NCR Testing & Deployment • When possible, items will be immediately applied to the operational website. • Some items, such as “Milestone Development” activities, will require a staged deployment. In these instances, changes will be applied to the Earthdata UAT environment. The CW Team, issue submitter, and/or Advisory Group, will then perform the necessary user acceptance testing prior to Operational deployment

  5. Sprint Scheduling • Proposed 2011 Sprints • Sprint “2011-1“ - 10/3 – 10/14 • Sprint “2011-2“ - 10/17 – 10/28 • Sprint “2011-3“ - 10/31 – 11/11 • Sprint “2011-4“ - 11/14 – 12/2 (Extended due to Thanksgiving) • Sprint “2011-5“ - 12/5 – 12/16 • Sprint “2011-6“ - 12/19 – 12/30 • Notifications regarding issue completion will come either from the CW Team or the CW Ticket Tracking tool. • Until a tool is developed, all communications will come from the CW Team. • Each sprint plan will be published to the informational page on the Earthdata website for historical referencing and planning purposes.

More Related