Here is an example of the statistic release plan and progress which is used within each iteration (0,1,2,3,4,5,6) to define the priorities of the stories within one iteration. It also lists the start and end date of a story, the number of tasks and the time spent on it. The estimates for the stories are taken over from the release planning. (The values are purely imaginativ. They were written before we had any experience about realistic values.)

The statistics stories per iteration, tracking (number of stories) and tracking (brick-values) can be generated from this statistic.

	explain the rows and last column explain when to fill in which value

- - - snip - - - 8< - - - - - - - - - - - - - - - - - - - - - - - -

	Jira	Name	started	closed	#tasks original	#tasks actual	∑ time original	∑ time actual
	(critical)	assured stories
01	JIRA:CV-47	Smell Detector for “Circular Dependency”	10.09.04	14.09.04	1	1	03:00	04:30	3
02	JIRA:CV-55	Metrics Performance Considerations	-???-	-???-					2		☼
03	JIRA:CV-49	Metric CBO (Coupling between Objects)	13.09.04	13.09.04	1	1	02:00	01:30	2
04	JIRA:CV-59	Metrics DIT, NORM, SIX, NOC, NOD	13.09.04	14.09.04	1	1	03:00	01:35	3
05	JIRA:CV-71	Spike: Calculate Metrics on builder thread	14.09.04	15.09.04	1	1	04:00	04:30	3
06	JIRA:CV-72	Showing description of the metric	14.09.04	14.09.04	1	1	01:30	01:15	1	Ø
07	JIRA:CV-61	Detector for Test Smell “For Testers Only”	14.09.04	14.09.04	1	1	02:00	02:40	2
08	JIRA:CV-73	Simple Test Coverage for Prolog	17.09.04	17.09.04	1	1	01:30	00:51	2	Ø
09	JIRA:CV-74	Detect if TestCases are named *Test	15.09.04	15.09.04	1	1	02:00	01:00	2		☼
10	JIRA:CV-75	Detect if Getters have no side-effect	15.09.04	16.09.04	1	2	04:40	05:20	5		☼
	(minor)	surplus stories
11	JIRA:CV-86	Don't freeze the GUI while calculating metrics	15.09.04	15.09.04	1	1	01:00	01:00	2		☼
12	JIRA:CV-89	Guide me to the smelly locations, Click→Jump	16.09.04	16.09.04	2	2	03:00	03:40	3		☼
13	JIRA:CV-62	Smell Detector for “Long Method”							1
14	JIRA:CV-63	Smell Detector for “Long Parameter List”							2		☼
14	JIRA:CV-76	Detector for our Prolog conventions							2
16	JIRA:CV-77	Detector for our Java conventions							2
17		TreeView for Measured Values							5	Ø
18		Metrics Reuse Ratio, Specialization Ratio							1
		…
	(trivial)	deferred stories
30		Halstead Metric							2	Ø
31		Smell Detector for “Temporary Field”							3
32		Refactoring “Split Temp”, Simple related Detector							8	Ø

Note: hangover from previous iteration are the following stories: Jingle, Small Bell, Whistle

- - - snap - - - >8 - - - - - - - - - - - - - - - - - - - - - - - -

Kurzerklärung der Felder (verbessern + übersetzen + verschieben)

<erste Spalte>:Laufende Nummer, die die Priorität angibt.

StoryKnackiger Name für die Storyh/nhangover,newa/s/dasured,surplus,deferredtasksAnzahl der Tasks zur Story&#8721; est.timeSumme der für die einzelnen Tasks geschätzen Zeiten&#8721; act.timeSumme der für die einzelnen Tasks verwendeten ZeitenbricksDurchschnitt der geschätzten Steinchen (max. 2 Nachkommastellen)stormProzentsatz der Entwickler, die einen schlechteren Verlauf für nicht unwahrscheinlich haltensunshineProzentsatz der Entwickler, die einen besseren Verlauf für nicht unwahrscheinlich halten

ES FEHLT NOCH: Eine Statusspalte

ZUORDNUNG VON Jira Konzepten und dieser Tabelle

Definition, welche Infos wo gepflegt werden. Um Duplikation zu reduzieren.