Skip to end of metadata
Go to start of metadata

Scope & Tasks

See working 2.4 Agile Planning Board for task breakdown, tracking, and progress.

Items

  1. KRRM-144 - Data cannot be retrieved due to an unexpected error
    1. KULRICE-8800 - Data cannot be retrieved due to an unexpected error
    2. KULRICE-8428 - Data cannot be retrieved due to an unexpected error
    3. KULRICE-9441 - Data cannot be retrieved due to an unexpected error
    4. KULRICE-9439 - Data cannot be retrieved due to an unexpected error
    5. KULRICE-5159 - Data cannot be retrieved due to an unexpected error
    6. KULRICE-8049 - Data cannot be retrieved due to an unexpected error
    7. KULRICE-9440 - Data cannot be retrieved due to an unexpected error
    8. KULRICE-9479 - Data cannot be retrieved due to an unexpected error
    9. KULRICE-9483 - Data cannot be retrieved due to an unexpected error
    10. KULRICE-9195 - Data cannot be retrieved due to an unexpected error
    11. KULRICE-9361 - Data cannot be retrieved due to an unexpected error
  2. KRRM-1 - Data cannot be retrieved due to an unexpected error
    1. KULRICE-9508 - Data cannot be retrieved due to an unexpected error
    2. KULRICE-9502 - Data cannot be retrieved due to an unexpected error
    3. KULRICE-9503 - Data cannot be retrieved due to an unexpected error
    4. KULRICE-9507 - Data cannot be retrieved due to an unexpected error
    5. KULRICE-9505 - Data cannot be retrieved due to an unexpected error
    6. KULRICE-9512 - Data cannot be retrieved due to an unexpected error
    7. KULRICE-9509 - Data cannot be retrieved due to an unexpected error
    8. KULRICE-9504 - Data cannot be retrieved due to an unexpected error
    9. KULRICE-9514 - Data cannot be retrieved due to an unexpected error
    10. KULRICE-9555 - Data cannot be retrieved due to an unexpected error  (possibly out of scope)

See Rice 2.4 Design and Analysis pages for more detailed analysis of Roadmap items.

Milestones

2.4 Milestone 1 - August 12, 2013 - complete

Scope: 

  • JPA: Data Layer Restructuring, some Internal JPA Conversion (tick)

Sprints:

  • JPA Sprint 1
  • JPA Sprint 2
  • JPA Sprint 3
  • JPA Sprint 4
  • JPA Sprint 5

2.4 Milestone 2 - October 15, 2013 - complete

Scope:

  • KRAD/KNS Equivalency: 
    • Lookup Gap Analysis complete (Phases 1 & 2 - identification of items & if they're already covered in KRAD) (tick)
    • Inquiry Gap Analysis complete for Inquiry (tick)
    • Maintenance Gap Analysis complete for Maintenance (tick)
    • Lookup Equivalency achieved (jiras done) 
    • Lookup Conversion Guide draft complete
    • Lookup Phase 3 Analysis (focus group preparation & review) (tick)
  • JPA:
    • Internal conversion of KEW to JPA (tick)
    • "Defaulting" features for inquiries, lookups, etc. (needed for demo at Kuali Days!) (tick)
  • KRAD Phase 3: 
    • Performance tuning goals for response time (tick)
  • UXI
    • Application Header
    • New Left Menu
    • Form Control redesign
    • Input Groups
    • Label Align CSS Grid
    • Styling improvements: View Header, Sticky Footer, Tabs, Disclosures, Dialogs
  • QA:
    • KULRICE-9741 - Data cannot be retrieved due to an unexpected error
    • KULRICE-9742 - Data cannot be retrieved due to an unexpected error
    • KULRICE-9952 - Data cannot be retrieved due to an unexpected error
    • KULRICE-9953 - Data cannot be retrieved due to an unexpected error

Sprints:

2.4 Milestone 3 - December 17, 2013 - complete

Scope:

  • KRAD/KNS Equivalency:
    • Review of Inquiry (tick)

    • Focus Groups for Inquiry (Peter)  (tick)

    • Sample App buildout for Inquiry (tick)

    • Conversion Guide - Documentation of change in how to do something in KRAD vs. KNS for non-gaps for Inquiry, Data Dictionary, Maintenance  (tick)

    • Finish Lookup, Inquiry, Data Dictionary, Conversion Script and Guide  (tick)
    • Review of Maintenance, Data Dictionary (tick)
    • Focus Groups for Maintenance, Data Dictionary (tick)
    • Sample App buildout for Maintenance (tick)
  • JPA: 
    • eDocLite converted to JPA (tick)
    • KSB converted to JPA (tick)
    • Basic documentation on how to convert OJB to JPA  (tick)
    • Conversion scripts for OJB to JPA (tick) 
  • KRAD Phase 3: 
    • Performance: DOM cleanup & memory work 
  • Implement DevOps Database Process Changes (tick) 
  • QA:
    • Formalize strategy for JPA testing (tick) 
    • Establish performance testing plan 
    • AFT Gap Analysis: Continue with gap analysis on granular level to confirm that existing tests perform as they should (tick) 
    • Continued JIRA backlog grooming (tick)
    • Close manually-testable Resolved jiras (tick)
    • Continue to fill AFT gaps (with JPA testing strategy in mind) (tick)
  • KD Prep (tick)

Sprints:

  • 2.4.0-m3 Sprint 1 
  • 2.4.0-m3 Sprint 2 
  • 2.4.0-m3 Sprint 3
  • 2.4.0-m4 Sprint 4

2.4 Milestone 4 - February 19, 2014 - complete

Scope:

  • KRAD/KNS Equivalency:  
    • Focus Groups for Components 
    • Finish Conversion Script & Guide for 2.4 (tick)
    • Work on non-UXI gap items (tick)
  • JPA:
    • KIM, KRMS,KEN Converted to JPA (tick)
    • Conversion script documentation (tick)
    • Mostly completed Documentation 
  • QA: 
    • Establish performance testing plan (tick)
    • Set up dedicated performance test environment (tick)

Sprints:

  • 2.4.0-m4 Sprint 1 
  • 2.4.0-m4 Sprint 2  
  • 2.4.0-m4 Sprint 3
  • 2.4.0-m4 Sprint 4

2.4 Final Release - April 18, 2014

Scope:

  • Complete Regression Testing
  • Complete Unit & Integration Tests
  • Complete Performance Testing
  • Complete Documentation 

 

  • No labels