(see the [*draft development cycle and approach*|OLE:OLE Development Cycle] page for further details)
h6. Prioritization \- Tiger Teams
# (2) \-assign stories to Roadmap
## Identify key user stories that match up to each Roadmap bulleted task or deliverable.
## Update working Roadmaps with matching user stories for each "Work Package", with Jira numbers, who assigned to, and due dates/progress.
### {html}<A href="https://docs.google.com/a/kuali.org/leaf?id=0ByXT6YhAHSXFM0xxZ2djd1lSV2s &hl=en_US\\
" mce_href="https://docs.google.com/a/kuali.org/leaf?id=0ByXT6YhAHSXFM0xxZ2djd1lSV2s &hl=en_US\\
" target="_Blank">OLE SCOPE AND SCHEDULE-COPY</A>{html}
### {link-window:http://goo.gl/vYO7b|scrollbars=true|menubar=true|location=true|statusbar=true|resizable=true|width=800|height=600|icon=false}Working OLE 0.6 Timeline{link-window}
{HTMLcomment}[https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0ApyHKv6I9MPFdFh3ZlIyZllrNjNxY1FUZTJTbFQ1Q2c&hl=en_US#gid=0]
{HTMLcomment}
### {link-window:http://goo.gl/1XeSo|scrollbars=true|menubar=true|location=true|statusbar=true|resizable=true|width=800|height=600|icon=false}Working OLE 0.8 Timeline{link-window}
{HTMLcomment}[https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0AuB_LtZjzdSedG9kRVB5Z1laTEMzc1RIWTFBam5NMXc&hl=en_US#gid=0]
{HTMLcomment}
### (OLE 1.0 Timeline coming soon)
## Determine white-paper/research needs and teams, versus spec writing needs/teams.
# (3) \-Prioritize Stories
## Use Roadmap or other brainstorming for identifying "Critical functionality" to prioritize efforts and teams.
## Plan assignments, and maintain organization on their status, for eventual updates to Timeline worksheets and Spec inventory in Jira (specs in progress, spec inventory, final specs, coding, etc).
## As stories are annotated, Jira will need to be updated with most current, governed list of stories by the Core Team (new stories; duplicates; one spec for multiple stories; etc).
# (4) \-Assign stories and deadlines to teams
## Solicit SMEs to complete above work
## [Draft SOW|Specification & Documentation Templates#sow] (see template) - Statement of Work for each spec team, to guide efforts, identify story goals or boundaries of the effort, what may be future or out of scope (if known), and any known precursors
## Tiger Team to assist Tiger Team System Analyst as needed to organize and kickoff each spec team.
## SA, Carla (cnorth@indiana.edu) or Nora (nroggeve@indiana.edu) can assist in updating Jira with known spec statuses and any new tasks or stories.
h6. (8) Review \- Tiger Team
(see:[Specification & Documentation Templates] for TT role in Review of Document)
# Review and approve specs: are they complete and in approved fSpec template?
# Are data needs annotated and complete in approved Data Requirements template?
# Finalize or add Acceptance Criteria - what and how?
# Note anything out of scope
# Meet with PM to help determine prioritization (if not in schedule)
# Sample data needs identified (ie, test data) - given to SA and TC
# Sample technical integration points culled by TC (ie for APIs, other tech specs needed)
# Upload specs to jira, updating workflow, and send email to Project Manager and Business Analyst (SA can complete this)
h6. (12), (17) Handoffs and Reviews
# Participate in handoffs to developers as requested.
# Make decisions on scope creep or other Q&A as required by SA and Core Team.
# Gap analysis as below.
h6. (23), (25)-(26) Testing: Spec Team, Tiger Team, QA Manager
# Identify testing SMEs as required and assign to efforts.
# Participate in Acceptance Testing as requested.
# Gap Analysis as below.
{anchor:gap}
h6. (iterative) Gap Analysis: Tiger Team
# Specs (8):
## Review specs for identifiable gaps or completeness.
## Remove or note any items "out of scope".
## Create new user stories or assign specs in re-prioritization efforts when gaps identified as part of initial spec writing.
# Codeable Specs (11):
## Repeat above reviews as requested, when Core Team identifies variations in "specs-to-coding" due to time or technology constraints.
# Testing (23), (25), (26):
## Organize and Annotate Gap Analysis with SA as Testers or Spec Teams identify known gaps in coded product.
## Re-prioritize items that have fallen out of coding in current releases for inclusion in future releases.
# Iterative Gap Analysis (from coding-begin to Acceptance):
## Tiger Team is to manage overall gap analysis as part of iterative design process.
## Core Team & SA are responsible for communicating gaps during coding as a result of technology constraints, so Tiger Team can re-prioritize or SA can discuss with Spec Team.
## General oversight
| 
