Versions Compared

Version Old Version 35 New Version Current
Changes made by

Nora Roggeveen-Sams (Unlicensed)

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 Team pages for roles and responsibilities with Development Process Model are being updated and reformatted.

Section
{panel:title=Contents|borderStyle=dashed|borderColor=#A40000|titleBGColor=#E8E8E8|bgColor=#F8F8F8} {toc:outline=false|minLevel=1} {panel} See below linked document and detailed task assignments that reflect the roles and responsibilities of Tiger Teams in the OLE Development Process. {link-window:http://goo.gl/YC95J|scrollbars=true|menubar=true|location=true|statusbar=true|resizable=true|width=800|height=600|icon=false}Draft Development Cycle -- Narrative Description, 2/3/2012{link-window} {HTMLcomment}[
Column
width50%
Wiki Markup
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

]{HTMLcomment}

Column

Tiger SME Teams

Leads

Acquisitions/Financial: Select & Acquire Tiger Team C Ruschoff

S Wiles-Young

Cataloging: Describe-Manage Tiger Team

M & G Charbonneau

Circulation: Deliver Tiger Team

R Schipper, C Case

Bib & Instance Editors: Record Creation/Modification

M Suranofsky

ERMS: Manage-Entity-Relationship Tiger Team

T McGeary

E Batista

Implementations/Technical: Systems Integration Tiger Team

C Case P Subrahmanya

Subscriptions project: GoKB

K Antelman Roadmap Development/Scope Decisions: Scope Tiger Team

T McGeary

Task Assignments

Section
unmigrated-wiki-markup
Column
width75%

(see

the

[*

draft

development

cycle

and

approach

*|OLE:OLE Development Cycle]

page

for

further

details)

h6. Prioritization \- Tiger Teams #

Prioritization - SME Teams
  1. (2)
\
  1. -assign
  1. stories
  1. to
  1. Roadmap
##
    1. Identify
    1. key
    1. user
    1. stories
    1. that
    1. match
    1. up
    1. to
    1. each
    1. Roadmap
    1. bulleted
    1. task
    1. or
    1. deliverable.
##
    2. Update
    1. working
    1. Roadmaps
    1. with
    1. matching
    1. user
    1. stories
    1. for
    1. each
    1. "Work
    1. Package",
    1. with
    1. Jira
    1. numbers,
    1. who
    1. assigned
    1. to,
    1. and
    1. due
    1. dates/progress.
###
      1. Wiki Markup
        {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}[
      2.  HTML Comment
        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}[
      2.  HTML Comment
        https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0AuB_LtZjzdSedG9kRVB5Z1laTEMzc1RIWTFBam5NMXc&hl=en_US#gid=0
]
{HTMLcomment}
### 
      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.  -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 
 
    1.  the 
 Core 
    1. Project Team 
 
    1.  (new 
 
    1.  stories; 
 
    1.  duplicates; 
 
    1.  one 
 
    1.  spec 
 
    1.  for 
 
    1.  multiple 
 
    1.  stories; 
 
    1.  etc).

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

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

## [
    2. Draft 
 
    1.  SOW
|Specification & Documentation Templates#sow] 
    1.  (see 
 
    1.  template) 
 
    1.  - 
 
    1.  Statement 
 
    1.  of 
 
    1.  Work 
 
    1.  for 
 
    1.  each 
 
    1.  spec 
 
    1.  team, 
 
    1.  to 
 
    1.  guide 
 
    1.  efforts, 
 
    1.  identify 
 
    1.  story 
 
    1.  goals 
 
    1.  or 
 
    1.  boundaries 
 
    1.  of 
 
    1.  the 
 
    1.  effort, 
 
    1.  what 
 
    1.  may 
 
    1.  be 
 
    1.  future 
 
    1.  or 
 
    1.  out 
 
    1.  of 
 
    1.  scope 
 
    1.  (if 
 
    1.  known), 
 
    1.  and 
 
    1.  any 
 
    1.  known 
 precursors
