Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
maxLevel2
outlinefalse

...


Action Items

Working list to be added to and used to frame some planning discussions, especially around Patty's July 11-20 visit to Bloomington.

...

  1. Tiger Teams and Meeting changes
    1. No more Monday TT or HTC calls
    2. S&A moved to Wednesday, 9am
    3. Need to address double-meetings (S&A, Editors)
    4. See new roles and responsibilities document
    5. Where are we with specs?
    6. Need to address:
      1. Tuesday, SA/BA/Core call, 8:30- next is July 18?
      2. Wednesday: Project team- 9am timeslot usurped by S&A TT standing call moved?
      3. Friday: Product Owner call, 10am-12pm
  2. Spec Progress
    1. PM wants "where are we at with specs"
      1. by TT
      2. by Dan
      3. by Kathy
    2. overdue on Roadmap
    3. roadblocks
    4. how to organize, modules
    5. going forward: SA vs BA
  3. SEARCH
    1. Simplify approach
    2. KG to create Q&A, form templates for each Tiger Team to complete for functional Search needs and desired fields
      1. links to TST, DEMO and info
      2. existing functions
      3. new features
      4. in progress
    3. To compile global requirements, then possibly work with SI team
      1. then UI edits
      2. indexing and performance issues
      3. KNS vs SOLR
      4. sample records
    4. Acceptance Criteria, Test Scripts- backward, forwards
    5. Above to enable regression testing as features added
  4. INSTANCE
    1. possible meeting July 16 or 17
    2. Get key stakeholders in a meeting, and review critical issues- make decisions (KG to summarize existing documentation, work with Patty to prep)
    3. Possible attendees: Patty, Peri, John P, Kathy, Gary C, Frances M, Michelle S, Doreen H
    4. Plan TBD with Patty Jul 9 +
  5. PURAP/KFS Prioritization
    1. Need answers on S&A additions to Roadmap
    2. where do we need more functional documentation on requirements?
    3. Need to discuss order of specs for functional and technical dependencies (what constitutes forking, how documenting, what waits for 5.0)
      1. SFC and fund rules
      2. Roles Workflows
      3. Order Types
      4. vs overdue specs
      5. Deposit accounts and other 0.8 PREQ features (vs post KFS 5 upgrade and PREQ M:1 edits)
    4. Peri & Patty- meeting to review app
    5. With Kathy and team: review KFS for what being used; what need to remove; overview future or in progress features 
  6. DESCRIBE- DOCSTORE
    1. have sit-down on Describe
    2. what features coded: docstore, bib, instance, search
    3. what coming
    4. how to prioritize Doc controls policies and: doc ownership, doc status, audit trail; work units, item availability, transaction links
    5. try to simplify fundamental issues with team and BA
    6. coordinating and communicating Editors work; BA vs SA
  7. DELIVER
    1. what issues outstanding?
    2. Key infrastructure in progress (baseline needed for all specs): Patron, Policy, Item, Item Status, Location
    3. TBD: Circ Desk (dependency with work unit, doc ownership, KIM and Locations extension)
    4. Next Patron enhancements and defining needs for 1.0
    5. GoKB competing- Dan going 50%
    6. Dan- other critical issues?

...

Additional discussions required

  • Rice vote and PM leading combined OLE discussion: ARC, TRC, KTI, KAI reps
  • Editors
    • Dual roles: framework/UI optimization vs UIs /Describe fSpecs
    • future framework
    • meetings
  • Docstore incomplete 
    • (Search, instance, facets, indexing- see above action items; summarized from KG working doc- more to be added)
  • Roadmap updates and timeline (S&A additions, reorder, dates)
  • Framework questions: 
    • Editors
    • Ingest profiles, overlay
    • Import, export
    • Patron loads
    • Financial integrations
  • Process
    • No more "Core Team", instead "OLE Project Team"- including original core team, SMEs, HTC etc- functional users
    • Roles for Spec Teams, Tiger Teams, lead SMEs, FC, TC, BAs in spec/requirements
    • Handoffs, coding, design, iterative demos
    • Testers, testing, roles for above, process
    • QA
    • Technical design: Nianli, John P, Peri
  • Documentation
    • User
      • Platform (Nora's work)
    • Technical
    • Release
    • who, what, when, how to maintain
    • wiki vs.....
  • UI/UX plan- see: OLE UI & UX

...