Hi Nicole, I agree with Vic about using a single tool if possible. But... We use TFS for our Scrum/Kanban work because of Build, Test, Release Automation and Source Control features in TFS. So, what we did was have one of our developers build integration that synchronizes the stories in TFS to the project plan in Workfront. It's only one way, from TFS to Workfront capturing TFS stories because that is where Product Owners and Teams create, split, and modify features and stories. The stories and their story points, assignments, estimates, status, and actual hours are copied into the project plan under an execution parent task. The stories maintain parent/child relationships. This synchronization happens every morning at 2:00 AM. Its not the most elegant solution but it gives the PMO and Project Managers an idea of what is in the backlog, in progress, and has been completed. It also populates our workers Workfront time sheets. All our projects have a unique sequential number ID prefix. All user stories in a project have the same prefix. Our developer's program searches TFS for any newly modified user story, matches the prefix with the project prefix, and inserts the story in the next available line under the execution patent task. There is room for improvement in the integration but it meets our requirements. Hope that gives you some ideas. David Allingham Project Manager Reed Tech®, a LexisNexis® Company dallingham@reedtech.com