1 / 15

JKO Mobile IPR Build 3 17 February 2014

JKO Mobile IPR Build 3 17 February 2014. Agenda. Executive Summary Approach Build 2 schedule and line items Build 3 schedule and line items Program Management. JKO Mobile Executive Summary (as of: 17 Feb 14). Task Order 180 Period of Performance ends 10 July 2014

gari
Download Presentation

JKO Mobile IPR Build 3 17 February 2014

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. JKO Mobile IPRBuild 317 February 2014

  2. Agenda • Executive Summary • Approach • Build 2 schedule and line items • Build 3 schedule and line items • Program Management

  3. JKO Mobile Executive Summary(as of: 17 Feb 14) • Task Order 180 Period of Performance ends 10 July 2014 • Build 2 work required bug fixes and enhancements: • JKO Mobile App: • 3 bugs • 3 enhancements (one deferred to Build 3) • M-Learning Suite: • 10 bugs (five deferred to Build 3) • Total: 16 items, 10 delivered. Six items were deferred to Build 3. • Build 3 work: • JKO Mobile App: • 8 bugs • 5 enhancements (one originally scheduled for Build 2) • M-Learning Suite: • 11 bugs (five originally scheduled for Build 2) • 3 enhancements • Total: 27 items - 19 bugs, 8 enhancements

  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. Review of Build 2 Work Schedule Mobile App Bugs/Enhancements M-Learning Suite Bugs/Enhancements

  6. Knowledge as a force multiplier JKO Mobile Development Timeline – Build 2 (as of 17 Feb 2014) Green= Complete, Yellow= In progress, Red= Off schedule, Black = Not started

  7. Build 2 Line Items Review: App Bugs/Enhancements

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

  9. Review of Build 3 Work Schedule Mobile App Bugs/Enhancements M-Learning Suite Bugs/Enhancements

  10. Knowledge as a force multiplier JKO Mobile Development Timeline – Build 3 (as of 17 Feb 14) Green= Complete, Yellow= In progress, Red= Off schedule, Black = Not started

  11. Build 3 Line Items: App Bugs(as of: 17 Feb 14)

  12. Build 3 Line Items: App Enhancements(as of: 17 Feb 14)

  13. Build 3 Line Items: m-Learning Suite Bugs(as of: 17 Feb 14)

  14. Build 3 Line Items: m-Learning Suite Enhancements

  15. Program Management(as of: 17 Feb 14) • Weekly updates at JSSM • A line item slide will be provided with percentages alongside each line item to monitor progress • Monthly updates at Production Brief • IPRs held monthly

More Related