VersionOne will help coordinate your Scrum teams across multiple sites
August 19, 2016
VersionOne will help coordinate your Scrum teams across multiple sites
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with VersionOne
VersionOne is what our teams use track stories and plan our sprints across over 25 sprint teams in multiple locations including Seattle, WA, San Francisco, CA, San Jose, CA, Ottawa, Canada, and Bucharest, Romania. Using VersionOne we are able to plan and coordinate to deliver our complex solution to our customers.
- 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.
- The ramp up took a lot of man hours, but once we all learned it, I think it went much more smoothly. I think roll out has a big impact on this. If a team had set this up with Epics and rolled it out to the teams to fold our stories into it instead of everyone figuring it all out at the same time, it would have been less headache for all of the team members and less time and money spent. I don't have specific numbers since I am not part of that side of the business.
- On the positive side, this did allow all our teams to coordinate better in one organizing tool. It doesn't work as well for teams who work better with Kanban, but it still allows visibility across all the teams.
JIRA appears to be more extensible with the ability for Scrum, Kanban, bug/incident tracking, and the ability to customize dashboards. However, VersionOne's performance over the same teams is extremely fast in comparison and therefore allows users to be more productive over the same amount of time.