In Aggreko we use a product called Heat ITSM to manage our support calls. Now all of these calls are tracked using its tracking system, but we (Group Development) want to track using Team System. We need some way of moving and syncing items between these two systems.
I completed the first part by using my TFS Event Handler project and that piece is live. If you put a field on any work item called “HeatITSM.Ref” and you fill it out (manually) with an ID from Heat then every time you change the work item it will update heat with a “Note” attached to that “Call”. This was very easy using the TFS Event Handler model, but it still means that you need to create the Work Item manually.
The next step is to create a TFS Heat ITSM application that loads all the calls for a specific “Application” (category) and allows you to create a Work Item with a single click.
Well, I have been working on it, and the Codeplex site is up, and a initial Alfa application is there, but I an doing a refactor at the moment as things were getting a little complicated and confusing on the code side so a simplification was required.
As you can see from the screen shots I am using the TFS Sticky Buddy base code as a starting point and working from there, although during the refactor I am making a lot of changes that will benefit Sticky Buddy v2.0 as well.
Well, Back to the code face :)
Technorati Tags: ALM Personal WPF TFS 2008 TFS
What to read next
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 …
Detecting agile theatre with real delivery signals
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 …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …