Pivotal Task Tracker: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 2: | Line 2: | ||
*story - a deliverable; specific request | *story - a deliverable; specific request | ||
=Abstract or User Story= | =Abstract or User Story for Task Tracker= | ||
Right now with GVCS Development we have the wonderful pickle of having many assistance offers, but many of them are not aligned with our core mission. This ends up wasting organizational time on part of the core GVCS development team. To address this, we are pursuing a task tracking system which by design - or automatically - puts people on the right track. | Right now with GVCS Development we have the wonderful pickle of having many assistance offers, but many of them are not aligned with our core mission. This ends up wasting organizational time on part of the core GVCS development team. To address this, we are pursuing a task tracking system which by design - or automatically - puts people on the right track. | ||
Revision as of 19:27, 30 May 2011
- User story - a request; who is requesting somethind and why
- story - a deliverable; specific request
Abstract or User Story for Task Tracker
Right now with GVCS Development we have the wonderful pickle of having many assistance offers, but many of them are not aligned with our core mission. This ends up wasting organizational time on part of the core GVCS development team. To address this, we are pursuing a task tracking system which by design - or automatically - puts people on the right track.
Properties of Tracker:
- Low entry barrier to participation
- Infinite spawnability of new projects
- By invite only