Jim Intriglia

Renaissance Soul, Unleashed.

JIRA Core Business Requirements Gathering

The JIRA Core Best Practice Series

Business Requirements Gathering and Documentation

One key practice I use when developing a new JIRA Core Project to manage a business process is to treat gathering and documenting business requirements the same as if I were developing a software application.

After initial JIRA Core project kickoff and orientation meetings with business stakeholders have concluded, I’ll arrange a meeting with one or more business Subject Matter Experts (SME’s) with the goal of gathering critical requirements.

The majority of JIRA Projects that I’ve configured for business stakeholders involve managing some aspect of a business process. Some JIRA Projects manage and automate a small part of a large business process, while other JIRA Projects provide end-to-end business process management.

If the initial project planning, stakeholder orientation and requirements gathering steps are successfully executed, odds are favorable for a JIRA Core Project that will result in measurable and significant increases in speed, efficiency and productivity for the business process owners, managers and others that are engaged in the process.

When gathering and documenting business requirements that will drive a JIRA Core Project configuration, I keep the following key goals and objectives in mind:

  • Produce the minimum number of document deliverables that capture critical client needs and requirements.
     
  • JIRA Core Project Design specifications should focus on providing a JIRA Administrator with critical data needed to configure a Project.
     
  • JIRA Core Requirements, design and development specifications should be useable as resources for end-user training development.

Using a Visual Approach to Documenting Business Requirements

It’s been said that a picture is worth a thousand words, so with that in mind I developed a visual diagram that captures most of the critical JIRA Project configuration that a JIRA Project Administrator will need.

A JIRA Workflow diagram is a view of the business process that will be managed by a JIRA Project. A completed workflow diagram communicates the following JIRA Core Project configurations that will be needed by a JIRA Administrator:

  • Workflow order and sequencing of steps

  • Workflow Steps, Transitions and Status information

  • User groups and roles

  • Process steps Administrator notes

  • Transition permissioning and configuration rules

  • Notification event configuration

  • Input and display screen configuration

As you can see, quite a lot of configuration information is captured in a single workflow diagram.

Couple a completed JIRA Workflow Diagram with an Excel spreadsheet that contains data element information for screen and report configuration, a JIRA Administrator has most of what they need to configure a Project for the first review by business stakeholders.

JIRA Workflow Diagrams can be constructed using Microsoft’s Visio application software. An excellent alternative to Visio is Lucid Software’s LucidChart web application.

Your questions, comments and suggestions drive future updates to this article. Please leave your comments below, or submit by email.

 

 

 

 

 

 

 

Show Support for my work now!