Skip to main content
Enterprise Agile Planning icon with arrows

This post is from the CollabNet VersionOne blog and has not been updated since the original publish date.

Last Updated Mar 17, 2011 — Enterprise Agile Planning expert

Doctor doctor, give me the news, I gotta bad case of loving you!

Enterprise Agile Planning

I’ll admit it, I’m in love with Project Workspaces. It’s just what the doctor ordered when it comes to customizing VersionOne to match each team’s unique process and workflow.

I work in Marketing and we’ve been practicing scrum for almost 3 years. During this time we’ve been using VersionOne (surprise, surprise, right?) to manage our work. It’s been great using the same tool as our development team. The challenge is, we’ve had to use their project and workspace-specific configurations. The status values they set up within the tool for their stories and tasks include “Ready for Dev”, “Ready for Test” and “Accepting”. These values definitely make sense for a development team, but don’t make as much sense for our marketing team. We use “Design”, “Review” and “Delivered” for our statuses. The standard workflow they set up in the tool is very streamlined and makes a lot of sense for developers, but our workflow has a few extra steps that didn’t exist in the tool. They also have a lot of fields in their stories, most of which we’ve never used.

In the past, we’ve always had to say to new team members, “just use ‘Ready for Dev” for “Design,” or “oh, that stage really means this to us,” and “ignore the extra fields on a story, we don’t use them”. Enter Project Workspaces! Now our workspace, across all of our projects, matches the way we work. The status values match those we use in Marketing and there’s no more translating for new team members. Being able to turn off a lot of unused fields also makes our story view more concise. With the ability to customize the tool and the terminology to match the way we work, our team now uses the tool a lot more, I suppose it’s because it now feels familiar to us.

If you have multiple teams with different workflows and methodologies, check out VersionOne’s Project Workspaces. Workspaces are disabled by default, so ask your system administrator to enable the feature, then go to Admin > Display Fields > Project Workspace Assets. From there, you too will fall in love with Project Workspaces. The great news is that the changes are real-time and can easily be reversed, so it’s easy to try different configurations to see what works for your team.

What’s more, “management” won’t have to log in to multiple tools just to see the status of the different team’s projects. With customized workspaces roll-up reports still work across teams.

The post Doctor doctor, give me the news, I gotta bad case of loving you! appeared first on VersionOne Blog.

More from the Blog

View more Government Cloud
Apr 12, 2022 Government Cloud receives FedRAMP Authorization through sponsorship from the United States Department of Veterans Affairs

Enterprise Agile Planning
Flagship Agility solutions can effectively scale agile deve ...
Read More
Nov 22, 2021

What are the qualities of highly effective agile teams?

Enterprise Agile Planning
A team is the core unit of productivity in an agile organization. Wher ...
Read More
Nov 15, 2021

How an open-first attitude revolutionized government tech development

Enterprise Agile Planning
Public perception of government is often that it is slow-moving, reluc ...
Read More
cross functional
Nov 08, 2021

6 best practices for building resilient cross-functional teams

Enterprise Agile Planning
Agile frameworks prize the quality of resilience within every facet of ...
Read More
Contact Us