I’ve been using Redmine for some time, but while looking for a better way to manage “requirements” came across OpenProject.

I guess I would just define a Work Package type for Requirements.

However, in our workflow:

• Requirements do not get assigned to individuals
• A number of Requirements get mapped to a Feature that will address those requirements.
• Features get broken down into Work Items that get assigned to individuals

So, what is the best way to represent the relationship between “work Packages” e.g. Feature x implements Requirements a,b,c

Many Thanks

John

Hi John,

defining an separate work package type with a separate workflow is a good way for this. Here at OpenProject we use the the scrum methodology. We have the following entities implemented as types with different work flows:

Theme -> Epic -> User Story -> Task

The good thing about different typs is that you can easily filter for types in timelines. So you can easily get an overview of a high level roadmap.

We try to have an 1:n-entity. So an theme can have several epics, an epic can have several user stories and so on.

A number of Requirements get mapped to a Feature that will address those requirements.

I guess you can apply the same concept for other process models, e. g.:

Feature -> technical requirement -> task

Requirements do not get assigned to individuals

I know a lot of teams that use the attribute “responsible” to show this. The development lead or team lead is then responsible for a requirement, the developer for a feature. The “assigned to” attribute then shows who is currently working on the work package, e.g a reviewer, designer, tester etc.

Regards
Niels

Hi Niels

This looks very promising.

• Am I right in thinking I would use the “related to” relationship or would I use the w-p hierarchy?
• Is it possible to extend the list of relations?
• Is it possible to import a set of work packages from a CSV file?

Thanks again

Regards

John