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. Best practice of SCRUM team's organisation when one team may work in few projects

Best practice of SCRUM team's organisation when one team may work in few projects

Added by Алексей Баранов over 4 years ago

Hello!

What is the best practice of SCRUM teams organisation in OpenProject?

We have a tree of departments in single instance of OpenProject. One of it's node is Dev Department, which works by SCRUM. Dev Department has it's own child nodes, each of them is a Project (see tree below). First of all I would like to know is it corrct implementarion of Project's structure.

Projects:

  • Dep 1
  • Dep 2
  • DEV Dep
    • Project 1
    • Project 2
    • ...
    • Project N

Now if it is correcct, then we go next. We have a separate backlog (version "Backlog") for each project. Those backlogs contains features and bugs assigned to each project. Is it correct ?

Next have a problem. The problem appears when one team have namy projects. So each sprint contains user stories from separate backlogs. I couldn't find the way how to do this. I have found visibility options in Version's settings but could not understud how they work. On of the possible ways is to have Version "Sprint N" in DEV Dep, which could contain work packages from any child projects as below. Technicaly this is possible in OP, but backlog's view works unpredictable in this situation.

Projects:

  • Dep 1
  • Dep 2
  • DEV Dep - Version "Sprint 152"
    • Project 1 - Version "Backlog 1"
    • Project 2 - Version "Backlog 2"
    • ...
    • Project N - Version "Backlog N"

So it is very interesting to know the best practice of SCRUM team's organisation when one team may work in few projects in OpenProject.

Alexey


Loading...