Agile Hive - SAFe in Jira vs. Jira Align

Daily activity management by using various kind of boards is very helpful to start the day with. Also, Backlog management is very good so it helps to keep track on the prioritized items. This can be used for all kind of Scrum activities by the Scrum master even for the Story management too. Also, it provides the required hierarchy levels, artifacts, boards, and workflows as an application in Jira. There is nothing to be shared as less appropriate while using SAFe.

Incentivized

This product is useful for a team/company working with multiple customers. Employee count anywhere larger than fifty or sixty will be benefited [from] this. Considering this product is expensive(as I’ve heard) this will not serve [many] purposes to smaller companies and startups who are having a very less customer base and [fewer...] employees.

• Team's progress.
• Risk Management.
• Visual representations - Dashboards.

Incentivized

• Jira is a great project management tool when it comes to tracking the progress of deliverables and milestones. Each member of the team can track individual deliverables and milestones. Jira comes with filters and search functions to perform these tasks.
• Jira is highly flexible when it comes to maintaining tasks and deliverable backlogs. You can plan and organize your sprints in such a way that you include your previous backlogs in them.

Incentivized

• it is not possible to plan if teams have different sprint length
• zoom into one sprint and then also zoom out to have big picture
• names of user stories are not good to read because of static big picture

Incentivized

• The initial ticket creation screen lacks some important features, such as assigning "point values" (a measure of effort needed for the ticket).
• The browser needs to be manually refreshed to see new tickets, which can make things confusing when several people in a meeting are simultaneously creating tickets.
• The interface on some smaller portions of the software are sometimes difficult to understand.

Incentivized

There is nothing that can be better than Jira but it needs to keep improving certain areas especially the attachment size area.

Incentivized

It has in general a good usability, but there are some downsides, the big picture view of the entire product increment is too static, so there is no zoom in or zoom out. Mostly throughout planning it is necessary to zoom in to a sprint level and manage the user stories there. Also, the pig picture view has some limitations, because you cannot read the entire user story name (boxes are too small).

Incentivized

Most of the things are easily manageable except certain things that are hidden and you need to ask teammates who are aware of how they can link attachements in the comment section and so on.

Incentivized

It is average. It needs to improve overall if you are paying the amount of money it costs. For now, it does the job, but with so many new features being added it would be very helpful to kick this up a notch.

Incentivized

With Jira Software alone it is also possible to plan a SAFe product increment planning, but it would be nearly impossible to see the overall big picture of all product teams involved in a release train. So, the planning on sprint level for one team would be more efficient, but the planning for a whole quarter with all dependencies across teams would be not feasible to present. Therefore, Agile SAFe enables value trains an efficient way to plan a product increment.

Incentivized

Atlassian JIRA Align (formerly AgileCraft) has an excellent suite of tools that integrate well with other tools and offers full support for various agile frameworks, including SAFe. It's just a complete integrated package, whereas some other tools seem to be lacking in different areas. Several plug-ins can be integrated to help with pro serv invoicing and integration with GitHub, Jenkins, Confluence, and other tools that we use.

Incentivized

• More transparency.
• Better product decisions.
• Saving time and resources.
• Less critical dependencies.

• Able to forecast & plan releases well using agilecraft leading to quality on time delivery.
• Distributed teams are able to collaborate well, be it be daily scrum, retrospective, estimation though this. Also team members love the gamification part & they have fun using this tool. Earlier we use to face challenges due to distributed teams but after AgileCraft, collaboration & communication was no longer a challenge & we are able to see improvement not only in team velocity, but also team satisfaction.
• Simplest tool to implement safe, scaling is always a problem with most of the agile tools but agilecraft helps in smoother implementation of safe practices & principles.

Incentivized