User:Nlee/Task tracker requirements

The General Gist

In implementing a task/project tracking system for the wiki, we want to be clear on our objectives. What capabilities do we want our tracker to have? Who should be able to use it, and how much should they be able to access?

There are multiple groups of people who will be using a task tracking system:

• admins - people who will be supervising organization and categorization of projects
• project leaders - the actual people who are coming up with and implementing a project
• project volunteers - people who want to pitch in on other people's projects

Functionality

What should people be able to do with the task tracking system?

Admins

Admins need to be able to "get behind the scenes" and take control of abandoned projects, etc.

• change the status of a project (pending, active, inactive, etc.)
  • current model involves only admins having this power
• edit projects
• move/recategorize project tasks

Project leaders

• create projects
• create subtasks and associate them with projects
• delete or remove subtasks from projects
• categorize subtasks (time needed, etc.)

Project volunteers

• find subtasks to do
  • should be able to easily figure out what overarching project is, who project leader is, who else is working on it, etc.
  • sorting based on time needed - minutes, hours, days, etc.
  • sorting based on level of skill needed - little/no experience, programming, language, etc.
• sign up for subtasks
• drop subtasks (un-sign up)
• mark tasks as completed

Categorizations

What searchable labels/categorizations should projects and subtasks be labeled with? What other information should be available?

• for subtasks, what project they tie into
• time needed
• amount of experience or skill needed
• suggested number of people (note to self: see if multiple people can sign up for a task)
• general project information
  • project description should be either included or very, very easy to find (think either on the task, or one "click me, click me!" link away)
  • project leader - for communication, questions, etc.
  • other people involved in task, if applicable
  • other people involved in project?

Feedback

• skill requirements for a task are perhaps a set of <skill, level> tuples. rather than a single tuple.
• tasks tend to accumulate notes and commentary. and so should have an associated wiki place.
• a very big value added not mentioned is being able to see what's going on. generate reports, etc.
• there are various olpc project things which one really wants a real database for. it might be a nifty extra benefit if this project was a prototype/foundation for blending database like things with the wiki.

MitchellNCharity 17:01, 16 October 2007 (EDT)