Versions Compared

Version Old Version 22 New Version Current
Changes made by

Kathleen Gerdink

Nora Roggeveen-Sams (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

(warning) Team pages for roles and responsibilities with Development Process Model are being updated and reformatted.

Section
Column
width50%
Panel
borderColor#A40000
bgColor#F8F8F8
titleBGColor#E8E8E8
titleContents
borderStyledashed
Table of Contents
minLevel1
outlinefalse

See below linked document and detailed task assignments that reflect the roles and responsibilities of SME Teams in the OLE Development Process.

HTML Comment

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} *

Column

SME Teams

Leads

Acquisitions/Financial:

Select

&

Acquire Tiger Team (C Ruschoff) * Cataloging: Describe-Manage Tiger Team (M Charbonneau) * Circulation: Deliver Tiger Team (R Schipper) * ERMS: Manage-Entity-Relationship Tiger Team (T McGeary) * Implementations/Technical: Systems Integration Tiger Team (M Tamarkin) * Identity Management: Manage-User-Relationships Tiger Team (F McNamara) * Subscriptions project: GoKB (K Antelman) * Roadmap Development/Scope Decisions: Scope Tiger Team (T McGeary)&nbsp; 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. ## Update working Roadmaps with matching user stories for each "Work Package", with Jira numbers, who assigned to, and due dates/progress. ###

Acquire

S Wiles-Young

Cataloging: Describe-Manage

M & G Charbonneau

Circulation: Deliver

E Batista

Implementations/Technical: Systems Integration

P Subrahmanya

Subscriptions project: GoKB

K Antelman

Task Assignments

Section
Column
width75%

(see the draft development cycle and approach page for further details)

Prioritization - SME Teams
  1. (2) -assign stories to Roadmap
    1. Identify key user stories that match up to each Roadmap bulleted task or deliverable.
    2. Update working Roadmaps with matching user stories for each "Work Package", with Jira numbers, who assigned to, and due dates/progress.
      1. Wiki Markup
        {html}<A href="https://docs.google.com/a/kuali.org/
spreadsheet/ccc
      1. leaf?
key
      1. id=
0ApyHKv6I9MPFdFh3ZlIyZllrNjNxY1FUZTJTbFQ1Q2c
      1. 0ByXT6YhAHSXFM0xxZ2djd1lSV2s &hl=en_
US#gid=0
      1. US\\
 " mce_href="https://docs.google.com/a/kuali.org/
spreadsheet/ccc
      1. leaf?
key
      1. id=
0ApyHKv6I9MPFdFh3ZlIyZllrNjNxY1FUZTJTbFQ1Q2c
      1. 0ByXT6YhAHSXFM0xxZ2djd1lSV2s &hl=en_
US#gid=0
      1. US\\
 " target="_Blank"
><strong>Working
      1. >OLE
OLE
      1. SCOPE
0.6 Timeline</strong><
      1. AND SCHEDULE-COPY</A>{html}
### {html}<A href="
      2.  HTML Comment
        https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=
0AuB_LtZjzdSedG9kRVB5Z1laTEMzc1RIWTFBam5NMXc
      1. 0ApyHKv6I9MPFdFh3ZlIyZllrNjNxY1FUZTJTbFQ1Q2c&hl=en_US#gid=0
" mce_href="
      2.  HTML Comment
        https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0AuB_LtZjzdSedG9kRVB5Z1laTEMzc1RIWTFBam5NMXc&hl=en_US#gid=0
" target="_Blank"><strong>Working OLE 0.8 Timeline</strong></A>{html}
### 
      2. (OLE 
 
      1.  1.0 
 
      1.  Timeline 
 
      1.  coming 
 
      1.  soon)

## 
    2. Determine 
 
    1.  white-paper/research 
 
    1.  needs 
 
    1.  and 
 
    1.  teams, 
 
    1.  versus 
 
    1.  spec 
 
    1.  writing 
 
    1.  needs/teams.

# 
  2. (3) 
\
  1.  -
 
  1. Prioritize 
 
  1.  Stories

## 
    1. Use 
 
    1.  Roadmap 
 
    1.  or 
 
    1.  other 
 
    1.  brainstorming 
 
    1.  for 
 
    1.  identifying 
 
    1.  "Critical 
 
    1.  functionality" 
 
    1.  to 
 
    1.  prioritize 
 
    1.  efforts 
 
    1.  and 
 
    1.  teams.

