Team Foundation Server And Kanban
12
TFS And Kanban: A Marriage of Convenience Charles Husemann [email protected] www.charleshusemann.com Twitter.com: @FalconGN
-
Upload
charles-husemann -
Category
Technology
-
view
2.202 -
download
1
Transcript of Team Foundation Server And Kanban
TFS And Kanban:A Marriage of Convenience
Charles Husemann
Twitter.com: @FalconGN
Overview
(I can see my house from here)
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)
“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)
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)
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*
Our Process
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
Keeping your WIT's about you
• (WIT Demo)
What we could have done better
• Use workflows to enforce constraints on queues
• Build reporting (Burn charts/velocity tracking) into system ahead of time
Alternatives
• Task Board for Team System
• Version One
• Agile Zen
Q&A
Contact Information:
(Available consulting engagements/children’s parties)[email protected]
Twitter.com: @FalconGN