## Tiger Team to assist Tiger Team System Analyst as needed to organize and kickoff each spec team.
## SA, Carla 
    1. precursors
    2. SME Team to assist Team System Analyst as needed to organize and kickoff each spec team.
    3. SA, Carla (cnorth@indiana.edu) 
 
    1.  or 
 
    1.  Nora 
 
    1.  (nroggeve@indiana.edu) 
 
    1.  can 
 
    1.  assist 
 
    1.  in 
 
    1.  updating 
 
    1.  Jira 
 
    1.  with 
 
    1.  known 
 
    1.  spec 
 
    1.  statuses 
 
    1.  and 
 
    1.  any 
 
    1.  new 
 
    1.  tasks 
 
    1.  or 
 
    1.  stories.


h6. 
(8) 
 
 Review 
 \
 - 
 Tiger Team 

SME 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), 
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, 
 Tiger 
SME Team, 
 
 QA 
 
 Manager


# 
  1. Identify 
 
  1.  testing 
 
  1.  SMEs 
 
  1.  as 
 
  1.  required 
 
  1.  and 
 
  1.  assign 
 
  1.  to 
 
  1.  efforts.

# 
  2. Participate 
 
  1.  in 
 
  1.  Acceptance 
 
  1.  Testing 
 
  1.  as 
 
  1.  requested.

# 
  2. Gap 
 
  1.  Analysis 
 
  1.  as 
 
  1.  below.

{anchor:gap}

h6. 

  1.  Anchor
    gap
    gap
(iterative) 
 
 Gap 
 
 Analysis: 
 Tiger Team

# Specs 
SME Team
  1. Specs (8):

## 
    1. Review 
 
    1.  specs 
 
    1.  for 
 
    1.  identifiable 
 
    1.  gaps 
 
    1.  or 
 
    1.  completeness.

## 
    2. Remove 
 
    1.  or 
 
    1.  note 
 
    1.  any 
 
    1.  items 
 
    1.  "out 
 
    1.  of 
 
    1.  scope".

## 
    2. Create 
 
    1.  new 
 
    1.  user 
 
    1.  stories 
 
    1.  or 
 
    1.  assign 
 
    1.  specs 
 
    1.  in 
 
    1.  re-prioritization 
 
    1.  efforts 
 
    1.  when 
 
    1.  gaps 
 
    1.  identified 
 
    1.  as 
 
    1.  part 
 
    1.  of 
 
    1.  initial 
 
    1.  spec 
 
    1.  writing.

# 
  2. Codeable 
 
  1.  Specs 
 
  1.  (11):

## 
    1. Repeat 
 
    1.  above 
 
    1.  reviews 
 
    1.  as 
 
    1.  requested, 
 
    1.  when 
 Core 
    1. Project Team 
 
    1.  identifies 
 
    1.  variations 
 
    1.  in 
 
    1.  "specs-to-coding" 
 
    1.  due 
 
    1.  to 
 
    1.  time 
 
    1.  or 
 
    1.  technology 
 
    1.  constraints.

# 
  2. Testing 
 
  1.  (23), 
 
  1.  (25), 
 
  1.  (26):

## 
    1. Organize 
 
    1.  and 
 
    1.  Annotate 
 
    1.  Gap 
 
    1.  Analysis 
 
    1.  with 
 
    1.  SA 
 
    1.  as 
 
    1.  Testers 
 
    1.  or 
 
    1.  Spec 
 
    1.  Teams 
 
    1.  identify 
 
    1.  known 
 
    1.  gaps 
 
    1.  in 
 
    1.  coded 
 
    1.  product.

## 
    2. Re-prioritize 
 
    1.  items 
 
    1.  that 
 
    1.  have 
 
    1.  fallen 
 
    1.  out 
 
    1.  of 
 
    1.  coding 
 
    1.  in 
 
    1.  current 
 
    1.  releases 
 
    1.  for 
 
    1.  inclusion 
 
    1.  in 
 
    1.  future 
 
    1.  releases.

# 
  2. Iterative 
 
  1.  Gap 
 
  1.  Analysis 
 
  1.  (from 
 
  1.  coding-begin 
 
  1.  to 
 
  1.  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

    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 Removed Image Added
 Table Row (tr)
 Table Cell (td)
alignright

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

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