Introduction
As a system admin or a project manager you often find yourself torn between management requirements and users who find the tools not as comfortable as they would like them to be. Jira is without a doubt a tool that can raise mixed emotions among users. Lucky for you, most of the users’ challenges can be easily handled.
In the Kanban Guide for Scrum Teams and the Professional Scrum with Kanban workshop, we introduce 4 key flow metrics that we believe Scrum teams
Jira Atlassian is a great ALM tool for managing your Agile environment. It provides a friendly work space for Agile teams and has some informative out-of-the-box reports that allow teams to easily apply root cause analysis.
At the program level, there are several easy ways to achieve aggregated data reports and epic progress boards. The relatively new Jira portfolio also has some interesting features that enable larger organizations to manage their program, including shared planning, shared releases, progress, and mitigation plans.
Visiting many organizations that use Jira as their main tool for their Agile environment, I decided to summarize 5 common pitfalls it is best to avoid.
Agile Testing/QA Reading List Engineering Higher Quality Through Agile Testing Practices The Agile Coach From Quality Assurance to Quality Assistance | Inside Atlassian No QA?
Request for additional information and prices