Versions Compared

Version Old Version 2 New Version 3
Changes made by

Kathleen Gerdink (Unlicensed)

Kathleen Gerdink (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. Start up a team: FC
    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.  
  3. How to start up a team: Facilitator
    1. Provide an overview of specification process (general FAQ any team can use)
    2. Provide overview link to Agile team approach (brief)
    3. Best Practices communicated in leader's guide:
      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
     
  4. Team Administration: Tools for managing specification team or other OLE team
  5. KIS access set up for new users
  6. New users added to file permissions for folders they need to access
  7. Access to OLE Scheduling calendar for key milestones, and conference call lines
  8. FreeConferenceCall dedicated callin line established
  9. Setup KIS team page
  10. Calendar
  11. Email distribution list
  12. All team members contact information
  13. Hotlink to Google Docs area
  14.  
  15. Google Docs Team folder
  16. Pre-seeded specification word docs for each spec to be completed
  17. Data modeling resources only for this set of related specs
  18. Pre-existing workflow models related to this set of specs
  19. Creation of draft/beginning Service Contract for related OLE Functions (overview) inc list to populate for business rules,
  20.  
  21. user roles, sample data
  22. Backlog/excel file of related user stories in workflow order with library labels
  23. Links to previously completed and related specification documents (prior teams)-examples
  24.  
  25. Creation of Spec Team Roadmap (as part of planning documents)
  26. FAQ on Wiki for frequently-used tools, Q&A, PPT to train/kickoff
  27. Improvements to spec document template
  28. See 1-4 above and document in FAQ
  29. See Google Docs SpecRoadmap
  30. Create self-paced training guide to specifications and orientation to OLE overall
  31. Include team/approach options from KG Spec Approach document
  32. Share link to overall specs, sprints, project schedule to convey understanding and urgency (in development)
  33. Schedules for specs, inc.: deadlines; startup/kickoff to educate team; Feedback Loop calls with core; handoff call to
  34.  
  35. Product Owner
  36. Facilitators Guide (this document)