java.net: Wiki

The Source for Java Technology Collaboration


 <<O>>  Difference Topic XPlanner (2 - 03 Jun 2005 - Main.robogeek)
Line: 1 to 1
 
META TOPICPARENT name="ProjectManagementApps"
Home | Help | Changes | Index | Search | Go
<-- This creates the navigation links to :  Home | Help | Index | etc.  -->

XPlanner
<-- this automatically adds a header showing the name of this page -->

Changed:
<
<
XPlanner
XPlanner is a project planning and tracking tool for eXtreme Programming (XP) teams. If you are not familiar with XP software development practices, the links page contains pointers to relevant resources. To summarize the XP planning process, the customers pick the features to be added (user stories) to each development iteration (typically, one to three weeks in duration). The developers estimate the effort to complete the stories either at the story level or by decomposing the story into tasks and estimating those. Information about team development velocity from the previous iteration is used to estimate if the team can complete the stories proposed by the customer. If the team appears to be overcommitted, the set of stories are renegotiated with the customer. The XPlanner tool was created to support this process and address issues experienced in a long-term real-life XP project.
Homepage
>
>
See ProjectManagementApps
 
<-- put two horizontal ruled lines between article and discussion of it. -->


 <<O>>  Difference Topic XPlanner (1 - 03 Sep 2003 - Main.comforteagle)
Line: 1 to 1
Added:
>
>
META TOPICPARENT name="ProjectManagementApps"
Home | Help | Changes | Index | Search | Go
<-- This creates the navigation links to :  Home | Help | Index | etc.  -->

XPlanner
<-- this automatically adds a header showing the name of this page -->

XPlanner
XPlanner is a project planning and tracking tool for eXtreme Programming (XP) teams. If you are not familiar with XP software development practices, the links page contains pointers to relevant resources. To summarize the XP planning process, the customers pick the features to be added (user stories) to each development iteration (typically, one to three weeks in duration). The developers estimate the effort to complete the stories either at the story level or by decomposing the story into tasks and estimating those. Information about team development velocity from the previous iteration is used to estimate if the team can complete the stories proposed by the customer. If the team appears to be overcommitted, the set of stories are renegotiated with the customer. The XPlanner tool was created to support this process and address issues experienced in a long-term real-life XP project.
Homepage


<-- put two horizontal ruled lines between article and discussion of it. -->

<-- anchor to allow a link to the discussion about this article -->

Discussion about XPlanner
<-- generate a header for the discussion part of page -->


Topic XPlanner . { View | Diffs r2 < r1 | More }
 XML java.net RSS