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 2 Next »

  1. Start up a team: FC
  2. Identify team members from partner staff, draft solicitation
  3. The Specification Writing Roadmap, for each functional area, provides
  4. Scoped time frame
  5. Skills required from SMEs
  6. Testing team requirement
  7. Charge to team contains
  8. Vision for functional area
  9. Context of that functional area within OLE
  10. Suggestion of 'straight line path' if one exists
  11. Makeup of spec writing team
  12. SMEs (4-10)
  13. Facilitator - a veteran SME
  14. Core team member(s)
  15. User Stories
  16. Groomed by US & Core team
  17. Grouped by functional area
  18. Library/workflow labels applied prior to team start
  19. Goals from FC
  20. Improve efficiency of specification writing efforts
  21. Balance concerns for overuse of particular staff
  22. Mentoring opportunities within partner staff
  23. Decouple spec writing from development sprints
  24.  
  25. How to start up a team: Facilitator
  26. Provide an overview of specification process (general FAQ any team can use)
  27. Provide overview link to Agile team approach (brief)
  28. Best Practices communicated in leader's guide:
  29. process should be viewed as independent & autonomous but should articulate dependencies
  30. concept of the "straight line"
  31. 80/20 rule: 20% of the resources create 80% of the effects
  32. note data requirements & sources / inputs & outputs
  33. facilitator should orient team to the process
  34. facilitator is responsible to report back to the FC with status updates
  35.  
  36. Team Administration: Tools for managing specification team or other OLE team
  37. KIS access set up for new users
  38. New users added to file permissions for folders they need to access
  39. Access to OLE Scheduling calendar for key milestones, and conference call lines
  40. FreeConferenceCall dedicated callin line established
  41. Setup KIS team page
  42. Calendar
  43. Email distribution list
  44. All team members contact information
  45. Hotlink to Google Docs area
  46.  
  47. Google Docs Team folder
  48. Pre-seeded specification word docs for each spec to be completed
  49. Data modeling resources only for this set of related specs
  50. Pre-existing workflow models related to this set of specs
  51. Creation of draft/beginning Service Contract for related OLE Functions (overview) inc list to populate for business rules,
  52.  
  53. user roles, sample data
  54. Backlog/excel file of related user stories in workflow order with library labels
  55. Links to previously completed and related specification documents (prior teams)-examples
  56.  
  57. Creation of Spec Team Roadmap (as part of planning documents)
  58. FAQ on Wiki for frequently-used tools, Q&A, PPT to train/kickoff
  59. Improvements to spec document template
  60. See 1-4 above and document in FAQ
  61. See Google Docs SpecRoadmap
  62. Create self-paced training guide to specifications and orientation to OLE overall
  63. Include team/approach options from KG Spec Approach document
  64. Share link to overall specs, sprints, project schedule to convey understanding and urgency (in development)
  65. Schedules for specs, inc.: deadlines; startup/kickoff to educate team; Feedback Loop calls with core; handoff call to
  66.  
  67. Product Owner
  68. Facilitators Guide (this document)
  • No labels

Operated as a Community Resource by the Open Library Foundation