Page Comparison

...

1. Start up a team: FC

   Anchor
   start start

   1. Identify team members from partner staff, draft solicitation
      1. The Specification Writing Roadmap, for each functional area, provides:
         1. Scoped time frame
         2. Skills required from SMEs
         3. Testing team requirement
   2. Charge to team contains
      1. Vision for functional area
      2. Context of that functional area within OLE
      3. Suggestion of 'straight line path' if one exists
   3. Makeup of spec writing team
      1. SMEs (4-10)
      2. Facilitator - a veteran SME
      3. Core team member(s)
   4. User Stories
      1. Groomed by US & Core team
      2. Grouped by functional area
      3. Library/workflow labels applied prior to team start
   5. Goals from FC
      1. Improve efficiency of specification writing efforts
      2. Balance concerns for overuse of particular staff
      3. Mentoring opportunities within partner staff
      4. Decouple spec writing from development sprints
2. How to start up a team: Facilitator

   Anchor
   facilitator facilitator

   1. Specification FAQ
   2. Agile Development Methodology
   3. Best Practices :
      1. process should be viewed as independent & autonomous but should articulate dependencies
      2. concept of the "straight line"
      3. 80/20 rule: 20% of the resources create 80% of the effects
      4. note data requirements & sources / inputs & outputs
      5. facilitator should orient team to the process
      6. facilitator is responsible to report back to the FC with status updates
3. Team Administration: Tools for managing specification team or other OLE team

   Anchor
   admin admin

   1. KIS access set up for new users
   2. New users added to file permissions for folders they need to access
   3. Access to OLE Scheduling calendar for key milestones, and conference call lines
   4. FreeConferenceCall dedicated callin line established
   5. Setup KIS team page
      1. Calendar
      2. Email distribution list
      3. All team members contact information
      4. Hotlink to Google Docs area
4. Google Docs Team folder

   Anchor
   google google

   1. Pre-seeded specification word docs for each spec to be completed
   2. Data modeling resources only for this set of related specs
   3. Pre-existing workflow models related to this set of specs
   4. Creation of draft/beginning Service Contract for related OLE Functions (overview) inc list to populate for business rules, user roles, sample data
   5. Backlog/excel file of related user stories in workflow order with library labels
   6. Links to previously completed and related specification documents (prior teams)-examples
5. Creation of Spec Team Roadmap (as part of planning documents)

   Anchor
   creation creation

   1. FAQ on Wiki, PPT to train/kickoff
   2. Improvements to spec document template
   3. See Google Docs SpecRoadmap
   4. See Google Docs help and tips
   5. Create self-paced training guide to specifications and orientation to OLE overall
   6. Include team/approach options from Spec Approach document
   7. Share link to overall specs, sprints, project schedule to convey understanding and urgency (in development)
   8. Schedules for specs, inc.: deadlines; startup/kickoff to educate team; Feedback Loop calls with core; handoff call to Product Owner
   9. Facilitators Guide (this document)

...