This is the instructions and script file for the JUnit Jazz demo.

Sample Demo Script 
================================================================================

A. Team structure

* team invitation

* Team is explicitly modeled
  o project roles
  o team and contributor awareness everywhere
* Each team can have its custom process
* Team first + team central
  o team aware filtering
  o RSS feeds per team (select team area in project area explorer> Subscribe to Team Events)
  o contributor hover shows team areas

B. Planning

* 2 focus areas in planning, team and individual

* Iteration planning
  o pick up items from the back log
  o markup&model to create work items
  o refinements assign work items
* My Work
  o Personal work planning
  o Team commitments

  o Web UI

C. Bug Work

* Team activity, non coding related team communications
  o Responding to new work items, triaging, querying, reports

D. Developing

* Builds are very important
  o review the build history, the current state
  o show the areas and ant scripts, there is no magic
  o personal builds, control over builds by all team members instead of only the releng person. More control == faster delivery
    since there is no waiting for releng anymore. 

* Stream and repository workspace concepts 
  o project/team/stream/repo workspace/component/change set
  o Give control to users - repository workspaces, private versioning	

* team based chats
	
* Fixing a bug reported against a specific build
  o team central shows a blocker bug in a 0.2 bucket
  o start work, will be asked to suspend current work
  o finding the build from the work item, see what changes were in it. compare builds.
  o create a repository workspace for it from the snapshot
  o accept changes from the make changes (show wi integration into workflow)
  o fix the bug
     o Edit the following files:
	    FailureDetailView.java
	    AdvancedTests.java
	 o add a file:
  	    junit.textui.WikiResultsPrinter.java
	 o setup a private build
	 o deliver when green
	 o create a bug fix stream for this work using flow browser, then integrate the fix into the mainline		
	 o show the link history in the work item

* Growing the team
  o Split streaming using the flow editor (add a level, split components)
  o Expand the team structure and create different levels of integration.
  o Maintenance can happen in another development line with it's own process and team members
		
E. Stabilize: The end-game
  
  o Change the milestone
    * Process becomes more tight
    * enable additional process rules
          o only component lead can assign a work item to a milestone
          o deliveries require a code review
                + approvers queries for reviews, performs review and approves

F. Web UI
   o Work Item, Planning, Reports

// NOT IMPLEMENTED YET
G. Where to publish build results on the web for customers to access
   o Currently this is a manual process
   o Web UI home page, static pages, linked into jazz web ui

