Lukas LandwehrIn mid-2019, we as toom IT started an agile transformation and we finally moved to the new organization in April 2020. While the transformation, I have taken responsibility for the roadmapping process, which should cover our cross-team (initially 13, now 15 teams) planning process. When we worked out the cross-team planning process, we decided to orientate on SAFe and the PI planning. While the simulations and the first real PI planning, we found out that JIRA is reaching its limit at various points and that we need a different or additional solution. After defining our requirements and creating a long and short list and an evaluation, we decided us for AgileHive. The right choice until today - we are very happy with Agile Hive. Base factors were to be able to visualize dependencies and to map hierarchies. The program (dependencies in ART / transparency about supplier services) and breakout board (planning the PI & coordination between teams) as well as the reports (quick overview of the most important SAFe metrics and the current status (“health”) of the PI) help us enormously in planning and managing the program increment. Really cool are many small useful features like the backlog visualization as well as the feature- and dependency-filter on the breakout-view, the automatically linking between stories and features by drag-and-drop, hints on program board & breakout overview (like “required issues are not in the current PI”) or the use of colors (for example for dependencies).
All in all easy to implement, easy to use and very helpful.
Was this review helpful?•