Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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

Operated as a Community Resource by the Open Library Foundation