InfoQ

InfoQ

InfoQ

En | 中文 | 日本語 | Br

562,907 Jan unique visitors

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

VersionOne announces V1: Team Edition

Posted by Mike Bria on May 26, 2008

Sections
Process & Practices,
Development
Topics
Agile ,
Artifacts & Tools
Tags
Products ,
VersionOneSoftware
VersionOne recently launched V1: Agile Team, a lightweight application that gives smaller projects or teams new to agile software development a way to get started with planning and tracking Agile projects. With V1: Agile Team a single team has the capability to manage their product and sprint backlogs, get interactive "taskboards" and "testboards" for day to day development activities, view progress of activities through various reports and burn graphs, and more.

Among these capabilities, users of V1: Agile Team can:
  • Quickly import stories and defects from a spreadsheet and manage a consolidated product backlog
  • Easily plan and prioritize stories via simple multi-item drag and drop functionality
  • Efficiently plan multiple releases and sprints via an electric whiteboard interface
  • Visually track releases and sprints through an interactive Taskboard, Testboard and Daily Scrum dashboard
  • Automatically generate key Agile metrics such as Burndown, Velocity, Estimate trends (Burnup) and Cumulative Flow Reports for releases and sprints
Robert Holler, founder and CEO of VersionOne, has this to say:
Today many software development teams rely on spreadsheets, bug trackers, emails and homegrown time-tracking tools to manage Agile development projects. These tools can be cumbersome and time consuming, particularly when trying to consolidate and share project status information with remote team members and stakeholders.

Our goal with V1: Agile Team is to provide customers a quicker, easier and more powerful way to plan and track a software development project. Now small teams have an efficient and cost-effective way to instantly gain visibility into their agile projects.
V1: Agile Team is extensible via a developer API/SDK and has free support for many third-party development tools such as Subversion, CruiseControl, Bugzilla, FitNesse, and others. For a limited time V1: Agile Team is available for free for an unlimited number of users. See the VersionOne site for more info including an online demonstration or to request an on-demand or on-site copy of V1: Agile Team.
  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.