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
    • 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
  • Feature tour
    Feature tour

Content

You are here:
  1. Forums
  2. Support Installation & Updates

Work Package Types Hierarchy

Added by Zorin Wiseputra over 10 years ago

AFAIK, there are several Work Package Types on OP

Task

Deliverable

Milestone

Phase

Bug

Feature

I’m curious of which one is on top of the other? Since when I create a subtask, I realize that even a Task can have a Milestone or a Phase as a subtask. This seems irrelevant.

On top of that, what is the role of a sprint? Since when I put one, I didn’t see it on Timeline.

I need more enlightenment on this subject. Such as the explanation of what each work package types mean.

Bona Fide,


Replies (1)

RE: Work Package Types Hierarchy - Added by Brendan Dunn about 10 years ago

Hi

It is all up to you and the project mgt technique you use.
Standard practice uses tasks and milestones,
agile methods can use feature, deliverable, bug or phase.
It is up to you. Make up your own :)

If you work in a organization that runs very specific projects such as product develeopment, you can create very specific work packages.
e.g.

instead of setting up generic tasks, if you “always” have a process to “define the colour” and it has several steps, make a new wp type
called “define colour” and then under that type define the steps. Your plan is a little clearer then. The business can read it more easily.

If you always follow the same process for requirements definition as per the BABOK….go for it, make a new type.

cheers
Brendan

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