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