1 / 13

In Progress Review JKO Mobile Work for Task Order 180 05 November 2013

In Progress Review JKO Mobile Work for Task Order 180 05 November 2013. Agenda. Executive Summary Approach Build 2 Schedule Build 3 Schedule Line Items by Build Build 2: App Bugs/Enhancements Build 2: m-Learning Suite Bugs/Enhancements Build 3: App Bugs/Enhancements

van
Download Presentation

In Progress Review JKO Mobile Work for Task Order 180 05 November 2013

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. In Progress ReviewJKO Mobile Work for Task Order 18005 November 2013

  2. Agenda • Executive Summary • Approach • Build 2 Schedule • Build 3 Schedule • Line Items by Build • Build 2: App Bugs/Enhancements • Build 2: m-Learning Suite Bugs/Enhancements • Build 3: App Bugs/Enhancements • Build 3: m-Learning Suite Bugs/Enhancements • Program Management

  3. Executive Summary • Task Order 180 Period of Performance ends 10 July 2014 • Work requires bug fixes and enhancements: • JKO Mobile App: • 12 bugs • 7 enhancements • M-Learning Suite: • 16 bugs • 3 enhancements • Total: 38 items - 28 bugs, 10 enhancements • We will do this in two build cycles: • Build 2, September 2013 through January 2014 (5 months) • Build 3, February 2014 through June 2014 (5 months)

  4. Approach JKO Systems Engineering Process Transition Moves a system element to the next development stage or to the user. Stakeholder Requirements Definition Translates stakeholder needs into technical requirements. Validation Confirms that system elements meet stakeholder requirements. Verification Requirements Analysis Confirms that system elements meet design-to or build-to specifications. Improves understanding of requirements and their functional relationships. Realized Solution Solution Specified Design Integration Incorporates lower-level system elements into higher-level ones. Architecture Design Implementation Develops alternative design solutions, physical architectures and selects final design. Creates (making, buying, or reusing) low-level system elements.

  5. Knowledge as a force multiplier JKO Mobile Development Timeline – Build 2 (as of 12 Sept 2013) Green= Complete, Yellow= In progress, Red= Off schedule, Black = Not started

  6. Knowledge as a force multiplier JKO Mobile Development Timeline – Build 3 (as of 12 Sept 2013) Green= Complete, Yellow= In progress, Red= Off schedule, Black = Not started

  7. Build 2 Line Items: App Bugs/Enhancements

  8. Build 2 Line Items: m-Learning Suite Bugs

  9. Build 3 Line Items: App Bugs

  10. Build 3 Line Items: App Bugs (continued)

  11. Build 3 Line Items – App Enhancements

  12. Build 3 Line Items: m-Learning Suite Bugs/Enhancements

  13. Program Management • Weekly updates at JSSM • Monthly updates at Production Brief • IPRs held monthly to measure progress

More Related