Home

Meeting Schedule and Work Plan (version 1; 15 Jan)

  1. 20 Jan-- Organizing Meeting for Everyone
    • Everyone signs up for a topic team (leads might already by in place)
    • Everyone also signs up to be a reviewer of two other topic teams
    • Some people have signed up to represent POVs or disciplines and to take a cross-topic review perspective as an advocate for that POV... do we need more than 1 person in this role for each POV?
    • Create "style" team to establish guidelines for writing style, structural granularity, incorporation of non text content, links,...
    • Create "multichannel" team to define relationship between book and online e environment; need classification / identification scheme for news and blog items to tie them to topic content
    • Create technology/platform/tools team
    • Nick and Ryan to set up and manage team to refine and package IO Lab content and determine relationship to topical content
  2. 20 Jan to 1 Feb
    • Each topic team identifies the concepts and examples for its chapter(s); don’t do this in coordination with other teams yet – important to have each team independently determine what they think goes together.
    • Bob to meet with each team or at least with team lead on Jan 28 or Jan 29
  3. 1 Feb - Everyone Meets Together
    • Discuss progress since Jan 20 and define the review process
    • We need to decide if the chapter bins are right? Are they in the optimal order? How should we “lump and split” to make each of the topic chapters the same length?
  4. 1 Feb to 15 Feb - Reviews
    • Reviews of the Feb 1 outlines/lists should be completed in 2 weeks; you are welcome to do more than 2 other teams, but essential to do a careful review; this should be done by 15 Feb but of course you can provide your comments earlier. The vertical POV advocates have a lot to do in this cycle… All of these comments should be made in the wiki
  5. 15 Feb to 22 Feb - Reconciliation and Revision
    • Each topic team should resolve the review comments by 22 Feb; this may involve “trading” or “shedding” topics to other chapters via negotiation among two or more teams that claim a particular concept. (This may be resolved by getting one team to commit to writing foundational material to foreshadow later chapter)
    • This activity will almost certainly cause some changes to the list of topic chapters; in particular, I expect that “Description” is going to be broken up. It may also lead to some changes in team composition or responsibilities
  6. 22 Feb -- Everyone Meets Together
    • Discussion of reconciliation efforts to finalize topical structure
    • Presentation of the writing style guide
    • Presentation by the multichannel team
    • Presentation by the technology/platform team
    • Presentation by the IO Lab team
  7. 22 Feb to 8 March - Writing First Draft
  8. 8 March - Everyone Meets Together
    • Discuss progress since 22 Feb and define the review process
    • Same review assignments as in first round review
    • Reviews due by 29 March (end of spring break)
  9. 29 March - Everyone Meets Together
    • Each topic team should resolve the review comments by 5 April; this may involve meeting with the reviewers; important in this round to improve connectivity as well as content.
    • Bob will meet with each team between 3/29 and 4/2, preferably earlier in the week
  10. 29 March to 5 April -- Reconciliation and Revision
  11. 5 April -- Everyone Meets Together
  12. 5 April to 19 April -- Writing Second Draft
  13. 19 April -- Everyone Meets Together
    • Shuffle reviewer assignments so that everyone reviews at least two chapters they haven't (officially) reviewed before.
  14. 19 April to 3 May -- Reviewing Second Drafts
  15. 3 May -- Everyone Meets Together
  16. 3 May to 7 May -- Reconciliation and Revision
  17. 8 or 9 May -- Party in St Helena