...
1. Introductions/Expectations/Skills/Availability of participants
2.
...
- Scope (redistributable KB or wiki, prioritized list of docs needed)
- Exploration of different levels of documentation for different audiences
3. Timeframe
4. Success stories, other products available?
Current Status
- Study of Samigo, at Stanford: Current Status of Tests & Quizzes Documentation (R. Hill)
- Why is it so hard to document the portfolio tools? (R. Hill, relying on S. Keesler)
- Because we're too lazy to learn the skills clearly designated as necessary; we want documentation to reveal the effort-free path.
- Because the Help files are written to an audience (faculty at Indiana) that understands the entire context.
- Because Sean's comprehensive documents on Confluence are found in different branches of the hierarchy.
- Because there is no visible intermediate result that affords the author a self-check of progress.
- Because there are assumed procedures and scenarios that hide restrictions.
- Because portfolios, insofar as they capture the essence of learning, are inherently complex objects.
3. Define goals
- Scope (redistributable KB or wiki, prioritized list of docs needed)
- Exploration of different levels of documentation for different audiences