Why is there not more integration found in Team Foundation Server “out-of-the-box” with SharePoint 2007. It seams obvious to me that you would want to show your Work Items in SharePoint and integrate SharePoint Workflow into Team Foundation Server. It only make sense to be able to initially create a SharePoint Work item that is a request from a user into SharePoint, have some sort of approval workflow before assigning it to a project within TFS .
I think that Mike Glaser ’s blog post on "How about one Team Foundation Server portal? I had a dream! " hits the nail exactly on the head. Why can we not view our bugs in SharePoint and create Change requests there?
What would be excellent would be Mike’s hierarchical project space. You should be able to create work items at the root level and then assign them to projects on the way down. This way, user, who have no idea what project a Change Request is for can create them in the central pool, and then the project manager or technical experts can filter them down into the actual project that the change is for.
As a start, instead of releasing “Web access for Team Foundation Server” as a power tool, it should have been re-engineered into a set of web parts that can be integrated into SharePoint. That way we could have used the default site, or created our own custom components.
Microsoft, if you are listening to either Mike or myself…please do not forget the Workflow integration too….
Technorati Tags: Fail SP 2007 ALM
What to read next
Solution to sub sites in Sharepoint 3.0 with Team Foundation Server
Explains how to configure Team Foundation Server to create SharePoint 3.0 project portals as sub-sites, including manual and automated setup …
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 …