No, is not the same.

Let me explain. Right now in Redmine you can create trackers
- which are just types of activities. This is fine.

You can create a new issue with a specific tracker and you
can specify the version, category, etc. Everything is
related to a project.

In XP meteorology, you have
- Project
- Iteration(version)
- Story (feature from user perspective - what the user
wants)
- Tasks - (Redmine = trackers)

Right now XPlanner doesn't support multiple task types,
actually it has some types, but is not flexible as in Redmine.

So basically, when you insert a task(tracker) you already
know the version and the feature(a group of functionalities
from the user perspective). When you have a bug related to a
feature you just add it to the right Story, and you can
track time spent to develop the feature and fix bugs(in case
of Redmine - you can split the time per trackers)

I'm not saying the current approach is not good. But I think
the XP approach is also a good one, even if you don't follow
all the rules.

And of course, it is easy to move features from version to
version, continue stories in the next version - if it didn't
make it on time for the current version and so on.

Thanks.
--------------------------------------------------------------------------------
You can create a 'Story' tracker in Redmine by going to:
'Admin -> Issue tracking -> Trackers' and click 'New
tracker'
(you need to log in as administrator).

After that, you can define workflows for this tracker in 'Admin
-> Issue tracking -> Wokflow'
--------------------------------------------------------------------------------
I'm not sure where to create a tracker 'Story' :)

Feature Requests is not the right place?
--------------------------------------------------------------------------------
Hi,

Couldn't you create a tracker called 'Story' and use issue relations
to group features, bugs inside stories ?
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
We're also using agile development and some features to manage iterations would be really nice. I created a custom field to store the name of the iteration that an issue was assigned to but we have multiple projects and there's no way to see all issues for a given iteration. What would be ideal is to be able to create an iteration, name it, give it a start and end date, and assign issues to it. Some basic reporting would make it even better - estimated hours, percent complete, and that sort of thing.
--------------------------------------------------------------------------------
Here are some specific changes in Redmine that would make it easier to use for Agile processes, without disrupting the many other ways that it can be used:

. The ability for each Redmine user to provide information on how many hours they will be available to work each day. One good way to do this might be to allow them to specify their working hours and days for a typical week, and then also allow them to edit the calendar for any one date (to deal with holidays and such).
. The ability to automatically calculate how many hours an issue will take, including dependencies.
. The ability to automatically calculate the end date of an issue, based on the start date, estimated hours remaining, the availability of the assigned developer, and also the end dates of any other issues that the issue in question depends on.

--------------------------------------------------------------------------------
Elliot Lee wrote:
> Here are some specific changes in Redmine that would make it easier to use for Agile processes, without disrupting the many other ways that it can be used:

And a few more ideas:

. A way to track the projected completion time of a set of issues over time. In other words, tracking how many hours were remaining to be done on a task at any point in time, and allowing that to be displayed on a nice chart of projected versus actual hours remaining (which in Agile land is called a burn-down chart).
. An easy way to re-order stories (err, issues :). Priority is not sufficient because it only has five levels of granularity. One could add a custom field called 'Sort order', but it's cumbersome to manually go in and edit this field on two issues when all one really one wants to do is swap their position.
. An easy way to wiki-link to the list, calendar, and gantt views for specific custom queries.
. A way to have queries display as a tree, which would be somewhat similar to list view, but also displaying the "children" of an issue (which would be the issues that 'block' or 'precede' the parents).

If you want more ideas, XPlanner looks interesting, and Rally Software (rallydev.com) has free demos of a system that is really nice for this. I guess it all depends how much time you care to invest in this area. :)
--------------------------------------------------------------------------------
XPlanner and Rally are specific software for managing agile prozesses. Redmine is not. But most of your ideas could be implemented in a plugin.
--------------------------------------------------------------------------------
Markus, you are correct, that Redmine is not Agile-specific. The problem with using XPlanner and Rally is that they lack all the great features of Redmine. They are only for Agile project management. Having one integrated system that can accommodate everything from source watching to issue tracking to wiki to project management would be so much more valuable than having four different software packages to do that. The idea of Redmine replacing some/most of XPlanner's and Rally's functionality is what's being suggested here and in issue #397.

It would be helpful to know which ideas could be implemented as plugins and which would require core redmine changes...
--------------------------------------------------------------------------------
Elliot Lee wrote:
> It would be helpful to know which ideas could be implemented as plugins and which would require core redmine changes...

Because of Ruby, I'm finding just about everything can be done in a plugin. Some are more difficult than others, but a lot can be done with the existing system.

--------------------------------------------------------------------------------