Dot voting is usually considered a decision-making tool, not an agile estimation technique. For example Dot Voting is preferred to select the most important 2-3 items during sprint retrospective. It’s a simple and effective way to prioritize or indicate the value of several small items quickly. When there is a relatively small set of items and […]
Dot Voting – Agile Estimation Method Read More »
The Bucket System Estimation technique is used when there is a very large number of items to be estimated with a medium to large group of people, and to do it quickly. This approach provides a consistent way for teams to size stories by discussing each story in terms of pre-defined complexity buckets before deciding
Bucket System – Agile Estimation Method Read More »
Agile teams need to estimate the size of their stories or product backlog items. The goal of the White Elephant Game is to get a quick estimate of the relative size of an agile project and the size of the individual stories before the project starts. It gives opportunity to everyone for their voices to be
White Elephant Sizing – Agile Estimation Method Read More »
You can create Jira Bulk Issue using a comma separated by value file (CSV). JIRA Bulk Issue import using CSV template is one of the key features of JIRA. This feature can be very useful when you have a large number of issues to create or when you need to import issues from an external
JIRA Bulk Issue creation using CSV Template Read More »
There are three categories (Agile Reports, Issue Analysis Reports & Forecast & Management Reports) of JIRA reports. Issue Analysis Reports can be further subdivided into the below-mentioned sub-categories. Average Age Report − Displays the average age in days of unresolved issues. Created Vs Resolved Issue Report − Display the number of issues created vs the number of
Issue Analysis Reports use in Agile Projects Read More »
Question: What are the types of reports generated in JIRA? Answer: In JIRA we can have multiple types of reports related to projects, versions, people, or other fields within issues. These are used to show the project statistics throughout the project life cycle. General reports for analyzing issues: Scrum Reports: Kanban Reports: Question: Explain the
JIRA Interview Questions & Answers Read More »
Jira delivers the relevant information in a convenient format called JIRA Reports. There are numerous reports available in JIRA, which enables you to gain visibility of the situation. In addition, these reports offer project statistics throughout the entire lifecycle. There are three categorized reports. Agile Reports Issue Analysis Reports Forecast & Management Reports Agile Reports
JIRA Reports use in tracking Agile Projects Read More »
Agile Scope Creep describes how a project’s requirements tend to grow over time, goals, or vision changes beyond what was originally agreed upon. Scope creep is frequently caused by changes in project requirements from key stakeholders (not properly defined requirements and additional features are added to an existing product), as well as internal miscommunication and conflicts.
Agile Scope Creep with Examples Read More »
Scrum adoption can be attributed to ADAPT- Awareness, Desire, Ability, Promotion, and Transfer. Each part of ADAPT cycle have a dedicated goal and tools to reach this goal. These activities not only helps in scrum but also helps in Agile values, or other Agile frameworks (like XP) can be improved, if there is a need
ADAPT – Scrum Adoption with Predictability and Flexibility Read More »
Kanban board provides transparency of work, team capacity, increases efficiency, and helps to visualization of work. Kanban means is a card or virtual signal. Kanban boards in Jira help teams visualize their workflow, limit work-in-progress, and maximize efficiency. Kanban is a method based on the continuous delivery of work, kanban board is designed to help
Kanban Board – Create & Customize for Kanban Team Read More »
JIRA Structure helps the team visualize, track and manage progress across JIRA projects. It lets you build hierarchical lists and share them with your team. A structure can contain issues, folders, and other items. There is no limit on the hierarchy depth, and you can bring together all types of issues from different projects. Epics:
JIRA Structure – Create & Manage Epics and Stories Read More »
A Power Interest Grid is a matrix used for categorizing or prioritizing stakeholders during a project to allow them to be effectively managed. Stakeholders are plotted on the grid in relation to the Power (Y-axis) & Interest (X-axis) they have in respect of the project. Charting the relationship between different stakeholders is the best way to
Power Interest Grid – Prioritize Stakeholders Read More »
Ishikawa diagram is a graphic technique, that is used for displaying the characteristics of a given situation or problem. It is also known as Fishbone Diagrams, Herringbone Diagrams, Cause-and-Effect Diagrams, or Fishikawa. Ishikawa diagrams are used for defect analysis (Root Cause Analysis). It is very useful when the analyzed defect has multiple causes. A problem
Ishikawa Diagram use in Root Cause Analysis Read More »
Tuckman Ladder Model is one of the models used to describe the process or different stages of team development. These four stages are “Forming, Storming, Norming, Performing, and Adjourning”. Important Points – Tuckman Ladder Model Usually, the stages occur in order. But teams can get stuck in a particular stage or regress to an earlier stage. Projects
Tuckman Ladder Model – Team Development Read More »
Agile Maturity Index is a way to know what the degree of maturity of the team is measured by applying some method, practice, or work technique, to know the level of mastery and the degree of adoption of Agile. It gives opportunities for improvement by challenging the team to implement the best-recommended behaviors to be
Agile Maturity Index & Agile Maturity Level Read More »
In Agile planning, there are many layers of planning involved, which gives the name “ Planning Onion ” to Agile planning. Agile does a lot more planning because it focuses more on frequent planning sessions instead of comprehensive planning that mitigates the risks of longer terms. The Planning Onion helps teams choose the right level of planning
Planning Onion – Levels of Agile Planning Read More »
Create a New Sprint – In JIRA, a Sprint is a defined time period in which a Scrum team commits to delivering a set of product backlog items. Sprints are used to organize and track the work of the development team, and to measure progress toward achieving the project’s goals. Create a New Sprint and
Create a New Sprint – Manage it in JIRA Read More »
Text Field search can be done using the quick search, basic search, and advanced search. Search Filters assist the team with creating views that you need to manage your issues. The text fields in JIRA can be searched for keywords or phrases. Text searches can be done in the advanced search when the CONTAINS (~) Tilda operator is used, e.g. summary~”windows*”. It
Text Field search using advanced search in JIRA Read More »
Stakeholder Engagement and Stakeholder Management are arguably the most important ingredients for successful project delivery. Stakeholders of a project are individuals, groups, or organizations that are affected or perceived to be affected either positively or negatively by a decision, activity, or outcome of a project. A stakeholder group can help it live out the pillars
Stakeholder Engagement & Management in Agile Read More »
Scrum Vs Kanban is about two different frameworks for implementing agile development. Kanban methodologies are continuous and more fluid, whereas scrum is based on short, structured work sprints. Scrum and Kanban are both iterative that rely on process flows and aim to reduce waste. Even though both are Agile but there are significant differences between
Scrum vs Kanban – Agile Methodologies Read More »
JIRA Scrum Board is a tool to help teams to achieve their goals and deliver the product in the scheduled/committed timelines. It is used to manage the sprint releases effectively. The word scrum is a very popular framework for the implementation of the agile software framework. Scrum supports projects that want to manage their issues
JIRA Scrum Board – Create & Customize Read More »
WSJF is a Prioritization method that helps calculate and understand what is the level of the financial impact of not finishing the task or implementing the solution sooner than later. a prioritization model used to sequence jobs (eg., Features, Capabilities, and Epics) to produce maximum economic benefit. At the end of the calculation of the
WSJF – Weighted Shortest Job First Prioritization Technique Read More »
Agile Estimation is the process of finding an approximation level of effort, which is a value that is usable for few purpose even if input data may be incomplete, uncertain, or unstable. Traditional waterfall method uses bottom up approach with the smallest tasks at the bottom. But agile uses two estimation techniques,Top-Down Estimation and Relative
Agile Estimation Techniques Read More »
EPIC JQL (Jira Query Language) lets you formulate search queries that exactly match your Jira configuration. Many JQL can show the issues in an epic, but none of them show subtasks and sometimes the team wants to get all issues and their subtasks belonging to a specific epic. To achieve this result you can use the
EPIC JQL to find included Issues and Subtasks Read More »
JIRA doesn’t have a direct “Sprint ID” field exposed in JQL (JIRA Query Language). In JIRA, the Sprint ID serves as a custom field utilized to associate all the issues encompassed within a Sprint. It proves valuable in mass-modifying issues, such as when setting a filter to isolate issues within a specific sprint in Jira.
Sprint ID for an Active or Closed Sprint Read More »
