Well in my current war to get my company to use TFS , I am loosing the battle for Visual Studio Team System adoption. I have fought many battles, against Jira, Confluence and Subversion, but they are currently wining. I cant seam to get the Architecture & Strategy guys to get behind the project. They are sitting on the sidelines encouraging me, but with no active participation.
Time and again I am running up against the problem that no one will read any of the content that I have provided. It is difficult to fight a battle on many fronts and the fact that Visual Studio 2005 Team Foundation Server is such an excellent product with complete integration between all of its services is actually not working in its favor.
Others are able to concentrate on selling Jira to one group of people while others are concentrating on selling Subversion. I have to lobby them all…
The call has now come down from on high to have all Risks and Issues stored in Jira. This will cripple the effectiveness of my arguments as the best arguments for the business revolve around Work Item Tracking, as they don’t really care if the developers can link their source code to tasks, or test results to Releases or even bugs to Change Requests.
Thus, I have created a CodePlex project for TFS Work Item Tracking to Jira Synchronization in the hopes that some enterprising developers would be interested in working on the code. I will not have time to work directly on the code as all development projects are now being outsourced to our Indian development team or to external companies, and I have been relegated to the bench of release management documentation…
Technorati Tags: Fail ALM TFS VS 2005
What to read next
Software Development Industrial Revolution
Explores how industrialising software development with tools like Team Foundation Server boosts speed, collaboration, and scalability in …
Deploying Team Server
Discusses the challenges, costs, and benefits of implementing Team Foundation Server (TFS) for large development teams in a corporate …
Microsoft's internal uptake of Team Foundation Server
Microsoft widely adopted Team Foundation Server internally, with 21 instances supporting 734 projects and 5,600 users, driving rapid product …
Branch madness!
Describes a complex source control issue in TFS involving branch mismanagement, its impact on merging, and step-by-step actions taken to …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …