Page Comparison

h5.
{note}Under Construction.{note}{html}<A href="https://docs.google.com/a/kuali.org/document/d/1ybw-WwuGdFhvUDlbha1BVNnaTFObWEbLNYzHqui4MIQ/edit?hl=en_US" mce_href="https://docs.google.com/a/kuali.org/document/d/1ybw-WwuGdFhvUDlbha1BVNnaTFObWEbLNYzHqui4MIQ/edit?hl=en_US" target="_Blank">Draft Development Cycle - Narrative Description, 1/6/2012</A>{html}


h2. Task Assignments

*PRIORITIZATION*\- Tiger Teams
# (2)-assign stories to Roadmap
## Identify key user stories that match up to each Roadmap bulleted task or deliverable
## Determine white-paper/research needs and teams, versus spec writing needs/teams.
# (3)\- Prioritize Stories
## Prioritize stories per above for assignment, and maintain organization on their status, for eventual updates to Spec inventory and Jira (specs in progress, spec inventory, final specs, coding, etc).
# (4)\- Assign stories and deadlines to teams
## Solicit SMEs to complete above work
## Draft SOW\- 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.

(8)\-*REVIEW\-* Tiger Team
# Review and approve specs
# Finalize or add Acceptance Criteria\- what and how?
# Note anything out of scope
# Meet with PM to help determine prioritization
# Sample data needs identified\- given to SA and TC
# Sample technical integration points culled by TC (ie for APIs, other tech specs needed)

(12), (17)\- *HANDOFFS & 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.

(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.

(iterative) *Gap Analysis*: Tiger Team&nbsp;

# Specs(8):&nbsp;
## Review specs for identifiable gaps or completeness.
## Remove or note any items "out of scope".
## Create new user stories or assign specs in reprioritization 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 reprioritize or SA can discuss with Spec Team.
## General oversight