Scenarios where it works well:
1) Retros can be very well facilitated & notes/action items
can be captured against the sprint.
2) Product Owner can effectively track the story
progress with all the test-cases, design etc.
3) Being good scaling support, it provides good visibility
across multiple teams, programs and agile portfolios, providing a centralized
environment where all our stakeholders can easily work together regardless of location.
4) It provides easy tracking all of your epics,
stories, themes, defects, tasks, tests and issues
5) I like its intuitive UI as for moving stories
around, burning hours.
6) It allows top leadership to visualize
and report their strategic plans, giving all stakeholders the relevant data
that they need to stay dedicated to the project priorities.
7) It can be easily integrated with slack
so for few teams we used slack for collaboration
Scenarios where it did not work well:
1) Test Management need improvement in
terms of tracking tests, team had hard time tracking regression test cases.
2) Version one comes with lot of features like
Rally but here we don’t get customizations which is there in Jira where from workflow
to issue everything can be customized based on your team/program/portfolio
requirements.
3) Lot of navigation to access basic
stuff. Example I want to go to bug attachment , there are lt of clicks &
navigation need to do which should be pretty straightforward I feel.
