Approaches to Kanban using Team Foundation Server - Dec 20
•Download as PPTX, PDF•
1 like•715 views
Although originally created to help manufacturing organizations schedule and improve processes, Kanban can also be effectively applied to software development. The lean principles of manufacturing can help development teams improve delivery through better visibility and limits on work in process. This Live Web Workshop will start with an overview of the Kanban method including the history and motivation, the core principles and practices, and how these apply to efficiency and process improvement in software development. We'll then move from theory into some of the practice application, demonstrating how Microsoft's Visual Studio 2012 Team Foundation Server 2012 can assist with work in progress visualization, determining limits, and improving processes.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Approaches to Kanban using Team Foundation Server - Dec 20
Similar to Approaches to Kanban using Team Foundation Server - Dec 20 (20)
More from Imaginet
More from Imaginet (19)
Recently uploaded
Recently uploaded (20)
Approaches to Kanban using Team Foundation Server - Dec 20
- 1. Unlock Your Team’s Full Potential Accelerate your Delivery and Reduce Overburdening using The Kanban Method with Team Foundation Server
- 2. Your Speaker Dave White Technical Program Director Imaginet Resources Corp. - Microsoft Partner • Management Board - Lean-Kanban University • Advisory Board - LKU’s Accredited Kanban Training program – Accredited Kanban Trainer (AKT) – Kanban Coaching Professional (KCP) • numerous Microsoft certifications – Microsoft Certified Trainer • 15 years of experience • specializes in helping organizations mature their software development and information technology practices • passionate about Application Lifecycle Management tooling, techniques, and mindsets and regularly talks and teaches on a wide range of ALM topics http://www.agileramblings.com
- 3. Why I Went Looking
- 4. Symptom Lead time for Feature: 12 months “The business unit built that?” “That isn’t what we wanted.” Release Date: in 9-12 months “We’ve got 100s of bugs waiting.” “We’re waiting on other teams.” “We have to get this out right away!” ETA of Bug Fix: ??? “That feature doesn’t matter anymore.” “We don’t have staff for that project/work” “We’re really late.”
- 5. Problem Lots of work, not enough capacity • Quality suffers • Features delayed • Technical debt • How much… • Work?? • Capacity?? Disengaged people!
- 6. Another Problem Why is this still a problem? We’re great problem solvers • But not our problems!
- 7. My Journey
- 8. What We’ve Tried So Far What’s Prevalent • Chaos • Waterfall • Scrum Still Looking… • Chaos is … chaotic • Waterfall not well suited • Large batch, single pass, long duration workflow • Scrum is well suited • prescriptive without understanding context
- 11. The Kanban Method is… …an approach to incremental, evolutionary process change for organizations. http://en.wikipedia.org/wiki/Kanban_(development)
- 12. Kanban Method So Why The Kanban Method • Designed to… • Be context sensitive kaizen • Foster organizational learning • Be evolutionary • Simple rules to govern complex systems • Teams of people are systems • Agile methods can emerge • Fully embraces Agile Manifesto • Lean methods can emerge • Fully embraces Lean Software Development Principles • Tactic-agnostic • Catalyst for organizational improvement To make better
- 13. Kanban Method agile Kanban Method • 4 principles lean • 6 practices … and it’s easy to get started
- 14. Kanban Method Principles start with what you do now agree to pursue incremental, evolutionary change initially, respect current roles, responsibilities & job titles encourage acts of leadership
- 15. 6 CORE PRACTICES visualize limit WIP manage flow make process policies explicit develop feedback mechanisms improve collaboratively
- 16. Visualize
- 17. Visualize
- 18. Limit WIP
- 19. Limit WIP
- 20. Manage Flow
- 21. Make Process Policies Explicit Explicit Policies Explicit Policies
- 23. Improve Collaboratively with Science!
- 24. The Benefits I’ve Seen Benefits of Agile plus… • Deeper understanding of demand and capacity • Constantly improving teams • Exposed Constraints Happy People
- 25. Better Teams = Better Business • Predictability • Agility • Risk Management • Governance • Change Management
- 26. Solutions Are Just Waiting to be Discovered • Work is understood! • Designed to understand demand • Discover capacity • People improve the system • People are engaged! • Empowered • Own the improvements • Pull work • Solving Our Problem • Our processes are important • Learning-focused approach
- 27. My Tools
- 28. Team Foundation Server 2012 Team Foundation Server 2012 Visual Studio Team Foundation Server 2012 (TFS) is the collaboration platform at the core of Microsoft's application lifecycle management (ALM) solution.
- 29. Kanban on TFS 2012 Kanban on TFS starts with… Ability to track work http://vsarkanbanguide.codeplex.com/ Ability to visualize work and flow https://tfs.visualstudio.com/
- 30. Tools Are Enablers Work Items – The data that is important to you
- 32. Tools Are Enablers Visualize CFD here
- 34. How You Can Get Here
- 35. Where to Start 1. Find a Leader 2. Get Foundational Knowledge 3. Visualize Your Work 4. Limit your WIP 5. Focus on HIGH Quality
- 36. Call to Action • Engage • Attend our Accredited Core Kanban class with our Visual Studio day • Reach out to Dave • @agileramblings or dwhite@imaginet.com • Join the Community! • Lean-Kanban University • Lean Kanban North America 2013 in Chicago! • kanbandev group (Yahoo) • Limited WIP Society or your local Kanban User Group
- 37. Want to know more...?
- 38. Imaginet’s New Visual Studio 2012 Website! Visit Imaginet’s new Visual Studio 2012 website, your one-stop hub for all your Visual Studio 2012 needs! http://visualstudio.imaginet.com
- 39. For attendees of today’s session that fill out the survey Free Web Training Subscription Offer Receive 1 free Imaginet On Demand web training subscription Good for 1 person for 1 month Imaginet On Demand is the source for the best Application Lifecycle Management (ALM) training on the internet. Imaginet On Demand is a subscription-based training program for the Visual Studio ALM tools, including Visual Studio, Team Foundation Server (TFS), Microsoft Test Manager, and Microsoft Visual Studio Lab Management. Learn Visual Studio at your pace, wherever and whenever you want. It's that simple! ALM Assessment Workshop One week on-site workshop 25% discount when ordered in the next 2 weeks* * 1 discount allowed per customer
- 40. Top Gun Academy Training Classes Other Imaginet Training Classes – ALM • Microsoft Visual Studio & TFS 2012 – Skills Upgrade (2 days) • Overview Training with Microsoft Visual Studio 2012 ALM Tools (4 days) • Overview Training with Microsoft Visual Studio 2010 ALM Tools (4 days) • Testers Training with Microsoft Visual Studio 2012 ALM Tools (4 days) • Testers Training with Microsoft Visual Studio 2010 ALM Tools (4 days) • Developers Training with Microsoft Visual Studio 2012 ALM Tools (4 days) • Developers Training with Microsoft Visual Studio 2010 ALM Tools (4 days) • Imaginet On Demand Online Web Training – Scrum/Kanban • Professional Scrum Foundations (PSF) (2 days) • Professional Scrum Master (PSM) (2 days) • Professional Scrum Developer (PSD) (5 days) • Professional Scrum Master (PSM) Using Microsoft ALM (3 days) • Accredited Core Kanban Using Microsoft ALM (3 days)
- 41. TFS / Visual Studio 2012 Upcoming Winter Workshops & Webcasts: Please visit http://visualstudio.imaginet.com for our 2013 webinar schedule!
- 42. ALM Planning & Implementation Services ALM Planning Testing • ALM Assessment & Envisioning Workshops • Manual Testing with Test Manager Quick Start (5 (3 or 5 days) days) • Visual Studio Testing Tools Quick Start • VS & TFS Migration Planning Workshop (10 days) (5 days) • Visual Studio Automated Testing Quick Start (5 • Microsoft Dev. Tools Deployment Planning days) • TFS Deployment Planning (5 days) • Visual Studio Load Testing Quick Start • Visual SourceSafe to TFS Migration Planning (3 Days) (5 or 10 Days) • Visual Studio Quality Tools Deployment Planning (5 days) Builds TFS Adoption or Upgrade • Automated Build & Release Management Quick Start (5 days) • TFS 2010 Adoption Quick Start (5 or 10 days) • Automated Build Center of Excellence (CoE) • TFS 2012 Adoption Quick Start Database (5 or 10 days) • Visual Studio Database Tools Quick Start (10 days) • TFS 2010 Upgrade Quick Start (10 days) • TFS 2012 Upgrade Quick Start (10 days) Integrations • Team Foundation Server (TFS) & Project Server Remote Support Integration Quick Start (10 days) • Remote Support for TFS & Visual Studio • TFS & Quality Center Integration/Migration Quick Start (10 days) Lab • Visual Studio Lab Management Quick Start (10 days) Email us at:
- 43. Thank you http://www.imaginet.com http://visualstudio.imaginet.com twitter: @justimaginet http://www.leankanbanuniversity.com http://tfs.visualstudio.com
- 44. For questions or more information, please contact us at: info@imaginet.com or (972) 607-4830
Editor's Notes
- Dave White is a Technical Program Director at Imaginet Resources Corp., a Canadian based Microsoft Partner and Microsoft ALM Partner of the Year for 2011. Currently, Dave is serving on the Management Board for Lean-Kanban University, the global standards body for The Kanban Method. He is also on the Advisory Board for LKU’s Accredited Kanban Training program. He holds numerous Microsoft certifications including Microsoft Certified Trainer. With over 15 years of experience, Dave specializes in helping organizations around the world realize their potential through maturing their culture and improving theirsoftware development and information technology practices. Dave is passionate about Application Lifecycle Management tooling, techniques, and mindsets and regularly teaches around the world on a wide range of ALM topics.
- Personalize the experience around meMy journey as a consultant working with lots of companiesBecome the “Luke Skywalker” of the presentation
- Longer and longer lead times for features/fixesCompetitor is firstMarket has changed – no longer neededAre we doing the right things? (business-driven development)Internal “solution” developed by business
- Teams are getting burned outToo much work, not enough timeQuality goes down (uh oh…)Bug fixing times takes up more of our time (Wasteful!!)New features sit in the backlogOr get crammed in with low quality (Wasteful!!!)Are we doing things right? (technically)Disengaged!!! (oh no…)Now we’re in trouble...http://www.istockphoto.com/stock-photo-20586125-frustrated-businessman.php?st=7645278
- WHY?“I don’t know!”“The business is unrelenting”“We’re working as hard as we can!!”“We’ve tried and given up”Our industry is so driven to produce solutions for other people’s problem, we often fail to solve our problems!We don’t have the experience to know what is wrong with ourselvesWe don’t know how to discover what is wrongLearning about our problems is not built in to our processesNot given time and space to figure it out and improveOur efficiency problems are mostly non-technicalhttp://www.istockphoto.com/stock-photo-18251736-confused-young-woman-scratches-head.php?st=79dbc5f
- What I did to solve my problemshttp://www.istockphoto.com/stock-illustration-4261767-old-map.php?st=e9d038d
- http://www.istockphoto.com/stock-photo-19914666-work-in-progress.php?st=93dd0d6So what did I find out there?!?Chaos (Doesn’t matter what we do. Let’s all just scramble!)Waterfall (Still? Really?? )Agile (Scrum, XP, home-grown methodology)Why (there is that word again) didn’t it work?Chaos (self-evident and sneaky – kinda looks like Agile)Waterfall (not well suited to knowledge work)Large batch, single pass, long duration workflow (usually)Agile (well suited, but book methodologies are prescriptive without understanding context)Lack of leadership in adoptionsWe have LOTS of grey-matter horsepower… often pulling in opposite directions
- I found a method that was …Learning focusedContext awareSpecific about leveraging teams/people to solve problemsEvolutionary, NOT revolutionaryhttp://www.istockphoto.com/stock-photo-17496132-businessman-has-idea.php?st=6c18412
- The Kanban Method is a proven evolutionary, change management approach built on numerous best practices that are intended to target specific problems across the whole knowledge work lifecycle.
- Why I love The Kanban MethodFocused on the peopleBusiness drivenSimple rules that scale to complex situationsLearning focusedEasy to start!!
- So we said that the Kanban Method is a simple set of rules that help us govern complex systems and that really is the case. In fact, the Kanban Method consists of 4 principles that we use to encourage specific behaviour and 6 practices that give us some tactics that allow us to start learning about ourselves and finding solutions to the process problems as they exist in our environments. One of the key advantages of the Kanban Method over other approaches is how easy it is to get started and use so that we can continue to learn and grow over the course of time. http://www.istockphoto.com/stock-photo-20042058-marathon-runners-at-the-starting-line.php?st=dabb4dd
- The Kanban Method is easy to get started because of the first principle, which is to start this improvement initiative what modeling how you work today without any changes. The Kanban Method advocates this approach as it has two positive effects that are important in any change initiative. First, we want to be able to understand the current state and create a baseline on which to compare any improvement activities. We want to find the best places to invest our precious time. Secondly, it will minimize the emotional impact to everyone involved. The second principle is a commitment to small, incremental improvement activities. Small increments are excellent learning opportunities where we minimize the cost and impact of sub-optimal changes. And these learning opportunities help teams plan out the next small improvement.The third principle acknowledges that engaged, happy people a key success factor in the delivery of business value and that we need to provide a respectful and safe environment for the people involved in these improvement activities.And finally, we need to create an environment that allows for and encourages the spontaneous display of acts of leadership at all points of the workflow. These acts of leadership will lead to improvement activities that were not anticipated but will arise to specific problems that the team encounters in their day to day activities.
- Now that we have some principles to govern our behaviour, the Kanban Method also provides 6 core practices that support the needs of a team that is looking to continuously improve and grow their Kanban Method maturity level. The sixcore practices of the Kanban Method are:VisualizeLimit Work In Process (WIP)Manage flowMake policies explicitDevelop feedback mechanismsImprove collaboratively (using model-driven experiments/scientific method)When adopting the Kanban Method, it is not required to practice all six of these concepts. All teams should start at the top in what is called a “shallow” Kanban implementation. As they grow in maturity and capability, teams then adopt more of the core practices as they move to a “deep” Kanban implementation.
- Humans love to see things! We’re very visually oriented. (percentage of brain attributed to visual stimuli?)SoVisualize – This simple tactic suggests that we create a visual representation of the flow of work through the system. In order to do this, we need to describe:Work Item Types in the system (user stories, bugs, improvement activities, support work)Workflow for these Work Item typesAny special behaviours that are associated with work item types (production defects expedited over user stories, only 1 improvement activity in flight at a time)The boundaries of the process being visualizedThe visualization of all of this information will be a powerful tool in impacting the behaviour of the consumers of the information.
- Can anyone see where the problem is in this system?
- Limit Work In Process (WIP) – systems that limit the amount of work in process tend to reduce overburdening on people and help to identify bottlenecks in the process
- Once WIP limits are in place, we formally acknowledge capacity constraints within a phase of our workflow and we can then start to change those constraints
- Manage flow – there are many different ways that we can improve the flow characteristics of work through the system and the Kanban Method explains specific tactics for improving flow in the system
- Make policies explicit – In making process policies explicit or “writing them down”, we’re providing information to everyone who needs to understand how the system is operating
- Develop feedback mechanisms at workflow, inter-workflow and organizational levels – In order to continuously learn and improve, feedback mechanisms must be created and sustained as a part of the way the team works. And these feedback mechanisms are used to manage broader concerns of the organization around the team adopting the Kanban Method.
- Improve collaboratively (using experiments/scientific method) – The last practice is to theories couple with observation and measurements to drive improvement activities. This is often described as using a scientific method to guide our improvement activities. Using a scientific method, we would describe an expectation or a “theory” on the impact of a change, ensure we are able to measure the change, and validate our choices.
- Many of our clients have experienced real, measurable benefits when they have adopted the Kanban Method as a way to manage their systems. Teams have quantitative information regarding demand in the form of work item types and the frequency at which these work items are introduced. And they understand their capacity to do work in the form of flow time and throughput.And now that teams understand demand and capacity in a quantitative fashion, we can measurably improve using flow improvement tactics or the elimination of bottlenecks in the workflow.Empowered to innovate Scientific approach (PDSA • LMB • OODA)Exposed ConstraintsSelf-imposedTeam & Organization scopeCan be rectified once exposedAnd on a more qualitative note, we very often see that team members are happier now that they have been given the permission and the tools necessary to improve the software development process. And since we can see when people are overburdened, we can proactively help teams achieve a sustainable pace and reduce the overburdening that burns out teams and causes employee dissatisfaction.http://www.istockphoto.com/stock-photo-15520861-elegant-middle-aged-woman-with-her-arms-crossed-against-white.php?st=fd67935
- Several of the observed benefits to the business when knowledge work teams use the Kanban Method include: Increased predictabilityImproved agilityBetter risk managementImproved governanceImproved change management@agilemanager: Predictability, improved agility, better governance, evolutionary change, better risk management
- People Solving Problem - http://www.istockphoto.com/stock-photo-12107866-group-of-business-people-looking-at-a-chart.php?st=25d7c05So lets revisit our original process problems and look at how the Kanban Method can help teams find solutions to these problems.To much work, not enough capacityDesigned to discover capacityEvolve your capability (build more capacity)Give people the time and space to improve both quality and processDisengaged peopleSelf-directed teams that are empowered to do the right thingOwn the opportunity to improveThe mountain of work is no longer on their shouldersNot Solving Our ProblemOur problems are mostly process relatedA learning-based approach to change that encourages evolution through a kaizen culture
- The Tools That I’ve used with my teamshttp://www.istockphoto.com/stock-illustration-4261767-old-map.php?st=e9d038d
- People Solving Problem - http://www.istockphoto.com/stock-photo-12107866-group-of-business-people-looking-at-a-chart.php?st=25d7c05To much work, not enough capacityDesigned to discover capacityEvolve your capability (build more capacity)Give people the time and space to improve both quality and processDisengaged peopleSelf-directed teams that are empowered to do the right thingOwn the opportunity to improveThe mountain of work is no longer on their shouldersNot Solving Our ProblemOur problems are mostly process relatedA learning-based approach to change that encourages evolution through a kaizen culture
- What I did to solve my problemshttp://www.istockphoto.com/stock-illustration-4261767-old-map.php?st=e9d038d
- Leadership image - http://www.istockphoto.com/stock-photo-16604784-leadership-highlighted-in-green.php?st=d792438Knowledge - http://www.istockphoto.com/stock-photo-17640698-knowledge.php?st=77ae894Training - http://www.istockphoto.com/stock-photo-18259628-training.php?st=77ae894
- Want to know more?
- Want to know more?