VersionOne Partner
VersionOne is recognized by agile practitioners as the leader in agile project management tools. By simplifying the planning and tracking of agile projects, we help teams deliver better software faster.
Methodologies Supported:
- Scrum
- Extreme Programming (XP)
- Crystal
- Dynamic Systems Development Method (DSDM)
- Feature-Driven Development (FDD)
- Lean Software Development
Version One Features
- Project Planning and Tracking
- Product planningRelease Planning
- Sprint Planning
- Tracking
- Review
- Test Management
- Acceptance Testing
- Regression Testing
- Collaboration
- Team
- Customer
- Reporting and Analytics
- Reporting
- Best Practice Dashboards
- Agile Report
- Test Status
Case Study: Children's Healthcare of Atlanta (CHOA)
- Project Work space was created in Version One for CHOA
- User Stories were added and related project documents ware uploaded into the work space.
- Members were added to the system like developers, testers, observer, customer, admin
- Effort and Resource allocations were updated by backlog items and their related tasks
- Project Start Dates and End dates were set
- Iterations and the iteration gaps were planned and created with start and end date for each iterations. Back log items were planned and their priorities were set and then backlog items were assigned to different iterations based on priorities.
- Back log items and tasks were assigned to developers. Member load was checked and wherever needed load redistribution was done.
- Every user has a Work page called “My Work Page” and all the tasks assigned to the logged in user is listed in the “My Work” page. The logged in user can change status of the tasks like from “in progress” to “Completed”.
- Testing team looked at the back log items and the tasks within the back log items for developing their test cases. All test cases were uploaded to the test board. This feature keeps all the test cases associated with the back log item in one place.
- Once the test team or end user started testing they logged the defects for each back log item. They could also update other changes needed per back log item, per tasks.
- This kept all the related items connected and traced very well. This is a “Requirement Traceability Matrix”, where all the changes, defects and issues will be having the relationship to the particular backlog item.
- Developers changed the status of the tasks on a daily bases and the project lead/manager updated the status of the backlog item and iterations.
- Based on all the data fed into Version One, we generated useful reports for the customer and developer.






