Jira Agile Management Tool – A Detailed, Complete, Easy and from Scratch Tutorial for Beginners
Agile Meaning
Agile simply means Quick.
What is Agile?
Agile is one of the different Software Development Life Cycle Models (i.e. SDLC Models) available in the market
Why Agile SDLC Model became popular in the market?
- Most of the Software projects use Agile SDLC Model for the below reasons:
-
These days most of the Application like Amazon, Flipkart etc. adapt to the changes in the market very quickly.Traditional SDLC Models won’t adapt to changes quickly and hence are not suitable for these days applications.Agile SDLC Model become popular in the market, for the medium and large sized Application which evolve over a period of time by quickly adapting to the market needs.
-
- Agile SDLC Model develops the Software over multiple iterations in an incremental manner
Agile Methodologies
Agile Scrum Methodology
Under Agile, Scrum Methodology is the number one in the market
Agile is not equal to Scrum
Agile Scrum Framework – Project Process
Scrum follows Agile principles and process
- Sprint
- Software is developed in iterations known as Sprint
- Software will be developed in an incremental manner with few set of requirements for every iteration
- Sprint duration is 1 to 4 weeks
- Ideal sprint duration is 2 weeks and is followed by most of the projects in real time
- Scrum Roles
- Product Owner
- Scrum Master
- Development Team
- Product Owner
- Knows the Business well
- Interacts with the customers
- Activities performed by Product Owner in the Project
- Creates Epics
- EPIC is a large requirement, which can be broken into smaller requirements known as User stories
- Example: View Here
- Creates User Stories
- User Stories are smaller requirements broken down from a larger Requirement known as Epic
- Example: View Here
- Maintains the Stories in Product Backlog and priorities them
- Created list of stories by Product Owner will reside in Product Backlog by default
- Creates a Sprint
- Create an Iteration known as Sprint for a duration which ranges from 1 to 4 weeks
- Sprint Planning Meeting
- Conducts Sprint Planning Meeting with Development Team
- Brings up the list of Prioritized Stories
- Estimates the stories with Development Team
- Story Point
- Development Team will estimate User stories roughly
-
- Fibonacci Series
- 0 1 1 2 3 5 8 ….
-
- Development Team will estimate User stories roughly
- Story Point
- Discusses and Finalizes stories that can be delivered by the Development Team in the Sprint
- Assigns the finalized stories to the Sprint Backlog
- Starts the Sprint
- Creates Epics
- Development Team
- Starts working on the User Stories assigned to the Sprint
- Scrum Board – View Here
- To Do
- In Progress
- Done
- Developers in the Team, perform the below activities for each and every User story added to the Sprint:
- Understand the Requirements to be developed
- Design the Requirements
- Code the Requirements
- Unit Testing and Integration Testing of Requirements
- Fix the bugs reported against the User Stories
- And others
- Testers in the Team, perform the below activities for each and every User story added to the Sprint:
- Understanding the Requirements for deriving the Testable Requirements
- Create Test Cases
- Execute Test Cases
- Re-test bugs which are stated as fixed by developers
- Perform other Testing activities like Automation, Testing Types etc.
- And others
- Scrum Master
- Monitors and drives the Development Team to finish their Sprint goals
- Conducts Daily Stand-up Meetings (i.e. Daily Scrum Meeting)
- Meeting lasts for 15 Minutes every day
- Development Team will attend this meeting and will be standing during this meeting
- Every team member will provide their current work status during the meeting
- What are we working now?
- What is blocking our work?
- What are our pending tasks?
- Will we be able to finish our work on time?
- Scrum Master Uses Burndown Chart to track the progress of the Development Team
- Burndown chart gives the clear picture of how much work is remaining in the Sprint
- Google search and check in Wikipedia about Burndown chart
- Sprint Review Meeting
- Developed and Tested Stories will be shown as Demo to the Product Owner
- Product Owner has to review and accept these stories
- Sprint Retrospective Meeting
- End of the sprint
- What went well?
- What went wrong?
- Improvements needed for next sprints
- Ceremonies
- Sprint Planning Meeting
- Daily Scrum Meeting
- Sprint Review Meeting
- Sprint Retrospective Meeting
Jira – Agile Management Tool
- Jira is an Agile Management Tool
- Automates the above explained Agile process
- Popularity of Jira Tool
- Survey Results – View Here
- By default, Jira doesn’t have the features for supporting Test Management
- Plug-ins like Zephyr or Xray needs to be installed
- Jira + Zephyr = Agile + Test Management
- Install and Configure Jira as Admin
- https://www.atlassian.com/software/jira
- Free Plan
- Create a Free account, skip things and select ‘Scrum’ project
- Select ‘Company Managed’ option
- Create Project
- Create different User roles in Jira
- Settings > User Management
- Invite different User roles say Product Owner, Developers and Testers
- Using the invitation, Create an Account and Login as Product Owner
- Select Backlog option in Jira
- Create Version
- Create Epic
- Use Excel file data for creating the Epic – View Here
- Click ‘Create’ button on the top to create User Stories
- Use Excel file data for creating the Stories – View Here
- Create Sprint
- Use ‘Create Sprint’ button in the Product Backlog page to create the sprint
- Specify the Sprint duration say 2 weeks
- As part of Sprint Planning Meeting,
- Product owner has updated the story points as per the estimations and Development Team has approved them
- As per the bandwidth and agreement with Development Team, Product owner has moved some stories from Product Backlog to Sprint Backlog
- Start Sprint
- Select Backlog option in Jira
-
-
-
- Product owner will start the sprint
-
-
- Using the invitation, Create an Account and login as Developer
- Select ‘Active Sprints
- Add Sub Tasks for one of the User Story
- Open the Story and add Sub Tasks to the Story
- Understand the Requirements to be developed
- Design the Requirements
- Code the Requirements
- Unit Testing and Integration Testing of Requirements
- Fix the bugs reported against the User Stories
- And others
- Open the Story and add Sub Tasks to the Story
- Using the invitation, Create an Account and login as Tester
- Select ‘Active Sprints
- Add Sub Tasks to the Story as Tester
- Open the Story and add Sub Tasks to the Story
- Understanding the Requirements for deriving the Testable Requirements
- Create Test Cases
- Execute Test Cases
- Re-test bugs which are stated as fixed by developers
- Perform other Testing activities like Automation, Testing Types etc.
- And others
- Open the Story and add Sub Tasks to the Story
- Working on the Tasks as Developers and Testers
- Moving the Tasks to the right side based on the progress
- As Admin, installing Zephyr plug-in from Apps
- As Tester,
- Create Test Cases
- Execute Test Cases
- Report the Defects
- As Developer.
- Fix the Defects
- As Tester,
- Retest the Defects and Assign back if still reproducing
- Retest the Defects and Close when fixed
- Development Team
- Demonstrate the completed Stories to Product Owner for Approval
- Check possible Test Reports
- Scrum Master
- Check Burndown chart
- And many more possibilities
By,
Arun Motoori
