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 24, 2011 — Enterprise Agile Planning expert

Teams Without Fuss

Enterprise Agile Planning
"Teams" Feature Discussion, Take 1...
(Fade in to training session, where a group of happy new VersionOne users are learning more about what their system can do for them.)New customer: "Where do we define the people on the team?"
VersionOne Expert: "Well, you don't have to."
New customer: Odd pause while displaying a quizzical look. Followed by, "...What do you mean?"
The above scenario plays out every so often with our customer/facing product experts. How can you have an agile development team without administering who is on the team? It's a natural enough question especially for those who spend more time than they'd like in a world of administrivia ("any time at all" is often sufficient to place one into that category). When designing the Teams feature, we made a conscious effort to minimize the amount of administration needed. What helps in understanding it is a slight change in the mental model. When you think of the VersionOne Teams feature, think of it as...a team room.[caption id="attachment_576" align="alignright" width="228" caption="Team Room"]Team Room Door[/caption] To create a Team, an administrator just defines the name of the room. That's all they have to do. Whoever doles out the backlog (typically product owners, scrum masters or team members) can then put backlog for the team into that room. Team members walk into the room (by setting the Team filter on their tracking page) to view, estimate, schedule, sign up for and work on that backlog. That's all they have to do. Stakeholders can see what's going on in the room by setting the Team filter on their report. That's all they have to do. The system doesn't act like a corporate hall monitor shouting, "Mr. Lee, you need to be in the Bluebird room right now". Mr. Lee knows he's part of the Bluebird Team and just goes on in to the Bluebird Team room to work with his team. Heck, with the way the system works, Mr. Lee only needs to specify that he's a Bluebird once and the system will automatically guide him back to the Bluebird room whenever he's ready to work. The Agile team's final score: Getting Things Done 1, Administrivia 0.

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