Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • 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
    • Professional 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?
      Create a new account

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
  • Roadmap
  • Work packages
  • Calendars
  • Team planners
  • Boards
  • Forums
  • Wiki
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showDeveloper
        • Hierarchy leafAccessibility Checklist
        • Hierarchy leafCode Review Guidelines
        • Expanded. Click to collapseCollapsed. Click to showContribution
          • Hierarchy leafGit Workflow
          • Hierarchy leafTranslations
        • Expanded. Click to collapseCollapsed. Click to showDeveloping Plugins
          • Hierarchy leafDeveloping an OmniAuth Authentication Plugin
        • Hierarchy leafRelease Process
        • Hierarchy leafReport a bug
        • Hierarchy leafSecurity
        • Hierarchy leafSetting up an OpenLDAP server for testing
        • Hierarchy leafTheme Features
      • Hierarchy leafDownload
      • Expanded. Click to collapseCollapsed. Click to showFeature tour
        • Hierarchy leafRelease Notes OpenProject 30
        • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 30 - Overview
          • Hierarchy leafGlossary
          • Hierarchy leafRelease Notes - Accessibility
          • Hierarchy leafRelease Notes - Accessibility changes
          • Hierarchy leafRelease Notes - Add work package queries as menu items to sidebar
          • Hierarchy leafRelease Notes - Copy projects based on Templates
          • Hierarchy leafRelease Notes - Design changes
          • Hierarchy leafRelease Notes - Fixed Bugs
          • Hierarchy leafRelease Notes - Keyboard Shortcuts
          • Hierarchy leafRelease Notes - Project settings
          • Hierarchy leafRelease Notes - Ruby&Rails Update
          • Hierarchy leafRelease Notes - Security
          • Hierarchy leafRelease Notes - Timelines
          • Hierarchy leafRelease Notes - Work packages
      • Hierarchy leafHowto create animated gifs
      • Hierarchy leafMigration Squashing
      • Hierarchy leafMod security
      • Hierarchy leafNew work package page
      • Hierarchy leafOP3 to OP4 Debian upgrade
      • Hierarchy leafOP4 Ubuntu1404 Stable with MySQL in production
      • Hierarchy leafOpenProject 40 Development Setup
      • Expanded. Click to collapseCollapsed. Click to showOpenProject Foundation
        • Hierarchy leafBoards
        • Hierarchy leafMembers
        • Hierarchy leafOPF-Meetings
        • Hierarchy leafStatutes
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes
        • Hierarchy leafOpenProject released on Bitnami
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 40 - Overview
        • Hierarchy leafRelease Notes OpenProject 40 - Accessibility improvements
        • Hierarchy leafRelease Notes OpenProject 40 - Column header functions in work package table
        • Hierarchy leafRelease Notes OpenProject 40 - Improved Design
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated query title on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated toolbar on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - OmniAuth integration for OpenProject
        • Hierarchy leafRelease Notes OpenProject 40 - Work package details pane
      • Expanded. Click to collapseCollapsed. Click to showSecurity and privacy
        • Hierarchy leafFAQ
      • Expanded. Click to collapseCollapsed. Click to showSupport
        • Expanded. Click to collapseCollapsed. Click to showDownload and Installation
          • Hierarchy leafInstallation MacOS
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 3 0
            • Hierarchy leafDebian Stable with MySQL in production
            • Hierarchy leafInstallation Ubuntu
            • Hierarchy leafInstallation Windows
            • Hierarchy leafInstallation on Centos 65 x64 with Apache and PostgreSQL 93
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 40
            • Hierarchy leafOP4 Debian Stable with MySQL in production
          • Expanded. Click to collapseCollapsed. Click to showMigration paths
            • Hierarchy leafFrom Chilliproject to OpenProject
            • Hierarchy leafMigration 15 to 30
            • Hierarchy leafMigration 24 to 30
            • Hierarchy leafMigration Redmine 2x › OpenProject 30
            • Hierarchy leafOpenProject 3 Migration
          • Hierarchy leafOpenProject 40
        • Expanded. Click to collapseCollapsed. Click to showNews
          • Hierarchy leafNew OpenProject Translations Plugin
          • Hierarchy leafNew Plugin on OpenProjectorg Local Avatars
          • Hierarchy leafNew design for OpenProject
          • Hierarchy leafNews Accessibility workshop for OpenProject
          • Hierarchy leafNews Glossary for OpenProject
          • Hierarchy leafNews Heartbleed fixed
          • Hierarchy leafNews Icon Fonts
          • Hierarchy leafNews OpenProject 30 Release
          • Hierarchy leafNews Release GitHub Integration Plugin
          • Hierarchy leafNews Success Story Deutsche Telekom
          • Hierarchy leafNews Timelines
          • Hierarchy leafOpenProject 3013 released
          • Hierarchy leafOpenProject 3017 released
          • Hierarchy leafOpenProject 40 released
          • Hierarchy leafOpenProject 40 will be coming soon
          • Hierarchy leafOpenProject 405 released
          • Hierarchy leafOpenProject and pkgrio
          • Hierarchy leafOpenProject news moved to a new blog
          • Hierarchy leafOpenProjectBitnami
          • Hierarchy leafPackager version with plugins released ("Community edition")
          • Hierarchy leafRegistration OpenProject-Foundation
          • Hierarchy leafRelease OpenProject AuthPlugins
          • Hierarchy leafUpdates on OpenProject
          • Hierarchy leafWe need your feedback for the the new fullscreen view for work packages
        • Hierarchy leafOpenProject Plug-Ins
      • Hierarchy leafWiki
