Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

General discussion
  1. OpenProject
  2. Forums
  3. General discussion
  4. Requirements Tracking

Requirements Tracking

Added by John Parker about 11 years ago

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


Replies (2)

RE: Requirements Tracking - Added by Niels Lindenthal about 11 years ago

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

RE: Requirements Tracking - Added by John Parker about 11 years ago

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

  • (1 - 2/2)
Loading...