JIRA: A great bridge between PM and R&D
August 20, 2019

JIRA: A great bridge between PM and R&D

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with JIRA Software

Our organization uses JIRA as a project management tool between our project management office, our product management team, and our research and development team to plan, coordinate, and deliver on product releases encompassing multiple initiatives, epics, features, users, stories, and tasks. Each team is responsible for various components of a release from inception to end-of-life.
  • Organization of features
  • Story development for R&D
  • Release candidate control
  • Ease of searching
  • Editing
  • Process flow of feature development
  • Acceptance Criteria development
  • Better organization for feature releases.
  • Linking to issues and enhancements has increased ROI from releases.
  • Customer satisfaction improved due to the adoption of continuous release model.
It is not the ideal user interface for managing information but that could be managed by your JIRA administrator. It does have a wonderful interface to other project management tools such as Aha, ProductPlan, etc. I would suggest that product management and R&D work closely with the administrator to ensure that the look and feel maps to the company processes.
The organization is very responsive to customer inquiries and provides standard templates to initiate set up. I would suggest working closely with their team to align your business, product management, and R&D processes. Once set up, the software runs effectively without much need for support calls or on-site visits.
We have used Microsoft Team Foundations Server in the past as a project management tool. It was well integrated with the R&D team through Visual Studio, but it was difficult to use a product management delivery tool. JIRA has natural integration with product management software which makes it easier to manage features on a per-release basis.
JIRA is well-suited for larger organizations that seek to have a controlled release process for releases. It is recommended for companies that utilize agile development methodologies in conjunction with a continuous release model. Companies only managing singular releases in a calendar year should avoid, as it is set up for multiple epics in a release, as opposed to a singular epic per release.