## 
    2. Plan 
 
    1.  assignments, 
 
    1.  and 
 
    1.  maintain 
 
    1.  organization 
 
    1.  on 
 
    1.  their 
 
    1.  status, 
 
    1.  for 
 
    1.  eventual 
 
    1.  updates 
 
    1.  to 
 
    1.  Timeline 
 
    1.  worksheets 
 
    1.  and 
 
    1.  Spec 
 
    1.  inventory 
 
    1.  in 
 
    1.  Jira 
 
    1.  (specs 
 
    1.  in 
 
    1.  progress, 
 
    1.  spec 
 
    1.  inventory, 
 
    1.  final 
 
    1.  specs, 
 
    1.  coding, 
 
    1.  etc).

## 
    2. As 
 
    1.  stories 
 
    1.  are 
 
    1.  annotated, 
 
    1.  Jira 
 
    1.  will 
 
    1.  need 
 
    1.  to 
 
    1.  be 
 
    1.  updated 
 
    1.  with 
 
    1.  most 
 
    1.  current, 
 
    1.  governed 
 
    1.  list 
 
    1.  of 
 
    1.  stories 
 
    1. by the Project Team (new 
 
    1.  stories; 
 
    1.  duplicates; 
 
    1.  one 
 
    1.  spec 
 
    1.  for 
 
    1.  multiple 
 
    1.  stories; 
 
    1.  etc).

# 
  2. (4) 
\
  1.  -
 
  1. Assign 
 
  1.  stories 
 
  1.  and 
 
  1.  deadlines 
 
  1.  to 
 
  1.  teams

## 
    1. Solicit 
 
    1.  SMEs 
 
    1.  to 
 
    1.  complete 
 
    1.  above 
 
    1.  work

## [Draft SOW#sow|Specification & Documentation Templates]&nbsp;(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)&nbsp;or Nora (nroggeve@indiana.edu)&nbsp;can assist in updating Jira with known spec statuses and any new tasks or stories.


(8)\-*REVIEW\-* Tiger Team (see:[Specification & Documentation Templates]&nbsp;for TT role in Review of Document)
# 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)
# Update Jira with "spec inventory" (with SA, Carla, or Nora).

(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.
{anchor:gap}

(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
    2. Draft 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
    3. SME Team to assist Team System Analyst as needed to organize and kickoff each spec team.
    4. 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.
(8) Review - SME Team
(see:Specification & Documentation Templates - Not sure (Archive?) for SME Team role in Review of Document)
  1. Review and approve specs: are they complete and in approved fSpec template?
  2. Are data needs annotated and complete in approved Data Requirements template?
  3. Finalize or add Acceptance Criteria - what and how?
  4. Note anything out of scope
  5. Meet with PM to help determine prioritization (if not in schedule)
  6. Sample data needs identified (ie, test data) - given to SA and TC
  7. Sample technical integration points culled by TC (ie for APIs, other tech specs needed)
  8. Upload specs to jira, updating workflow, and send email to Project Manager and Business Analyst (SA can complete this)
(12), (17) Handoffs and Reviews
  1. Participate in handoffs to developers as requested.
  2. Make decisions on scope creep or other Q&A as required by SA and Project Team.
  3. Gap analysis as below.
(23), (25)-(26) Testing: Spec Team, SME Team, QA Manager
  1. Identify testing SMEs as required and assign to efforts.
  2. Participate in Acceptance Testing as requested.
  3. Gap Analysis as below.
     Anchor
    gap
    gap
(iterative) Gap Analysis: SME Team
  1. Specs (8):
    1. Review specs for identifiable gaps or completeness.
    2. Remove or note any items "out of scope".
    3. Create new user stories or assign specs in re-prioritization efforts when gaps identified as part of initial spec writing.
  2. Codeable Specs (11):
    1. Repeat above reviews as requested, when Project Team identifies variations in "specs-to-coding" due to time or technology constraints.
  3. Testing (23), (25), (26):
    1. Organize and Annotate Gap Analysis with SA as Testers or Spec Teams identify known gaps in coded product.
    2. Re-prioritize items that have fallen out of coding in current releases for inclusion in future releases.
  4. Iterative Gap Analysis (from coding-begin to Acceptance):
    1. SME Team is to manage overall gap analysis as part of iterative design process.
    2. Project Team & SA are responsible for communicating gaps during coding as a result of technology constraints, so SME Team can re-prioritize or SA can discuss with Spec Team.
    3. General oversight
 Column
 HTML Table
border0
 Table Row (tr)
 Table Cell (td)
alignright
Phases:
 (info) For the complete model, see 
 OLE Development Cycle 

 Spec Writing
 Table Cell (td)
alignright
Image Added
 Table Row (tr)
 Table Cell (td)
alignright

 Coding
 Table Cell (td)
alignright
Image Added
 Table Row (tr)
 Table Cell (td)
alignright

 Testing
 Table Cell (td)
alignright
Image Added
 Table Row (tr)