v.2.16 - Lead and Cycle time, Kanban Board on Program level
All the features described below appeared in TargetProcess v.2.16 (Sep-9)
TargetProcess v.2.16 requires .NET Framework 3.5. Please plan your upgrade accordingly.
Kanban Board on Program Level
Problems: "We are using Kanban process and have one team working on several projects. There is no single place to visualize flow in TargetProcess".
Solution: Provide Kanban Board area on Program level that includes stories and bugs from all projects.
Kanban Board on Program level shows stories and bugs from all projects inside a program. It gives you a possibility to manage one development team working on many projects in one place.
Lead and Cycle Time Report
Problem: When we are using Kanban, usual tracking charts do not provide any value. We are not using burn down charts and need a metric to track process.
Solution: Provide Lead and Cycle Time charts.
Lead time shows when user story in backlog may be released, while Cycle time shows when user story that is already planned may be released. These are key metricks in lean and quite clearly show development team dynamic. If lead and cycle time decreasing - development team is improving.
Iteration-less Development
Problem: "We do not use iterations and have to configure Kanban process manually. It is time consuming and iterations just take unnecessary space."
Solution: Provide default Kanban process and make an option to turn off Iterations.
Obviously, if you don't use iterations, you should have simpler user interface. Now you may turn off Iterative Development practice in a development process and all actions like Add Iteration, Iterations List, Plan Iterations, etc. will be removed from teh application.
To provide better Kanban support we've implemented some changes:
- Kanban process added into default installation
- Iterations can be switched off in process configuration
- Release Burn Down Chart can be drawn by weeks
- Daily Progress Report can be drawn for Release
- Task Board can be drawn for Release
Microsoft Team Foundation Server (TFS) Integration
Problem: We use TFS, but can't benefit from fancy TargetProcess source control integration.
Solution: Provide TFS integration plugin.
Other Improvements
Features
* Navigation: When user changes project, he stays in the same area
* JUnit integration
* Filter by Tags and Keywords in Release Plan
* When project is deleted, enable the user to delete the process associated with it by avoiding to have to go into the DB backend and delete it
* Filter by Role in Assign Team Members
* Tags for Task entity
* JIRA: Map all unmapped user to TargetProcess Default user
* Performance fix for plugins (Subversion, Bugzilla, all other).
* CSV export delimiter configuration
* User Story's Tab "Source" now shows task's commits
* User Story's Tab "Time" now shows task's time records
* Support for Bugzilla 3.4.1 added
Bug Fixes
#18716 User with no access can view 'People' using Custom Reports
#18551 Release's inner lists (bugs, stories) are not displayed if there is no iteration in release
#19328 Connecting to Jira getting SSL error
#17139 Custom Reports: Report fails with error about GetData
#18869 Image attachments are becoming corrupt
#19439 Change iteration to new release, but sub-entities are not updated
#19306 All reported time disappear from Time Sheet after delete process
#19592 Error when trying to change Request's parent project and assignment at the same time
#19587 entity.EntityState.Name - problem in Email integration when change state for any entity
#19507 Help Desk works incorect with Scope –> Company
#18901 Validation of custom fields values during bugs import from Bugzilla should be disabled
#19638 Entity lookup gives JS error in IE 7
#19608 Button label 'Submitting' doesn't fit the button width.