“Oh no, it’s the retrospective time!”
This cry for help is not uncommon, I’m afraid, among practitioners of Scrum. That is a shame. For me, this meeting is the climax of the scrum framework – this is the place where we get better. The discussions can get very deep and very meaningful. I would like to show here how to move from the statement appearing in the title of this paragraph to “Oh boy, it’s the retrospective time!”.
Introduction Atlassian is in the process of making some big changes to its products for the past year. It started with the acquiring of Agile
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.
I’d like to share with you some tips and tricks of setting a scrum board I usually share with my clients. The bottom line is that too many tools have too many features that support old ways of thinking. Let’s look at the various items one by one
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.
Request for additional information and prices
