Facile à utiliser et vous pouvez trouver exactement les bons chiffres pour découvrir dans quelle mesure le développement de votre produit est aligné.

As a developer, I like that I can easily see ongoing work from my team and from other teams. We have used Swarmia in our team bi-weekly to check our completed, ongoing and upcoming tasks for our team and for other teams working with us. We can track various areas of the development cycle, like how long reviews have taken, how long stories / PRs have been open etc. I have also liked that I can see deployments and especially if there has been rollbacks and seeing which PRs and stories were related to the failed deployments. It is pretty easy to configure your development cycle so that it works well with Swarmia. If you follow some good development practices, you probably don't need to do much. We had to change our review process a bit to get some good data to measure how long reviews take, but the new review process using github codeowners and github internal review assignment is actually much better and more standard way to assign reviews than our previous process. So using Swarmia made us to start using a better and more standard process for reviews. Feeling that using Swarmia gives always some new ideas what to improve. Like it can measure "Scope creep" metric to measure if you just keep adding more and more tasks to some task that you though was simple but turned out to be a huge task. Identifying these kind of stories seems really useful.

The feature I use the most is the "Pull Request" tab. It is helpful to avoid passing the pull request to your team by hand. They can see Prs pending to review when they want. The notifications in Slack are also appreciated.