Info |
---|
Wiki Markup |
{info}Working page to track requirements and planning issues with BA's\- initial page created per Patty to document workingdiscussion items discussion items {info} Quicklinks/Table of Contents: |
...
Table of Contents | ||||
---|---|---|---|---|
|
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.
Action items identified, KG & PM 6/29/12
- Tiger Teams and Meeting changes
- 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
- 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
- PM wants "where are we at with specs"
- SEARCH
- 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
- possible meeting July 16 or 17
- 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
- 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
- have sit-down on Describe
- 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
- 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?
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)
- Implication Issues
- 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.....
- User
- UI/UX plan- see: OLE UI & UX
Future: By Functional Module or Specific Requirements/Features
(below are placeholders to begin to list functional or infrastructure issues by module- will need to improve outline or approach, maybe child or functional wiki pages- TBD)
...
Acquisitions
...
- Tiger Team: Select & Acquire (SA: Bob Persing)
- Library Functions: Select, Acquire
- Rice 1/KFS: PURAP, VENDOR, GL
- 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:
...
Financial, COA
...
- Tiger Team: Select & Acquire (SA: Bob Persing)
- Library Function: Acquire, Manage funds, budgeting
- Rice 1/KFS: PURAP, COA, FS, PDP, GL, BA
- Infrastructure/dependencies/outstanding decisions:
- KFS 5 changes
- Financial integrations with university systems- OLE 1.0
- FYRO- OLE 1.5
- Other issues/notes:
...
Licensing
...
- Tiger Team: MER (SA: Emily Lynema)
- Library Functions: MER, ERMS, Electronic Resources Management, Licensing
- Rice 1/KFS: None
- Rice 2: License Requests & UIs
- Docstore: Agreements, Agreement Docs, (Future: Deal, Package, Agent)
- Infrastructure/dependencies/outstanding decisions:
- GoKB- OLE 1.0 & 1.5
- Other issues/notes:
...
Cataloging
...
- Tiger Team: Describe/Manage (SA: Michelle Suranofsky)
- Library Functions: Describe, Manage, Editors, Cataloging, Technical Services
- Rice 1/KFS: combined search
- Rice 2: Editors, Ingest/Load/Overlay records- KRAD, KRMS
- Docstore: Bibliographic, Instance, (Future: Authority)
- Infrastructure/dependencies/outstanding decisions:
- Authority Records - OLE 1.5
- Scoping for 1.0
- Other issues/notes:
...
Editors
...
- Tiger Team: Editors (SA & Team lead: Michelle Suranofsky)
- Library Functions: Framework for (above) cataloging
- Rice 1/KFS: N/A
- Rice 2: KRAD UI
- Docstore: Bib, Instance, (Agreement/License thru MER)
- Infrastructure/dependencies/outstanding decisions:
- Framework vs individual UI's
- Scope of system config in OLE 1.0
- Other issues/notes:
...
Circulation
...
- Tiger Team: Deliver (SA: Stuart Miller/Chris Case)
- Library Functions: Circulation, Patrons
- Rice 1/KFS: N/A
- Rice 2: Patron, Checkout/Loans, Checkin, Policies, etc
- Docstore: Bib & Instance, but primary actions on Items and Locations within Instance
- Infrastructure/dependencies/outstanding decisions:
- Patron- further scoping, coding for 1.0
- Other issues/notes:
...
Infrastructure
...
- see each team and global issues
- may belong with Technical below
- Rice 1 vs Rice 2, and providing for future integrations
- Docstore: Document controls, ie Records Management; Checkin and Checkout; Search
- Infrastructure/dependencies/outstanding decisions:
- OLE Identity Management
- APIs: Grouper, Shibboleth etc
- KIM 1 vs 2
- Authz/Authx
- User loads
- Any original IdM, MUR- Manage User Relationships work
- others?
- OLE Identity Management
- Other issues/notes:
...
Technical/Systems Integration
...
- performance improvements
...
{toc:outline=false | maxLevel=2}\\ h2. 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. +Action items identified, KG & PM 6/29/12+ # *Tiger Teams and Meeting changes* ## 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* ## 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* ## 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* ## {html}<A href="https://docs.google.com/a/kuali.org/?ui=1#folders/folder.0. 0B1zG4eNDtxYpNExXNFM5dnd3eUE " mce_href="https://docs.google.com/a/kuali.org/?ui=1#folders/folder.0. 0B1zG4eNDtxYpNExXNFM5dnd3eUE " target="_Blank">Instance 9.x</A>{html} ## possible meeting July 16 or 17 ## 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* ## 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: {color:#0000ff}+[review KFS for what being used; what need to remove|https://wiki.kuali.org/display/OLE/OLE+Rice+1.x+vs.+2.x+Development#OLERice1.xvs.2.xDevelopment-KFS%26Rice1%3AModulesSummary]+{color}; overview future or in progress features # *DESCRIBE\- DOCSTORE* ## have sit-down on Describe ## 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* ## 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? h2. 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)\- [Not Yet Complete Summary|https://docs.google.com/a/kuali.org/document/d/1-IqbfePn73oicDaLXnaVb5sYoRqm1pWrQttsC6wBaG4/edit] ** [Implication Issues|https://docs.google.com/a/kuali.org/document/d/1cc7rIXYI39hSTLLUn901_GpM1-Dw7jhYFceyh8iSLk8/edit] * 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:OLE UI & UX] h2. Future: By Functional Module or Specific Requirements/Features (below are placeholders to begin to list functional or infrastructure issues by module\- will need to improve outline or approach, maybe child or functional wiki pages\- TBD) h6. Acquisitions * Tiger Team: Select & Acquire (SA: Bob Persing) * Library Functions: Select, Acquire * Rice 1/KFS: PURAP, VENDOR, GL * 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: h6. Financial, COA * Tiger Team: Select & Acquire (SA: Bob Persing) * Library Function: Acquire, Manage funds, budgeting * Rice 1/KFS: PURAP, COA, FS, PDP, GL, BA * Infrastructure/dependencies/outstanding decisions: ** KFS 5 changes ** Financial integrations with university systems\- OLE 1.0 ** FYRO\- OLE 1.5 * Other issues/notes: h6. Licensing * Tiger Team: MER (SA: Emily Lynema) * Library Functions: MER, ERMS, Electronic Resources Management, Licensing * Rice 1/KFS: None * Rice 2: License Requests & UIs * Docstore: Agreements, Agreement Docs, (Future: Deal, Package, Agent) * Infrastructure/dependencies/outstanding decisions: ** GoKB\- OLE 1.0 & 1.5 * Other issues/notes: h6. Cataloging * Tiger Team: Describe/Manage (SA: Michelle Suranofsky) * Library Functions: Describe, Manage, Editors, Cataloging, Technical Services * Rice 1/KFS: combined search * Rice 2: Editors, Ingest/Load/Overlay records\- KRAD, KRMS * Docstore: Bibliographic, Instance, (Future: Authority) * Infrastructure/dependencies/outstanding decisions: ** Authority Records - OLE 1.5 ** Scoping for 1.0 * Other issues/notes: h6. Editors * Tiger Team: Editors (SA & Team lead: Michelle Suranofsky) * Library Functions: Framework for (above) cataloging * Rice 1/KFS: N/A * Rice 2: KRAD UI * Docstore: Bib, Instance, (Agreement/License thru MER) * Infrastructure/dependencies/outstanding decisions: ** Framework vs individual UI's ** Scope of system config in OLE 1.0 * Other issues/notes: h6. Circulation * Tiger Team: Deliver (SA: Stuart Miller/Chris Case) * Library Functions: Circulation, Patrons * Rice 1/KFS: N/A * Rice 2: Patron, Checkout/Loans, Checkin, Policies, etc * Docstore: Bib & Instance, but primary actions on Items and Locations within Instance * Infrastructure/dependencies/outstanding decisions: ** Patron\- further scoping, coding for 1.0 * Other issues/notes: h6. Infrastructure * see each team and global issues * may belong with Technical below * Rice 1 vs Rice 2, and providing for future integrations * Docstore: Document controls, ie Records Management; Checkin and Checkout; Search * Infrastructure/dependencies/outstanding decisions: ** OLE Identity Management *** APIs: Grouper, Shibboleth etc *** KIM 1 vs 2 *** Authz/Authx *** User loads *** Any original IdM, MUR\- Manage User Relationships work ** others? * Other issues/notes: h6. Technical/Systems Integration * Tiger Team: Systems Integration (Lead: Chris Case), Technical Council * Library System Functions: Data migrations, Discovery layer, z39.50, NCIP, external interfaces; KFS & Rice upgrades * OLE: API's * Infrastructure/dependencies/outstanding decisions: ** performance improvements * Other issues/notes: |