Providing Developers with Early Visibility into Requirements

Pattern name: Dev Requirements Visibility

About this Pattern

Organizations that develop very complex products in heavily regulated industries use Requirements Management tools like Jama, IBM DOORS NG and Polarion ALM for their product requirements.

The development teams that need to implement those requirements would prefer to have them flow into their Agile planning tools automatically as epics or features, in tools like Jira, CA Agile Central or TargetProcess. Then, these artifacts can be broken down into user stories, maintaining the relationship to the parent epic and its associated requirement for traceability.

Integration Pattern Providing Developers with Early Visibility into Requirements


  • Both parties benefit from a seamless flow of work from the planning teams to product management teams.  

  • In addition, as work progresses, updates flow back upstream providing the portfolio managers with visibility on execution and completion against the plan

Artifacts Typically Synchronized


Implementation Artifacts

  • Requirements

  • User stories

  • Epics

  • Features

  • Stories

Example of this Pattern