The document discusses implementing Agile software development using JIRA and CI/CD. It describes key Agile methodologies like Scrum and Kanban and compares them. It then explains what JIRA is and how it can be used to manage an Agile software development workflow, including concepts like projects, issues, tasks and sprints. It also covers setting up a CI/CD pipeline using Jenkins and git to enable continuous integration and delivery.

1. Implementation of
Agile SDLC with JIRA
and CI/CD

2. Why Agile

3. Agile S/w Development Process

4. What Agile solves

5. Benefits of Agile
Improved Quality
2. Focus on Business
Value
3. Focus on Users
4. Stakeholder
Engagement
5. Transparency
6. Early and
Predictable Delivery
7. Predictable Costs
and Schedule
8. Allows for Change

6. The key Agile methodologies are:
SCRUM EXTREME
PROGRAMMING OR
XP
CRYSTAL FEATURE DRIVEN
DEVELOPMENT OR
FDD
AGILE PROJECT
MANAGEMENT OR
APM
LEAN KANBAN OPENUP.

7. Scrum Vs Kanban
Scrum Kanban
Cadence
Regular fixed length
sprints (ie, 2 weeks)
Continuous flow
Release methodology
At the end of each
sprint
Continuous delivery
Roles
Product owner, scrum
master, development
team
No required roles
Key metrics Velocity
Lead time, cycle time,
WIP
Change philosophy
Teams should not make
changes during the
sprint.
Change can happen at
any time

8. What is JIRA?
JIRA lets you prioritize, assign, track, report and audit your ‘issues’, from
software bugs and helpdesk tickets to project tasks and change requests
More than just an issue tracker, JIRA is an extensible platform that you can
customize to match your business processes
JIRA improves productivity by cutting down on time wasted on tracking
issues and coordination
JIRA improves quality by ensuring all tasks are recorded down with all the
details and followed up till completion

9. S/w Development Workflow

10. JIRA Concepts: Projects, Issues & Subtasks
Akeles Consulting
BUG: A BUG IS A PROBLEM
WHICH IMPAIRS OR
PREVENTS THE FUNCTIONS
OF A PRODUCT.
EPIC: A BIG USER STORY
THAT NEEDS TO BE
BROKEN DOWN.
SUBTASK: A SUBTASK IS A
PIECE OF WORK THAT IS
REQUIRED TO COMPLETE A
TASK.
STORY: A USER STORY IS
THE SMALLEST UNIT OF
WORK THAT NEEDS TO BE
DONE.
TASK: A TASK REPRESENTS
WORK THAT NEEDS TO BE
DONE.

11. Getting started with JIRA Agile

12. Contd..
• JIRA Agile has two primary modes Scrum and
Kanban

13. Using JIRA Agile project templates

14. Create Agile Scrum Project
• Creating a new Scrum Project

15. Dashboard

16. Create Issue

17. Create Version

18. Backlog
• Backlog contains Epics, User stories…etc and
versions of a project

19. Ranking and prioritizing your issues

20. Planning sprints

21. Start sprint

22. Active Sprints

23. Completing a sprint

24. Reports

25. Testing in
JIRA
“JIRA IS THE IDEAL
ENVIRONMENT FOR TEST
MANAGEMENT”
... SO WHAT IS MISSING IN
JIRA ?

26. Contd..
TEST RELATED ARTIFACTS
(TESTS, EXECUTIONS,
PLANS)
VISIBILITY OF TESTING
RESULTS AND PROGRESS IN
AGILE BOARDS
REQUIREMENT COVERAGE
VISIBILITY
ADVANCED REPORTING FOR
GENERATING DOCUMENTS
AND DRILL-DOWN ON DATA

27. All for One and One for All
• A single project to manage your Requirements and
Defects,Test related issues and have all your Test
Executions.

28. Testing with Xray
Specify
• Test
• Pre-Condition
Organize
• Test Set
• Test Repository (v3.0)
• Test Plan
Plan
Execute
• Test Execution
• Sub-Test Execution
• Test Run

29. • Composed by a list of steps
• Each Step is defined by:
• Action/Step
• Data
• Expected Result
• InputAttachments
• Support for JIRA Wikimarkup
• Importing steps from
• Excel (using copy&paste)
• CSV
• JSON
• Other Test issues
Specifying “Manual Tests”

30. • Native support for Cucumber
• BDD – Specify tests in a business-readable
domain-specific language
• Test definition serves as documentation
• Automated test steps may be implemented in
Ruby, Java, .Net, etc
• Export specification and execute it during
Continuous Integration
Specifying “Automated Cucumber Tests”

31. Organizing Tests Cases
Flat, with “Test Sets”
A issue that represents a list of tests organized
by some logical way.
Hierarchical (v3.0)
For the “hierarchy/folder mindset”…

32. A “Test Plan” has the following goals:
• Specify which Test Cases will be
included in your testing goal (e.g.
the next release)
• Consolidating the latest execution
results for the Tests
Planning with “Test Plans”

33. A task for executing a group of tests on a given version and environment of the
system.
• Contains a list of tests and their results (i.e. test runs)
• Can be labeled, prioritized, assigned to testers and contain components, etc.
• May be created manually or during Continuous Integration
Executing with “Test Executions”

34. • Set Execution Result
• Create Defect issues
• Attach Evidences
• Add comments
• Check the Execution Activity Log
At the execution screen of a Test Run…

35. • Built-in reports
• JIRA gadgets in JIRAdashboards
• Agile boards
• Through other top-notch JIRA add-ons
Multiple ways of reporting

36. Why Devops?

37. CI/CD Process

38. Continuous Integration/Delivery Using Jenkins
and git

39. CI/CD Pipeline

40. Thank you
Thank you for your time and your interest