Page Comparison

...

Working list to be added to and used to frame some planning discussions, especially around Patty's July 11-20 visit to Bloomington. Action items identified, KG & PM This Action Items section is part notes/part possible action items per PM/KG call 6/29/12.

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
   7. PM meeting 6/27: mentioned 1-2 day meeting while in Bton on planning?
2. Spec Progress
   1. OLE Scope & Schedule folder
   2. OLE 0.8 Jira
   3. PM wants "where are we at with specs"
      1. by TT
      2. by Dan
      3. by Kathy
   4. overdue on Roadmap
   5. roadblocks
   6. how to organize, modules
   7. going forward: SA vs BA
3. SEARCH
   1. Federated Search (Google Docs folder)
   2. Simplify approach
   3. 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
   4. 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
   5. Acceptance Criteria, Test Scripts- backward, forwards
   6. Above to enable regression testing as features added
4. INSTANCE
   1. Instance 9.x (google docs folder)
   2. possible meeting July 16 or 17
   3. Get key stakeholders in a meeting, and review critical issues- make decisions (KG to summarize existing documentation, work with Patty to prep)
   4. Possible attendees: Patty, Peri, John P, Kathy, Gary C, Frances M, Michelle S, Doreen H
   5. 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

The following is based on items not yet discussed, but listed in several outstanding or planning lists, esp around roadblocks or decisions for OLE 0.8 or 1.0 coding and spec-writing.

• 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)- Not Yet Complete Summary
• Roadmap updates and timeline (S&A additions, reorder, dates)
• Framework questions: 
  • UI & Role/Rule based Defaults and Templates
  • Editors
  • Ingest, overlay
  • Import, export
  • Transmit
  • Patron loads
  • Policy engines (circ; licensing; ingest)
  • Financial integrations
  • Configurable Search, indexing, sort, facets
• Process
  • See (working page): OLE Jira and Backlogging Protocols; Google Docs/working Jira planning docs; OLE Development Cycle
  • 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- OLE User Documentation
    • Platform (Nora's work)
  • Technical: OLE Project Development; OLE Technical Documentation; Service Registries
  • Release: OLE Release Documentation
  • who, what, when, how to maintain
  • wiki vs.....
• UI/UX plan- see: OLE UI & UX

Future: By Functional Module or Specific Requirements/Features

(below are placeholders This section is placeholder, as possible template going forward to track open issues by functional module- to begin to list functional or infrastructure issues by module - will need to improve outline or approach, maybe child or functional wiki pages - TBD with PM)

Acquisitions

• Tiger Team: Select & Acquire (SA: Bob Persing)
• Library Functions: Select, Acquire
• Rice 1/KFS: PURAP, VENDOR, GL; KEW; KIM
• Rice 2: Ingest/Load/Overlay records- KRAD, KRMS (SA: Michelle Suranofsky)
• Infrastructure/dependencies/outstanding decisions:
  • Many-to-One Purchase Order-to- Invoice/Payment Request
  • KFS 5 changes
• Other issues/notes:

...