The integration of SwiftKanban with Team Foundation Server (TFS) ensures that the development and product management teams are in complete sync with each other. The development team has clear visibility into the business goals and needs and the product team has end-to-end insight into how each development assignment is progressing.
SwiftKanban TFS Integration Overview
In an Application Lifecycle Management (ALM) environment, the choice of systems and the collaboration between the cross-functional teams play a great role in delivering quality solutions. While the choice of systems impacts the productivity of a team, the cross-functional collaboration helps the teams get complete context of the business requirements. Best-of-breed systems such as SwiftKanban and TFS bring rich functionalities to the ecosystem.
By integrating SwiftKanban and TFS, the development teams will have real-time visibility into business requirements, and the product management teams will be able to trace all user stories and test cases associated with the requirement. As the overall collaboration in the ecosystem would increase, enterprises will deliver better quality products to customers at a faster pace.
How SwiftKanban – TFS integration is beneficial for an enterprise
- Powerful visual representation of the delivery ecosystem
- Trace the requirement breakdown completely – access the features, tasks, sub-tasks associated with a requirement
- Real-time updates into business goals & customer priorities
- Track the estimated and actual development efforts
With SwiftKanban + TFS integration, enterprises can:
How OpsHub Integration Manager integrates SwiftKanban and TFS
OpsHub Integration Manager integrates SwiftKanban and TFS bi-directionally. It ensures that all historical and current data is available to each user, in that user’s preferred system, with full context, in real-time. All ‘cards’ from ‘SwiftKanban automatically synchronize to TFS and all the entities in TFS associated with the ‘cards’ synchronize back to SwiftKanban.
Entities that can be synchronized between SwiftKanban and TFS
Use Case: SwiftKanban integration with TFS
Problem statement: Development team uses TFS for development work planning and project management team uses SwiftKanban for overall project planning. Both teams collaborate manually to exchange data and insights. This leads to miscommunication at multiple times.
Solution: When SwiftKanban and TFS are bi-directionally integrated using OpsHub Integration Manager, there is no scope for communication gaps or miscommunication between project management and development teams. The product management team, using SwiftKanban, can use the powerful visual representation ability of SwiftKanban to see how the development work is progressing.
- The Product Manager creates a user story card in SwiftKanban. The Product Manager, then, adds details such as priority, customer expectations (in description), and expected date of delivery.
- The card synchronizes to TFS as a product backlog item with all the specified details.
- The development team lead breaks down the backlog into multiple tasks and assigns the tasks to different developers within the team.
- The development team lead assigns a deadline for each task and defines the estimated effort hours for the tasks.
- The tasks synchronize to the corresponding user story card in SwiftKanban along with details such as estimated delivery dates. The Product Manager has complete visibility into the development team’s schedule from SwiftKanban itself.
- The development team starts work on the tasks and change the status of the task to ‘In Progress’ in TFS, the status of tasks within SwiftKanban changes as well.
- Once all the tasks are completed, the development team changes the status of the backlog to ‘completed’. The corresponding user story card in SwiftKanban also moves to the ‘completed’ column.
Benefits of integration for SwiftKanban and TFS users
- Traceability for business requirements throughout the ALM tool chain
- Visibility into the progress of development work
- No dependency on manual communication for making business decisions
- Complete context of the business requirements
- Real-time updates for any changes to the requirements or delivery timelines
- No manual efforts needed to keep product management teams updated on the development status