Whiteboard
White Board
If the desire becomes to create or adopt a tool to manage tasks, what are the requirements?
Assumptions
- Tool will be web based
- Development will be collaborative and transparent
- Process will be intuitive/easy
Requirements
- Task must have a community/business sponsor
1.1 Task must capture posting date
1.2 Task must capture desired completion date or ASAP
1.3 Task must have a state ( viz. proposed, active, complete, closed )
- Task must be assigned
- Task must have one or more contributors
- Task must reference a spec ( Wiki ? )
4.1 Task must state purpose
4.2 Task must identify stake holders
4.3 Task must identify requirements
4.4 Task must describe submission process
- Effort which is defined as large in scope or has several related tasks may be defined as a project ( viz. Icon Project ).
May share a single spec.
Risks
- Can the tool be created in a timely manner?
- Will the change cause a lack of participation?
If the desire becomes to create or adopt a tool to store submissions, what are the requirements?
Assumptions
- Tool will be web based
- Submissions will be appropriately licensed
- Attribution will be given when appropriate
Requirements
- Repository must support duplicates or version-ed submissions
- Repository must support multiple file formats
- Submissions must link to a task/proposal
- Submissions must capture threaded comments ( Blog style ? )
- Submissions must identify submitter
Risks
- Can the tool be created in a timely manner?
- Will the change cause a lack of participation?
Artwork/Documentation/Blueprint/Whiteboard (last edited 2010-10-26 14:10:25 by 136)