3. Why Lean/Kanban? Lean Speed development process Deliver value to customer faster Eliminates Waste Kanban Instantly see project status Visualize project flow (If I’m speaking too fast let me know, it’s not rude I’m just nervous)
4. “Kanban/Lean is the best way to develop software. It cuts development costs, eliminates waste, and decreases the time it takes to deliver value to your business.” -Charles Husemann (just now)
5. Why Team Foundation Server? Central Repository for Project artifacts User Stories Estimates Acceptance Criteria Wireframes Code Generate reports from data You like writing checks to Microsoft (Seriously let me know if I’m going a mile a minute)
6. Why the two together? IF you're a MS Shop it's a great way to implement Kanban/Lean Kind of mostly/low friction TFS supports any methodology you have Great for remote clients/distributed teams*
8. Getting the two to play together Done through Work Item Templates Linked pieces of workflow goodness Can create whatever flow you want Editing them requires the Team Foundation Server Power Tools Not exactly user friendly in TFS 2008 Sucks a little less in TFS 2010
10. What we could have done better Use workflows to enforce constraints on queues Build reporting (Burn charts/velocity tracking) into system ahead of time
Hi, My name is Charles Husemann and I’m here to talk to you about how I managed to marry TFS and Kanban together. My contact info and blog are listed above and you can follow me on twitter at FalconGN. As a warning the project management stuff on my twitter account is a bit buried under a lot of video game, hockey, and general inanity.My blog would be a source of good information if I updated it on a regular basis which I’m planning on doing right after they add two extra hours to the day.
So today we are going to talk a little bit about marrying a Kanban/Lean process to TFS, something that a lot of hardcore agilepeople would advise against What I’m going to do is talk about the approach we used on a recent project with the hope that it will provide some insight into at least one way you can use Team Foundation Server and Kanban in one place as well as talking about a few misses and areas where we could improve the processTo start I’m going to talk a little bit about Lean and Kanban
Is there anyone here who doesn’t have a least a basic idea of what Lean/Kanban is?For those who don’t this was a me
To give you an idea of how this works I’m going to talk a little bit about our implementation of TFS -At a top level we have user stories which define our high level functionsWe have a backlog of all the user stories the client has identified, from there to conceptualization, Verification, and decompWithin these stories we have Kanban items
