Jira -Agile project management tool
JIRA: Jira was designed to manage End to End project implementation, Bug, and issue tracker. It uses Agile Methodology and provides Scrum and Kanban Boards that are highly customizable.
Scrum is one of the agile methodologies designed to guide teams in the iterative and incremental delivery of a product. In Scrum project management, the project team, led by the project manager, consists of a product owner, Scrum master, and other cross-functional team members.
The product owner is responsible for maximizing the value of the product, while the Scrum master is accountable for ensuring that the project team follows the Scrum methodology. The Scrum methodology is characterized by short phases or “sprints” when project work occurs. During sprint planning, the project team identifies a small part of the scope to be completed during the upcoming sprint, which is usually a two to four-week period of time.
At the end of the sprint, this work should be ready to be delivered to the client. Finally, the sprint ends with a sprint review and retrospective—or rather, lessons learned. This cycle is repeated throughout the project lifecycle until the entirety of the scope has been delivered.
Kanban is a type of Agile methodology that seeks to improve the project management process through workflow visualization using a tool called a Kanban board. A Kanban board is composed of columns that depict a specific stage in the project management process, with cards or sticky notes representing tasks placed in the appropriate stage. As the project progresses, the cards will move from column to column on the board until they are completed. The team collaborates with each other to improve the flow of work throughout the project.
Organizations will select which project methodology they need to achieve smooth project/product delivery. The JIRA dashboard consists of many useful functions and features which make handling issues easy.
Jira is used for Requirement Management, Test Case Management, Project Management, Product Management, Task Management, Bug Tracking
follow the Steps:
1)first create the project and add the team to access the project.
2)Board: then create epics and move those to the sprint
3)Backlog: team can move issues/stories once they started working on them, then move those to in progress. Once the work is done can move to the done state.
4)We can update directly in the Jira tool by raising the bugs or defects to create issues where we can prioritize the test case and comment as well.
We have daily standup calls and code reviews among the team using google meet /zoom meetings.
Sprint ceremonies(Agile Scrum): The main point we have to remember is every organization doesn’t have all these meetings.
Backlog Refinement: In Scrum, Backlog Refinement is an ongoing process in which the Product Owner and the Development Team collaborate to ensure that items on the Product Backlog:
are understood the same way by all involved (shared understanding),
have a size estimate for the (relative) complexity and effort of their implementation, and
are ordered according to their priority in terms of business value and effort required.
Backlog Refinement is about creating a shared understanding of what the Product will, and won’t, do, the effort, it will take to implement it, and the order in which you’ll do that.
2. What happens in the Grooming meeting?
Tech leads will assign the user stories and discuss who should work on what. The team must go through those user stories, Do an analysis. Business owners, testers, and developers will be in the grooming calls. The team will give user story points based on the user story. Tell the dependencies and ask doubts if any. If needed any info from business users, ask for docs.
3. What happens in a stand-up meeting?
Attendees: Scrum master, BA, Developers, Testers, Team Lead, and Architect may or may not attend the Standup meeting.
Scrum master opens Jira, asks for user stories, and asks each person what they have done daily. Do you have any blockers, or need any help, checking progress, and what is to be done the next day? When will you complete this work? How much time will it take to complete? The main idea of this status call is to know the team status of What they did yesterday, what they are doing today, and what they will do tomorrow.
4. What is a Core Hours session meeting:
The whole team will be collaborating and if we have any doubts like solution approach discussions we can discuss them. If there is a blocker, we can discuss it with the team members, try to find the approach to a solution, etc., and can work accordingly. We can get help too from them.
5. Retrospective session:
Every 15 days will have a Retrospective meeting. For each sprint scrum master and the entire team will discuss What went well, and what didn't go according to the plan. What needs to be improved for the next sprint? What better we can do?
Burndown charts: Once the sprint is completed, we can see accurate reports from reports like Burndown charts.
A burndown chart shows the amount of work that has been completed in an epic or sprint, and the total work remaining by the team members. It’s used to predict your team's completing their work in the time available.