The BA is able to maintain Leverforce as a system of record for the requirements approved during the project initiation while carrying out all scrum tasks using the development team´s JIRA Software instance.
JIRA is the most popular ALM tool and in our practice is the option we recommend to collaborate with development teams in Agile contexts.
The Leverforce integration supports the following features:
Create Epics: Use Cases drafted in Leverforce can be replicated automatically as epics in JIRA software
Create Stories: Stories drafted in Leverforce can be replicated automatically as stories in JIRA software.
Trace Requirements: Each JIRA story created maintains a synchronized description of the associated requirements in Leverforce and a link to its Leverforce record.
Maintain Hierarchy: The hierarchy between Use Cases and Stories in Leverforce is also synchronized in JIRA epics and stories
Synchronize JIRA progress: Changes in status, start date, due date and story points that are carried out in JIRA stories and epics are synchronized back in the related Leverforce use case and story records
Below is a list of Business Analysis activities and how we use JIRA software to carry them out during a Scrum:
Validate Requirements (BABOK® 7.3)
JIRA Story: Verify end-to-end traceability of solution components to project goals
Define Design Options (BABOK® 7.5)
JIRA Story: Collaborate with the development team and plan the solution components for a JIRA story (Story Mapping)
Maintain Requirements (BABOK® 5.2)
JIRA Story: Refine JIRA stories to retain or increase requirement accuracy and consistency throughout the scrum
Prioritize Requirements (BABOK® 5.3)
JIRA Story: Rank stories in the order of relative importance to the project stakeholder to facilitate sprint planning
Assess Requirements Change (BABOK® 5.4)
JIRA Story: Collaborate with development team in evaluating the implications of proposed changes to requirements associated to a user story
Approve Requirements (BABOK® 5.5)
JIRA Story: Formalize agreement on and approval of a JIRA story for solution construction to proceed.
Assess Solution Limitations (BABOK® 6.3)
JIRA Story: Review requirements allocated to a JIRA story to assess the performance of the implemented solution and accept the delivery.