Agile Software Development with JIRA and Confluence

1. AGILE SOFTWARE
DEVELOPMENTWITH JIRA &
CONFLUENCE
Anand Kumar

2. JIRA PROJECT / CONFLUENCE SPACE:
IMPLEMENTATION I
Create Groups (in Active Directory  Crowd)
ex. jira-SC-administrator
jira-SC-businessanalyst
jira-SC-users
confluence-SC-administrator
confluence-SC-users
Associate Users with Groups (in Active Directory  Crowd)
Create project (in JIRA)
Create space (in Confluence)
Associate Groups with Roles at the project level (in JIRA)
Associate Groups with Permissions at the space level (in Confluence)
 Project Name (Project Key)
ex. Sky Cities (SC)

3. JIRA PROJECT / CONFLUENCE SPACE:
IMPLEMENTATION II
(in JIRA)
Create Permission Scheme
ex. SC Permission Scheme
Create Notification Scheme
ex. SC Notification Scheme
Create Issue Type Scheme
ex. SC Issue Type Scheme
Create Issue Type(s)
ex. Risk
Change Request
Create Issue Type Screen Scheme
ex. SC Issue Type Screen Scheme
Create Screen Scheme(s)
ex. SC Risk Screen Scheme
SC Change Request Screen Scheme
Create Screen(s)
ex. SC Risk Screen
SC Change Request Screen
Create Workflow Scheme
ex. SC Workflow Scheme
Create Workflow(s)
ex. SC Risk Workflow
SC Change Request Workflow
Create Field Configuration Scheme
ex. SC Field Configuration Scheme
Create Field Configuration(s)
ex. SC Risk Field Configuration
SC Change Request Field Configuration
Associate all schemes with project

4. JIRA PROJECT / CONFLUENCE SPACE:
IMPLEMENTATION III
Agile Projects Waterfall Projects
Create Scrum Board (in JIRA Agile)
ex. Sky Cities – Scrum Board
Create Kanban Board (in JIRA Agile)
ex. Sky Cities – Kanban Board
Create Kanban Board (in JIRA Agile)
ex. Sky Cities – Kanban Board
Configure Scrum Board Filter (in JIRA Agile) to only show Bugs, Epics,
Stories, and Sub-tasks
Configure Kanban Board Work Sub-Filter (in JIRA Agile) to only show
Bugs, Tasks, and Sub-tasks
Configure Kanban Board Work Sub-Filter (in JIRA Agile) to only
show Bugs, Requirements, Tasks, and Sub-tasks
Create a hierarchy (in Structure) if necessary
Configure Columns, Swimlanes, Quick Filters, Card colors, Card layout (in JIRA Agile)
Add pre-sprint action items as Tasks (in JIRA Agile) in the Kanban
Board
Implement versions and components as needed (in JIRA)
Record Definition of Done (applies globally to all PBIs for a product)
(in Confluence)
Record Acceptance Criteria (per PBI) (in JIRA)
Implement project specific and program specific calendars (in Confluence Team Calendars)

5. JIRA PROJECT / CONFLUENCE SPACE:
IMPLEMENTATION IV
Conduct Sprint Planning Meeting
Record notes (in Confluence)
Select product backlog increments, break them down into sub-tasks and
commit to work (in JIRA)
Timebox: 2 week sprint = 4 hours
Conduct Daily Scrum
Record notes (in Confluence)
Timebox: 15 minutes
Conduct Backlog Refinement Meeting (Backlog Grooming / Backlog
Maintenance / Story Time)
Record notes (in Confluence)
Refine and re-order (in JIRA)
Conduct Sprint Review Meeting
Record notes (in Confluence)
Timebox: 2 week sprint = 2 hours
Conduct Sprint Retrospective Meeting
Record notes (in Confluence)

6. JIRA PROJECT / CONFLUENCE SPACE:
IMPLEMENTATIONV
Use the Clone Plus for JIRA plugin to clone to a different project and issue type during the clone operation.
Use the Clone Plus for JIRA plugin to customize clones (Clone to IT, Clone to QA, etc…)
Use the Structure plugin for JIRA to create structures to arrange issues in meaningful hierarchies of any depth
Use the Run Self-Service Reports for Confluence plugin along with Run CLI Actions in Confluence and Run CLI Actions in JIRA to automate
repetitive functionality in JIRA and Confluence