The document describes an approvals workflow that involves multiple steps: 1. Issues such as change requests, improvements, and feature requests are created. 2. The requests go through stages of being opened, documented, analyzed for impact and risk, and reviewed by committees. 3. The workflow provides advantages like a standardized process, centralized knowledge capture, and easy tracking of all approvals linked to each issue.

1. Approvals Workflow
Issue Types:
Main Tasks: Sub-Tasks:
Change Request Requirements Gap
Create Issue
Improvement
Feature Request
Open
Document
Request
Reject
Clarification Return to Documentation
Analyze
Documentation
Impact
Reopen
Clarification Return to
Needed Documentation
Impact Analysis
Analyze
Reopen
Risks
Back to
Impact Analysis
Risk Analysis
Review
Request Further Review Rejected
Requested
Back to
Risk Analysis
Committee Reject
Ready for Request
Review
Review
Need Further
Waiting for
Information Approve Approved
Information
1

2. Approvals Workflow
• Workflow is used by multiple issues types that are Features, Change
Requests or Requirements Gaps that should be reviewed and approved prior
to work.
• Size of work is not the driving factor, approval of the work is key.
• The advantages to tracking “approval” activities are
– There is a standard process followed across the enterprise
– Knowledge capture is standardized and an integral part of the process, not an after
thought
– All approvals are discoverable and linked to the relevant issue and is stored in a
persistent centralized location.
• Change Requests: All Change Requests are captured and can be tracked
easily. JIRA enables quick and easy creation of Dashboards to create
comprehensive reporting on CRs’ statuses.
• Traceability and sign-offs for all related issue types are clear and
unambiguous.
2