Codehaus: Tag: agile

QixWeb

Sun, 20 Apr 2008 07:56:07 -0500

QixWeb has been tagged with agile

qixweb was born by refactoring a few XP projects from the ground up. Its essential elements are: 1. an abstraction of node, each representing a page in a browser; each node is attached to some piece of the domain, but the domain is kept separated and clean ==> nodes may be connected directly to each other or via commands, which constitutes an abstraction of navigation of the entire webapp 2. an abstraction of command as action that will change the domain, producing a new node ==> ie: these commands may be used to wrap easily Prevayler commands 3. an abstraction of browser, url and link that keep nodes & commands well separated in turn from servlets and container aspects ==> it is therefore possible to test all the dynamic navigation logic server side without working with html, http or containers 4. an abstraction of response handler and renderer that enables browser to use template engines like Velocity on one side and that opens the world of multichannel applications on the other side

agilifier

Mon, 19 Feb 2007 17:29:16 -0600

agilifier has been tagged with agile

Agilifier provides a means for structuring, running and publishing for Agile/XP projects that use Story based acceptance tests using FIT.

XPlanner

Tue, 23 Jan 2007 23:13:02 -0600

XPlanner has been tagged with agile

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.