Get the Most Out of Your Team Foundation Server Implementation
Organizations with .net development practices use Team Foundation Server (TFS) for source code management. TFS could be the heart of your Agile and DevOps practices if you used all the features you are paying for.
Microsoft’s marketing team must have been playing buzzword bingo when they rebranded the cloud version of Team Foundation Server (TFS) to Azure DevOps. Despite that, TFS and Azure DevOps are robust tools.
Product and development teams often only adopt a fraction of the extensive feature list that includes a configurable, seamless integration of product backlog, Agile team and work management, source code control, reporting, Kanban boards, continuous delivery, build and release, and much more. If you own TFS you should review the full feature set of TFS/Azure DevOps as soon as possible to see what you are missing!
Our Take
The Agile Manifesto may have declared that we should value individuals and interactions over processes and tools. Note that this is not instead of tools. An integrated application delivery tool chain can be a catalyst for building an Agile, DevOps, and Product practice. You need to automate, but only as part of a whole transformation including culture, learning, integrated teams, metrics, and governance.
Want to Know More?
- Info-Tech’s Implement Agile Practices That Work, Structure Your DevOps Adoption Using a Metrics-Driven Approach, and Transition to Product Delivery have information and exercises to help you define the artifacts and workflows you will automate with TFS.
- Explore Seven Reasons You Need a Data-Driven Approach to Application Lifecycle Management.
- Learn more about Microsoft Team Foundation Server (TFS) on SoftwareReviews.
