since Jira do not provide safe support, Version one has been chosen among other tools such as AgileCraft & rally.
Version one supports safe i.e Strategic
themes, budgeting, WSJF prioritization, PI planning, roadmaps, safe metrics, continuous delivery etc.
Also VersionOne can support any configuration of SAFe & it is pretty easy to configure.
At team level we use it for release planning, sprint
planning, test management & active collaboration since teams were distributed.
Team rooms & planning rooms were very helpful to keep team focused & track progress.
- For Distributed teams, collaboration is the biggest concern. So in Version one there is awesome feature for collaboration, called ‘Conversations’ which can be used by teams to discuss work and ideas. It helps in keeping all stakeholders at same page & enhances transparency.
- To track forward & backward dependencies, it has feature called Visualization which lets you trace all project activities through multiple levels to see how stories are related and can help you in identifying blocking issues/impediments.
- Integrates well with GitHub so whenever new build is triggered, the build version is updated to the story on Version One. So its keeps everyone updated & no need to send mails/release notes after the deployments.
- It provides good support for continuous improvement, the basic requirement for scrum teams as it has feature called “Ideas" - an idea submission and voting platform for team members.
- I also found the goal page very useful, here you can list the goals for the team & leadership and track which goals are completed & which are in progress.
- The team room feature offer a place to see team backlog, a storyboard for the current sprint & task board for the current sprint. This feature is there in AgileCraft s well & I found it very useful.
- For sizing the stories, it includes the mini-game 'Estimably' which helps teams estimate stories anonymously. Anonymously is the key here.
- Tracking team progress is easy using Sprint Tracking feature & Task board. Sprint Tracking shows the total estimates, capacity, completed hours, etc. & Task board shows which story is done, in progress & not started.
- Set up is a little complicated when compared to other tools.
- Version one comes with lot of features like Rally but here we don’t get customization which is there in Jira, where from workflow to issue everything can be customized based on your team/program/portfolio requirements.
- I found it bit slow specifically when a particular story has test, documents tagged/attached to it.
- Lot of navigation to access basic stuff. Example: if I want to go to bug attachment , there are lot of clicks & navigation need to do which should be pretty straightforward I feel.
- Test Management need improvement in terms of tracking tests, team had hard time tracking regression test cases.
- Support desk is not good , if contacted they will confuse you more, better google the thing you want to do rather than connecting with support desk.
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
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.
- VersionOne makes it easy to create stories and move them across teams, as needed.
- VersionOne's team view gives the team a clear view of the work to be done, work in progress, and work completed. This is particularly useful to have as a visual aid in stand ups or during reviews.
- VersionOne allows the team to track capacity and work for each story which is useful to determining if the story is still on track.
- Saving of changes is inconsistent. Sometimes the changes appear to save automatically and other times the user needs to click the "Apply" button. Until the user is familiar with when this needs to happen, work can easily be lost.
- This may be a setup configuration issue, but it would be good to be able to set the default team when creating stories. Too often stories are created and the user forgets to enter the team and they need to search the entire database for the story that was just created.
- Assigning backlogs is simple once you're in a project. The ability to add backlogs in line is helpful when you just want to list out new backlogs before adding your user stories.
- The ability to sort by different types of data, so that you only view exactly what you want to see is very helpful, especially during sprint planning meetings.
- The customizability of the app enables the user to adjust certain criteria based on their team's needs. For example, adjusting sprint length.
- As a whole, Version One is not user-friendly. Without an intense familiarity of the app, it's often difficult to find things you're looking for. Given the complex reality of the customizability, I'm not sure if there's a way to make the interface simpler.
- I would like the ability to add attachments and imbedded images more simply within user stories. Sometimes, It'd be helpful to have the ability to add a screenshot of a page at specific points within your user story.
- From the Version One homepage, there is no clear CTA for users to login.
- Storyboard view
- Ability to customize fields in backlogs and defects
- Ease of learning the tool
- VersionOne speed is not the best and is not consistent
- The Search function could be better, it returns a TON of clutter
- Test case management is poor, to the point where no one here recommends VersionOne for test
- No drag and drop capability for attachments
- Text editor has real problems, limited formatting, balky pasting of images
It's not good at all for test case management. It's just not built for software test. Although from some perspectives, it is beneficial to have tests embedded in the work item.
In Aaron's installation, teams could not customize V1 storyboards and items - changes were all or nothing for the site, so it's not suited to team-by-team customization.
- The reporting functionality is great. VersionOne allows you to create custom reports as needed, including burn down charts for work completed to ensure that deadlines are met.
- Visibility to project work is fantastic. I can see what everyone is working on in the sprint. The team visibility helps keep everyone focused and on task.
- Tracking issues is really easy. I can see which stories are challenging and help manage problems and issues brought up from our testing team as soon as they're discovered.
- This is built for Agile work. Traditional waterfall projects don't really fit well with VersionOne.
- There are some features I don't use, such as Mind Maps, web conferencing, and messaging features. We already have platforms that perform these tasks. If I didn't however already have solutions for these features, I would have no problem using them.
- There is a learning curve when using VersionOne. At first it can be difficult figuring out how it works, but you can find tutorials, etc., online to help.
- Helped in retrospection and comprehensive agile management
- Better visibility of tasks breakdown and innovations
- Reporting and analytics and portfolio management
- Need better UI for the scrum board
- More privacy using individualistic accounts
- Integration with mobile app for on-the-go tracking
- Helps with management of projects
- Helps with dependency management
- Allows stats tracking
- VersionOne is not a very flexible tool to recode. When engineers want to integrate pull requests, this is a hard task.
- This tool also has stats tracking limitations. Project managers should be able to track as little or as much as they would like without having to use VersionOne and another tool, such as an Excel spreadsheet, to get the job done.
Good: VersionOne allows teams to keep track of the status of their work. It also allows for the management of granual level project tasks.
Not so good: Engineers like to customize tools to suit their particular needs, VersionOne does not allow a great deal of customization.
VersionOne Scorecard Summary
VersionOne Technical Details