VSTS is a great tool - but just for development teams
November 12, 2018
VSTS is a great tool - but just for development teams
Score 7 out of 10
Vetted Review
Verified User
Overall Satisfaction with Microsoft Visual Studio Team System
It is being used and maintained by our engineering team for development work. Product management accesses VSTS to see project statuses and write user stories.
- Writing detailed use stories
- Assigning people to tasks
- Allowing for attachments
- It has nice tools for gathering data for reporting purposes.
- Having a more modern user interface which doesn't feel outdated.
- VSTS is very development team-centric. Development teams are working very closely with product management, who sets their tasks and priorities. There is no way in VSTS for product managers to develop product roadmaps based on product strategies and trickle that down to user stories for developers. The link between product management and development is missing.
- Tools like Estimably or something similar for pointing stories in an agile development setting would be very useful, as they are used daily by agile teams.
- More built-in visual reporting functionality that could be customized would be a huge asset.
- It has saved our development team a lot of time in organizing sprints and communicating within the team effectively.
We are moving away from VSTS to Version One since Version One has a better end to end workflow for a product based team (where product and development work very closely together and need to access the same data and communicate in an efficient manner.)