Pivotal Task Tracker - Revision history

Elifarley: /* See Also */ Added link to Trello

2012-03-28T01:17:24Z

Chris F: /* Alternatives */

2011-09-27T16:25:30Z

Alternatives

← Older revision		Revision as of 16:25, 27 September 2011
Line 60:		Line 60:
	==Alternatives==		==Alternatives==
	* http://retrospectiva.org/ - ''Open-source project management tool, intended to assist the collaborative aspect of work carried out by agile software development teams.''		* http://retrospectiva.org/ - ''Open-source project management tool, intended to assist the collaborative aspect of work carried out by agile software development teams.''

			==See Also==
			*[[Website]]
			*[[Bettermeans]]


	[[Category: Organization]]		[[Category: Organization]]
	[[Category: IT Infrastructure]]		[[Category: IT Infrastructure]]

Elifarley: Added alternative: http://retrospectiva.org/

2011-07-04T10:30:13Z

Added alternative: http://retrospectiva.org/

← Older revision		Revision as of 10:30, 4 July 2011
Line 57:		Line 57:

	Members can optionally break down user stories into finer grained user stories, or they can attach actionable tasks to it. There's also provisions to comment on them, attach files, and move user stories through a cycle of "Not Yet Scheduled, Started, Finished, Delivered, Accepted or Rejected, and Finished." Pivotal takes care of putting the user stories in the right place, and notifying the invested parties: the task requester (often the stakeholder), or the task owner (usually a team member), or everyone on the team (if the team member likes). It's simple, but great at what it does.		Members can optionally break down user stories into finer grained user stories, or they can attach actionable tasks to it. There's also provisions to comment on them, attach files, and move user stories through a cycle of "Not Yet Scheduled, Started, Finished, Delivered, Accepted or Rejected, and Finished." Pivotal takes care of putting the user stories in the right place, and notifying the invested parties: the task requester (often the stakeholder), or the task owner (usually a team member), or everyone on the team (if the team member likes). It's simple, but great at what it does.

			==Alternatives==
			* http://retrospectiva.org/ - ''Open-source project management tool, intended to assist the collaborative aspect of work carried out by agile software development teams.''

	[[Category: Organization]]		[[Category: Organization]]
	[[Category: IT Infrastructure]]		[[Category: IT Infrastructure]]

Vann at 22:56, 21 June 2011

2011-06-21T22:56:04Z

← Older revision		Revision as of 22:56, 21 June 2011
Line 47:		Line 47:
	* ''drawing'' box		* ''drawing'' box
	* ''drawing'' button		* ''drawing'' button

			== Motivation ==

			Pivotal is a hosted, agile, free for public use, project management tool that just "gets out of your way." Unlike some heavier weight tools (say, BaseCamp) that include chat rooms, forums, and so forth, we decided to adopt a modular approach, one that both encourages an agile work flow, and who modularity mirrors OSE's hardware development efforts.

			Pivotal is based around the concept of tracking "user stories." User stories are high level requests by a stakeholder, written in plain English, that state who needs what, and why. A user story might be "OSE needs a way for team leaders to sort through all these people offering to help us so we can get the GVCS built ASAP! "

			After stakeholders create some user stories, team members can take ownership of the stories, and rate their difficulty on a relative scale. Stakeholders can prioritize user stories accordingly based on their difficulties. Pivotal takes care of estimating a team's capacity by observing how many tasks (of what difficulty) are performed per week, and automatically breaks the tasks into iterations and creates burn down charts, thereby giving project leaders an easy way to estimate how long a given project will take.

			Members can optionally break down user stories into finer grained user stories, or they can attach actionable tasks to it. There's also provisions to comment on them, attach files, and move user stories through a cycle of "Not Yet Scheduled, Started, Finished, Delivered, Accepted or Rejected, and Finished." Pivotal takes care of putting the user stories in the right place, and notifying the invested parties: the task requester (often the stakeholder), or the task owner (usually a team member), or everyone on the team (if the team member likes). It's simple, but great at what it does.

	[[Category: Organization]]		[[Category: Organization]]
	[[Category: IT Infrastructure]]		[[Category: IT Infrastructure]]

Elifarley: Added to :Category: IT Infrastructure

2011-06-20T13:08:12Z

Added to Category: IT Infrastructure

← Older revision		Revision as of 13:08, 20 June 2011
Line 49:		Line 49:

	[[Category: Organization]]		[[Category: Organization]]
			[[Category: IT Infrastructure]]

Elifarley: Wikification according to Wiki instructions#Sections

2011-06-20T13:06:56Z