You are here:
  • Forums
  • Development

Content

Requirements Tracing through Agile Boards

Added by Sebastian Siegert almost 2 years ago

Hi all,

I am currently evaluating how to best modernize our aged project management and development tool suite. I have in the past implemented a full scale CI/CD pipeline, starting with Jira for user stories / tasks, tracing into code and eventual K8S deployment. However this was a small and detached project in which I had full control and few formal project management requirements.
Now we are starting a huge project with formal requirements, long term project plans and (I fear) several roaring waterfalls involved. I still want to be as modern and agile with this project as possible so I'd like to have the formal processes in the waterfall as connected to each other as possible. We will keep our requirements in IBM Rational DOORS (because history) and I've stumbled across the ConnectAll Universal Adapter (https://www.connectall.com/integration/universal-adapter/) to connect Jira with DOORS. 
So far we are using Microsoft Project for formal PM but we want to switch to OpenProject Enterprise. Now the question is: can we use the OpenProject API to extend ConnectAll in order to create Subtasks in OP Boards and link them to work packages? In theory this should work but maybe there are some caveats that I do not see right now. 
The workflow would look like this:

  • The PMs create their formal (waterfall) project plan with OpenProject
  • The Lead Requirements Engineer evaluates customer requirements and stores them in DOORS
  • ConnectAll adapter fetches the requirements and adds them to a product backlog
  • The Lead Systems Engineer (that would be me) roughly assigns these tasks to work packages
  • The Scrum Team(s) will take these tasks, add those that are not formal requirements and takes them into sprints
  • At the end of the sprint, completed tasks are set to done, the PMs can see that things happen to their work packages
  • ConnectAll adapter modifies the requirements and sets their status to "implemented" or whatever

Am I missing something? Does that make sense at all? I'm curious for your ideas.

Regards
Sebastian


Replies (3)

RE: Requirements Tracing through Agile Boards - Added by Sebastian Siegert almost 2 years ago

Well, the community is not really active, is it? Do I already need enterprise support to ask questions or dicuss ideas?

RE: Requirements Tracing through Agile Boards - Added by Jens Ulferts almost 2 years ago

I don't know (other than having skimmed over their page) and haven't used ConnectAll. But generally speaking, your scenario should work if there is a system in between that translates between the integrated systems. Then the problem probably boils down to:

  • Authentication & Authorization: OpenProject supports API keys as well as oauth and one can set the permissions as desired.
  • Which system triggers a change: OpenProject can be polled on the API or it can also be told to call a webhook  
  • Conflict resolution: This is probably the hardest as the right resolution is in part dependent on the scenarios the integration is used in. Here, I don't know what ConnectAll will offer and what you want to achieve e.g. if a work package is in an unexpected state.

 But generally speaking, such an integration should work.

RE: Requirements Tracing through Agile Boards - Added by Sebastian Siegert almost 2 years ago

Hi Jens, 
thank you for the answers. I've been in contact with the ConnectAll sales team and will have a demo next weeks. The adapter is REST-based and offers a UI-based configuration for the API. According to the company they take care of conflict resolution so I hope that won't be a problem.

What I'm asking myself is whether it's possible to import requirements as subtasks into the backlog of agile boards. We would basically have to fuse requirements and work packages in the middle, coming from the top and the bottom. Is there any way to test that? I'm thinking about hosting an OpenProject instance, creating a basic project plan with some work packages and then use someting like postman to call the API directly. Would that work? If I can make API calls with postman and create tasks that way, the manual fusing (or attaching, to be more precise) should be a piece of cake (although a very large one if we have hundreds of requirements).

Thank you for your support.

Regards
Sebastian

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