Let's document, as orderly as possible, the justification for putting in development time for this dynamic schedule.
The value to the user is same
Static Schedule is a couple minutes to maintain weekly - estimating really high @ 5m, still easy; the web team meets weekly - could be done while waiting for all to join the call.
Dynamic: What does this mean? Taking the information from Confluence when it is shown to the user? (7/12,JimD)
________________________
Pros - benefits of making the schedule dynamic vs. static
- a) A non-web team member can update it. (7/12,JimD)
- b) Currently updating redundant information → http://confluence.technologynursery.org/display/TSSG (7/12,JimD)
- c) Single source of truth of schedule (7/12,JimD)
- d) No web skills required (7/12,JimD)
Cons - downside of making the schedule dynamic
- a) Other area affected - Confluence, TSSG space, Venue SSOT page. Concern: falling into temptation to make the calendar cluttered with more than Wednesday Schedule whereas that site is for new prospects, not members. SHOULD a member login area be added, the dynamic format makes more sense.
- b) Adds development time.
- c)