Wikification according to Wiki instructions#Sections

← Older revision		Revision as of 13:06, 20 June 2011
Line 3:		Line 3:
	* Task - is specific. User story is more abstract, allows more flexibility to person doing the action. Point: specific is good. It allows direct results to be produced for the project. This limits contributions to significant ones only.		* Task - is specific. User story is more abstract, allows more flexibility to person doing the action. Point: specific is good. It allows direct results to be produced for the project. This limits contributions to significant ones only.

	= Abstract =		== Abstract ==

	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.
Line 13:		Line 13:
	* By invite only		* By invite only

	= Metalevel Description of Pivotal Functionality =		== Metalevel Description of Pivotal Functionality ==

	* Someone creates a project		* Someone creates a project
Line 30:		Line 30:
	To summarize: this tracker formalizes the basic human interaction pattern of creating shared promises - via request, offer, submission, and acceptance/rejection cycles.		To summarize: this tracker formalizes the basic human interaction pattern of creating shared promises - via request, offer, submission, and acceptance/rejection cycles.

	= Populating the Tracker with Tasks =		== Populating the Tracker with Tasks ==

	* Start with 32 steps of [[GVCS Development Template]]		* Start with 32 steps of [[GVCS Development Template]]
Line 38:		Line 38:
	* Use google map or cMap tools as a breakdown tool and indexical environment for each project.		* Use google map or cMap tools as a breakdown tool and indexical environment for each project.

	= Useful Tips =		== Useful Tips ==

	'''Use Labels'''		'''Use Labels'''

Syk0saje at 06:07, 2 June 2011

2011-06-02T06:07:32Z

← Older revision		Revision as of 06:07, 2 June 2011
Line 1:		Line 1:
	*User story - a request; who is requesting something and why		* User story - a request; who is requesting something and why
	*story - a deliverable; specific request		* story - a deliverable; specific request
	*Task - is specific. User story is more abstract, allows more flexibility to person doing the action. Point: specific is good. It allows direct results to be produced for the project. This limits contributions to significant ones only.		* Task - is specific. User story is more abstract, allows more flexibility to person doing the action. Point: specific is good. It allows direct results to be produced for the project. This limits contributions to significant ones only.

			= Abstract =
	=Abstract=

	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.
