Wiki
	· Home · 2.0 Release · 2.0 Beta 1 · 2.0 Alpha 4 · 2.0 Alpha 2 · 2.0 Alpha 1 · Development · Direction · Status edit menu

	Main
	· About · Documentation · Publications · Download · HOWTO · FAQ · Discussion Area (Wiki) · Status · Contact

	Projects
	· VR Juggler · Gadgeteer · VPR · Sonix · JCCL · Tweek · PyJuggler · VRJ.NET

	Events
	· SIGGRAPH 2004 BoF? · SIGGRAPH 2003 BoF? · Virtual Reality Course · IEEE VR 2003 Course · SC 2002 Exhibit

	Site Search

	Sponsors
	· Infiscape · VRAC · Iowa State University · SourceForge

	Link To Us

XP tracking introduction

This page explains the way XP projects are tracked in these pages

Layout

There is a hierarchy of information here:

• Web - the TWiki web for XP tracking. One web can be used to track multiple projects.
• Project - the project being worked on for a Product. Usually this will be the next major release. Each project has a page, which contains an auto-generated summary of the project progress.
• Team - Each project has one or more teams, groups of developers that work on one aspect of the project. Each team has a page which contains an auto-generated summary of the team's progress.
• Iteration - a project is divided into a series of short (usually 2-4 week) iterations. Each iteration has a page, the contents of which are also auto-generated.
• Story - An iteration comprises a number of stories. Stories are pieces of related functionality that are owned by a lead developer but can be worked on by more than one developer. The story page contains information on the acceptance criteria, and also a list of tasks.
• Tasks - these are the atomic units of work. A story is usually broken up into a number of tasks. No task should take more than 3 days to complete. Tasks may be shared among more than one developer. Tasks details are entered on the story page.

Information is only entered for Stories and their associated tasks. Information for all other levels in the hierarchy is automatically generated (once the pages are initialised)