trac 4 eXtreme Programming?

[buildup@…]

Hi.

Trac is a very good software. I use it for my personal and professional development… the integration whit subversion is wonderfull. Many thanks.

I have some interesting idea to extend trac. My idea is adding eXtreme Programming feature like as: iteration, backlog, story, task and release. This 5 concept are the core of a very good and powerfull agile metodogy. Backlog and release are feature of Scrumm metodology, but is quite simple use and integrate these whit the other eXtreme Programming feature.

The Story are the must important part of the metodology. It is a simple use case and represent an atomic, easy to test, functionality required from user (client or committer).

The Task are a developer activity required to complete a story. For each story there are some task to do complete. When all task is complete the story is complete too.

The Iteration is a collection of funcitionality sorted by priority the must be implemented until a specified date. For each iteration there are some Story. When all story of an iteration is complete, the iteration is complete too.

The Release is a collection of iteration. Is it quite as Milestone or conventional Major release. For each iteration there are some iteration. When all iteartion is complete, the Release is complete too.

Backlog is a user' sandbox. The user (client or customer) write directly his Story. During the planning game, the lead developer help user to select some Story from Backlog, and insert these in a new iteration.

Story and Task could have wikibased functionality, so user, developer, can write their requirement, software specification, coding standard, ecc…

It is possible adding this feature to trac?

I'm a discrete python programmer, can I help you to extend trac for adding eXtreme Programmin metodology feature? Can you help me to extend trac for adding eXtreme Programmin metodology feature?

References

​http://www.xprogramming.com

​http://www.extremeprogramming.com

Many thanks for your attention. See you.

buildup

[Christian Boos]

You can already use TicketTypes to get something close.

However, there are a few forthcoming features that would be quite useful for implementing the complete use case you describe, in particular have a look at the discussion in ticket #886 (ticket dependency and parent/child relationships):

• The Backlog would be the pool of Story tickets not assigned to any Release.
• A Release would correspond to a milestone.
• An Iteration ticket would be a toplevel ticket, assigned to a milestone
• A Story ticket would be a child of an Iteration
• A Task Ticket would be a child of a Story