Line 10:		Line 9:
	Properties of Tracker:		Properties of Tracker:

	*Low entry barrier to participation		* Low entry barrier to participation
	*Infinite spawnability of new projects		* Infinite spawnability of new projects
	*By invite only		* By invite only

			= Metalevel Description of Pivotal Functionality =

	~~=Metalevel Description of Pivotal Functionality=~~		* Someone creates a project
			* 5-10 people per project - or too many people trying to work together; at best, small team, collocated, with high level of trust
	*Someone creates a project		* Task list is created (Icebox). These are the user stories or requests as defined above.
	*5-10 people per project - or too many people trying to work together; at best, small team, collocated, with high level of trust		* Someone takes on task, rates its difficulty on a relative scale, and then it can be started.
	*Task list is created (Icebox). These are the user stories or requests as defined above.		* Reasons for using a Tracker:
	*Someone takes on task, rates its difficulty on a relative scale, and then it can be started.		** Provides transparency:
	*Reasons for using a Tracker:		*** Tasks to be done
	**Provides transparency:		*** If anyone is doing a task
	***Tasks to be done		*** What the status is (not taken, in development, delivered, or complete
	***If anyone is doing a task		** Prioritizing all tasks (in backlog and initial task list)
	***What the status is (not taken, in development, delivered, or complete		** Estimation of time to completion (probably not so useful due to a large number of unknown, critical parameters)
	**Prioritizing all tasks (in backlog and initial task list)		** Allows stakeholder to make requests and rank them in importance, and allows team members to offer a deliverable on their own schedule; allows team team members' difficulty ratings to influence prioritization by stakeholder
	**Estimation of time to completion (probably not so useful due to a large number of unknown, critical parameters)
	**Allows stakeholder to make requests and rank them in importance, and allows team members to offer a deliverable on their own schedule; allows team team members' difficulty ratings to influence prioritization by stakeholder

	To summarize: this tracker formalizes the basic human interaction pattern of creating shared promises - via request, offer, submission, and acceptance/rejection cycles.		To summarize: this tracker formalizes the basic human interaction pattern of creating shared promises - via request, offer, submission, and acceptance/rejection cycles.

			= Populating the Tracker with Tasks =

	~~=Populating~~ the ~~Tracker with Tasks=~~		* Start with 32 steps of [[GVCS Development Template]]
			* Break down the 32 steps into substeps. This is the master index.
			* Import into pivotal tracker
			* Generate [[Systems Engineering Breakdown Map]]
			* Use google map or cMap tools as a breakdown tool and indexical environment for each project.

	*Start with 32 steps of [[GVCS Development Template]]		= Useful Tips =
	*Break down the 32 steps into substeps. This is the master index.
	*Import into pivotal tracker
	*Generate [[Systems Engineering Breakdown Map]]
	*Use google map or cMap tools as a breakdown tool and indexical environment for each project.


	=Useful Tips=

	'''Use Labels'''		'''Use Labels'''
Line 51:		Line 47:
	* ''drawing'' box		* ''drawing'' box
	* ''drawing'' button		* ''drawing'' button

			[[Category: Organization]]

Mjn at 11:35, 31 May 2011

2011-05-31T11:35:41Z

← Older revision		Revision as of 11:35, 31 May 2011
Line 2:		Line 2:
	*story - a deliverable; specific request		*story - a deliverable; specific request
	*Task - is specific. User story is more abstract, allows more flexibility to person doing the action. Point: specific is good. It allows direct results to be produced for the project. This limits contributions to significant ones only.		*Task - is specific. User story is more abstract, allows more flexibility to person doing the action. Point: specific is good. It allows direct results to be produced for the project. This limits contributions to significant ones only.


	=Abstract=		=Abstract=
Line 12:		Line 13:
	*Infinite spawnability of new projects		*Infinite spawnability of new projects
	*By invite only		*By invite only


	=Metalevel Description of Pivotal Functionality=		=Metalevel Description of Pivotal Functionality=

	*Someone creates a project		*Someone creates a project
	*5-10 people per project - or too many people trying to work together; at best, small team, collocated, with high level of trust		*5-10 people per project - or too many people trying to work together; at best, small team, collocated, with high level of trust
Line 28:		Line 31:

	To summarize: this tracker formalizes the basic human interaction pattern of creating shared promises - via request, offer, submission, and acceptance/rejection cycles.		To summarize: this tracker formalizes the basic human interaction pattern of creating shared promises - via request, offer, submission, and acceptance/rejection cycles.


	=Populating the Tracker with Tasks=		=Populating the Tracker with Tasks=
Line 36:		Line 40:
	*Generate [[Systems Engineering Breakdown Map]]		*Generate [[Systems Engineering Breakdown Map]]
	*Use google map or cMap tools as a breakdown tool and indexical environment for each project.		*Use google map or cMap tools as a breakdown tool and indexical environment for each project.


			=Useful Tips=

			'''Use Labels'''

			Create labels that represent sub-tasks. Say for example that your machine has three parts: base, box, and button. Naturally, each of these will need engineering drawings. Create the story with the name of the drawing and give it a label of "drawing". The titles of the stories will then appear as:

			* ''drawing'' base
			* ''drawing'' box
			* ''drawing'' button

Jiff64138 at 00:30, 31 May 2011

2011-05-31T00:30:32Z

← Older revision		Revision as of 00:30, 31 May 2011
Line 1:		Line 1:
	*User story - a request; who is requesting ~~somethind~~ and why		*User story - a request; who is requesting something and why
	*story - a deliverable; specific request		*story - a deliverable; specific request
	*Task - is specific. User story is more abstract, allows more flexibility to person doing the action. Point: specific is good. It allows direct results to be produced for the project. This limits contributions to significant ones only.		*Task - is specific. User story is more abstract, allows more flexibility to person doing the action. Point: specific is good. It allows direct results to be produced for the project. This limits contributions to significant ones only.

Vann miller: /* Abstract or User Story for Task Tracker */

2011-05-30T23:33:45Z

Abstract or User Story for Task Tracker

← Older revision		Revision as of 23:33, 30 May 2011
Line 3:		Line 3:
	*Task - is specific. User story is more abstract, allows more flexibility to person doing the action. Point: specific is good. It allows direct results to be produced for the project. This limits contributions to significant ones only.		*Task - is specific. User story is more abstract, allows more flexibility to person doing the action. Point: specific is good. It allows direct results to be produced for the project. This limits contributions to significant ones only.

	=Abstract ~~or User Story for Task Tracker~~=		=Abstract=

	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.

← Older revision		Revision as of 01:17, 28 March 2012
Line 62:		Line 62:

	==See Also==		==See Also==
			* [[Trello]]
	*[[Website]]		*[[Website]]
	*[[Bettermeans]]		*[[Bettermeans]]