Kanban was originally created as a scheduling system to help manufacturing organizations determine what to produce, when to produce it, and how much to produce. Although this may not sound like software development, these lean principles can be successfully applied to development teams to improve the delivery of value through better visibility and limits on work in process.
This webinar will provide 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 also describe how Team Foundation Server can be used as a foundation for your work visualization and work flow management.
Approaches to Kanban using Team Foundation Server - Dec 20Imaginet
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.
Introduction to kanban calgary .net user group - feb 6Dave White
February 6, 2013 Calgary .NET User Group Lunch Seminar series - An introduction to Kanban presented by Dave White of Imaginet (http://www.imaginet.com) and board member at Lean Kanban University (http://www.leankanbanuniversity.com)
Approaches to Kanban with Microsoft Team Foundation Server (TFS) Dec 6-2012Imaginet
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.
Kanban was originally created as a scheduling system to help manufacturing organizations determine what to produce, when to produce it, and how much to produce. Although this may not sound like software development, these lean principles can be successfully applied to development teams to improve the delivery of value through better visibility and limits on work in process.
This webinar will provide 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 also describe how Team Foundation Server can be used as a foundation for your work visualization and work flow management. Come join us for this free Webinar!
Top Business Benefits of Application Lifecycle Management (ALM)Imaginet
Why should your business focus on Application Lifecycle Management? What benefits will you see to your overall business? How does ALM impact your bottom line? Come attend this free webinar to discover all the answers!
A Day in the Life: Developer Enhancements with Visual Studio 2012Imaginet
Visual Studio 2012 contains many new developer tools that enhance standard activities. This session will demonstrate features like unit testing, code reviews, and code clones. Visual Studio 2012 introduces a Metro UI, improves usability, and supports asynchronous processes. Team Explorer in Visual Studio 2012 allows improved task management, version control, and code reviews. Developers can now use local workspaces which improve the offline experience. The Test Explorer supports multiple testing frameworks and running tests on compile. Fakes provide isolation for unit tests through stubs and shims.
Kanban was originally created as a scheduling system to help manufacturing organizations determine what to produce, when to produce it, and how much to produce. Although this may not sound like software development, these lean principles can be successfully applied to development teams to improve the delivery of value through better visibility and limits on work in process.
This webinar will provide 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.
Come join us for this free Webinar!
Using Lean and Kanban to Revolutionize Your OrganizationImaginet
The document discusses using the Kanban Method to improve processes in organizations. It describes Kanban as an incremental, evolutionary approach based on visualizing workflow, limiting work-in-progress, and continuously improving processes. The Kanban Method focuses on starting with the current process and making incremental changes over time. It emphasizes principles of visibility, flow management, and continuous improvement through collaboration.
Approaches to Kanban using Team Foundation Server - Dec 20Imaginet
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.
Introduction to kanban calgary .net user group - feb 6Dave White
February 6, 2013 Calgary .NET User Group Lunch Seminar series - An introduction to Kanban presented by Dave White of Imaginet (http://www.imaginet.com) and board member at Lean Kanban University (http://www.leankanbanuniversity.com)
Approaches to Kanban with Microsoft Team Foundation Server (TFS) Dec 6-2012Imaginet
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.
Kanban was originally created as a scheduling system to help manufacturing organizations determine what to produce, when to produce it, and how much to produce. Although this may not sound like software development, these lean principles can be successfully applied to development teams to improve the delivery of value through better visibility and limits on work in process.
This webinar will provide 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 also describe how Team Foundation Server can be used as a foundation for your work visualization and work flow management. Come join us for this free Webinar!
Top Business Benefits of Application Lifecycle Management (ALM)Imaginet
Why should your business focus on Application Lifecycle Management? What benefits will you see to your overall business? How does ALM impact your bottom line? Come attend this free webinar to discover all the answers!
A Day in the Life: Developer Enhancements with Visual Studio 2012Imaginet
Visual Studio 2012 contains many new developer tools that enhance standard activities. This session will demonstrate features like unit testing, code reviews, and code clones. Visual Studio 2012 introduces a Metro UI, improves usability, and supports asynchronous processes. Team Explorer in Visual Studio 2012 allows improved task management, version control, and code reviews. Developers can now use local workspaces which improve the offline experience. The Test Explorer supports multiple testing frameworks and running tests on compile. Fakes provide isolation for unit tests through stubs and shims.
Kanban was originally created as a scheduling system to help manufacturing organizations determine what to produce, when to produce it, and how much to produce. Although this may not sound like software development, these lean principles can be successfully applied to development teams to improve the delivery of value through better visibility and limits on work in process.
This webinar will provide 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.
Come join us for this free Webinar!
Using Lean and Kanban to Revolutionize Your OrganizationImaginet
The document discusses using the Kanban Method to improve processes in organizations. It describes Kanban as an incremental, evolutionary approach based on visualizing workflow, limiting work-in-progress, and continuously improving processes. The Kanban Method focuses on starting with the current process and making incremental changes over time. It emphasizes principles of visibility, flow management, and continuous improvement through collaboration.
Kanban was originally created as a scheduling system to help manufacturing organizations determine what to produce, when to produce it, and how much to produce. Although this may not sound like software development, these lean principles can be successfully applied to development teams to improve the delivery of value through better visibility and limits on work in process.
This webinar will provide 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.
Come join us for this free Webinar!
Getting Agile Right - Rebooting an Agile Organization in 100 days - Agile Tou...Maurizio Mancini
Presentation by Senior Consultant Maurizio Mancini of Exempio.com about an Agile Reboot of one Agile organization that was accomplished in just 100 business days!
The document discusses implementing agile practices at Yellow Pages (YP) and its subsidiaries. It finds that the level of software maturity determines whether an organization is ready for agile or should first transition to incremental and iterative development. At YP, the most mature team successfully adopted agile while less mature teams continued with iterative development. Key factors for agile success included commitment from all roles, dedicated resources, and experienced scrum masters. The optimal approach depends on an organization's ability to fully commit to agile principles.
Drafted presentation to encourage changes to Development processes considering the crises brought on by injecting a start-up into an enterprise environment
2014.09.10 Are Agile Teams More Effective? Findings from the Teamwork Literat...NUI Galway
Professor Torgeir Dingsøyr, SINTEF Research Foundation, Norway, gave this seminar on Are Agile Teams More Effective? Findings from the Teamwork Literature and Empirical Studies of Agile Teams at the Whitaker Institute on 10th September 2014
Going Beyond WIP Limits for Ever-Higher Organizational PerformanceLeanKit
In this webinar, I introduce the concept of WIP Targets and their application at the enterprise scale, and address key questions about how to implement WIP Targets on your team and at scale.
Getting Agile Right - Rebooting an Agile organization in 100 days - Agile Tou...Maurizio Mancini
Presentation at Agile Tour Montreal 2018 by Maurizio Mancini of Exempio and Paul T. Ryan CTO of OpenX.
Many organizations think they are Agile when they are not. Here is how to recognize when you need an Agile reboot and how to reboot your organization to become a true Agile organization.
The document discusses Kanban, an approach to workflow management. It begins with introductions and an agenda for a workshop on Kanban theory and simulation. It then outlines a common problem of handling capacity, output, and strategy. Kanban is presented as a potential solution, emphasizing limiting work in progress based on bottlenecks. The core practices of Kanban are defined as visualizing workflow, limiting work in progress, managing flow, making policies explicit, implementing feedback loops, and improving collaboratively. Examples are given and a simulation exercise is proposed to conclude the workshop.
Agile Evangelist 22 - Freddie Quek - How Not To Do Agile Arrows_Group
This document provides an overview of lessons learned from Freddie Quek's experience implementing Agile practices at Wiley. Some key points:
- Quek has been using Agile since 1999 and leading Agile implementations at Wiley since 2009 involving teams as large as 150 people.
- Common mistakes include not making stand-ups quick and useful, not having retrospectives with action items, and treating remote teams differently.
- When starting a new project, an Agile assessment is helpful to understand the current process. Training, an Agile coach, and experienced practitioners can help teams learn Agile.
- For a large, important project at Wiley involving migrating an existing partnership to a new system, Quek
This document provides an overview of Agile development methods Scrum and Kanban. It defines Scrum roles like Product Owner and Scrum Master, and processes like sprints, daily stand-ups, and retrospectives. Sprints are time-boxed iterations where a cross-functional team works on user stories to deliver working software. Kanban uses visual boards and limits work-in-progress to manage workflow and continuously improve processes through small experiments. While Scrum is more prescriptive, both are empirical and aim to deliver value continuously through feedback loops.
Bosnia Agile slides from Bosnia Agile Tuzla meetup where attendees had a chance to learn about basics of Scrum, by certified Professional Scrum Product Owner Enis Zeherović, and then to participate in a great "Team Work" training that explains all the soft skills Scrum team or any other team needs to have to work smoothly.
In a world where the there is no perfect visualisation, WiP limit, policy or measures? A good choice depends on the context. There aren't only one answer, but in my experience good questions could help to guide to your answer.
Lean and Kanban: An Alternative Path to Agility -Gartner PPM Summit 2014LeanKit
Chris Hefley, CEO of LeanKit, gives this presentation at the 2014 Gartner PPM & IT Governance Conference on Lean & Kanban-An Alternative Path to Agility.
Agile Odyssey: Case Study of Agile Adoption within A Health Insurance Companyalstonehodge
This document summarizes an organizational assessment of an insurance company's adoption of Agile and Scrum practices. The assessment found that while over half of projects used some variation of Scrum, very few teams fully practiced the core Scrum principles. Root causes identified included viewing adoption as an IT initiative rather than company-wide, accelerated use of offshore contractors, and an "Agile deficit disorder" with difficulties committing to practices. Recommendations included updating training, promoting coaching, educating leadership, and rebuilding the Agile community of practice.
Scrum Journey In Healthcare Day Of Agilealstonhodge
An organizational assessment of a healthcare company's agile implementation found that while over half of projects used Scrum, very few teams truly practiced Scrum principles and most struggled with adhering to key Scrum practices. Common issues included teams taking on multiple concurrent projects in sprints, lack of retrospectives, and risks not being properly identified and managed. The root causes were identified as viewing the adoption as an IT initiative rather than company-wide, over-reliance on offshore teams with less experience, and a lack of focus on truly adopting Scrum rather than just adapting it. Recommendations included improving training, establishing an agile coaching program, educating leadership, and fully embracing Scrum principles and values.
Games become more and more important to help people understand the underlying mindset. They help us try new things and experiment in a safe environment. The question is: what makes a good agile game and how to develop one? Before we developed the game I only knew some models about how to develop them, but it was still mostly an abstract concept for me. In this session I want to tell the story of how we developed the Kanban Pizza Game.
Scrum is an agile framework for developing work. It originated in the 1980s and was refined in the 1990s. Scrum uses short iterations called sprints to incrementally develop work items from a prioritized backlog. A self-organizing cross-functional team works during a sprint to deliver a potentially shippable product increment. Scrum rituals like daily stand-ups, sprint planning and retrospectives provide transparency and opportunities to inspect and adapt the process.
Kanban was originally created as a scheduling system to help manufacturing organizations determine what to produce, when to produce it, and how much to produce. Although this may not sound like software development, these lean principles can be successfully applied to development teams to improve the delivery of value through better visibility and limits on work in process.
This webinar will provide 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 also describe how Team Foundation Server can be used as a foundation for your work visualization and work flow management. Come join us for this free Webinar!
This document provides an introduction to lean principles and kanban. It discusses two pillars of lean thinking: don't trouble the customer and develop people. Lean principles include continuous improvement, respect for people, eliminating waste, and problem solving. Kanban is introduced as a change management methodology that utilizes lean tools like visualizing workflow, limiting work-in-progress, measuring and managing flow, making process policies explicit, and using models to recognize improvement opportunities. Similarities and differences between scrum and kanban are also outlined.
Kanban was originally created as a scheduling system to help manufacturing organizations determine what to produce, when to produce it, and how much to produce. Although this may not sound like software development, these lean principles can be successfully applied to development teams to improve the delivery of value through better visibility and limits on work in process.
This webinar will provide 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.
Come join us for this free Webinar!
Getting Agile Right - Rebooting an Agile Organization in 100 days - Agile Tou...Maurizio Mancini
Presentation by Senior Consultant Maurizio Mancini of Exempio.com about an Agile Reboot of one Agile organization that was accomplished in just 100 business days!
The document discusses implementing agile practices at Yellow Pages (YP) and its subsidiaries. It finds that the level of software maturity determines whether an organization is ready for agile or should first transition to incremental and iterative development. At YP, the most mature team successfully adopted agile while less mature teams continued with iterative development. Key factors for agile success included commitment from all roles, dedicated resources, and experienced scrum masters. The optimal approach depends on an organization's ability to fully commit to agile principles.
Drafted presentation to encourage changes to Development processes considering the crises brought on by injecting a start-up into an enterprise environment
2014.09.10 Are Agile Teams More Effective? Findings from the Teamwork Literat...NUI Galway
Professor Torgeir Dingsøyr, SINTEF Research Foundation, Norway, gave this seminar on Are Agile Teams More Effective? Findings from the Teamwork Literature and Empirical Studies of Agile Teams at the Whitaker Institute on 10th September 2014
Going Beyond WIP Limits for Ever-Higher Organizational PerformanceLeanKit
In this webinar, I introduce the concept of WIP Targets and their application at the enterprise scale, and address key questions about how to implement WIP Targets on your team and at scale.
Getting Agile Right - Rebooting an Agile organization in 100 days - Agile Tou...Maurizio Mancini
Presentation at Agile Tour Montreal 2018 by Maurizio Mancini of Exempio and Paul T. Ryan CTO of OpenX.
Many organizations think they are Agile when they are not. Here is how to recognize when you need an Agile reboot and how to reboot your organization to become a true Agile organization.
The document discusses Kanban, an approach to workflow management. It begins with introductions and an agenda for a workshop on Kanban theory and simulation. It then outlines a common problem of handling capacity, output, and strategy. Kanban is presented as a potential solution, emphasizing limiting work in progress based on bottlenecks. The core practices of Kanban are defined as visualizing workflow, limiting work in progress, managing flow, making policies explicit, implementing feedback loops, and improving collaboratively. Examples are given and a simulation exercise is proposed to conclude the workshop.
Agile Evangelist 22 - Freddie Quek - How Not To Do Agile Arrows_Group
This document provides an overview of lessons learned from Freddie Quek's experience implementing Agile practices at Wiley. Some key points:
- Quek has been using Agile since 1999 and leading Agile implementations at Wiley since 2009 involving teams as large as 150 people.
- Common mistakes include not making stand-ups quick and useful, not having retrospectives with action items, and treating remote teams differently.
- When starting a new project, an Agile assessment is helpful to understand the current process. Training, an Agile coach, and experienced practitioners can help teams learn Agile.
- For a large, important project at Wiley involving migrating an existing partnership to a new system, Quek
This document provides an overview of Agile development methods Scrum and Kanban. It defines Scrum roles like Product Owner and Scrum Master, and processes like sprints, daily stand-ups, and retrospectives. Sprints are time-boxed iterations where a cross-functional team works on user stories to deliver working software. Kanban uses visual boards and limits work-in-progress to manage workflow and continuously improve processes through small experiments. While Scrum is more prescriptive, both are empirical and aim to deliver value continuously through feedback loops.
Bosnia Agile slides from Bosnia Agile Tuzla meetup where attendees had a chance to learn about basics of Scrum, by certified Professional Scrum Product Owner Enis Zeherović, and then to participate in a great "Team Work" training that explains all the soft skills Scrum team or any other team needs to have to work smoothly.
In a world where the there is no perfect visualisation, WiP limit, policy or measures? A good choice depends on the context. There aren't only one answer, but in my experience good questions could help to guide to your answer.
Lean and Kanban: An Alternative Path to Agility -Gartner PPM Summit 2014LeanKit
Chris Hefley, CEO of LeanKit, gives this presentation at the 2014 Gartner PPM & IT Governance Conference on Lean & Kanban-An Alternative Path to Agility.
Agile Odyssey: Case Study of Agile Adoption within A Health Insurance Companyalstonehodge
This document summarizes an organizational assessment of an insurance company's adoption of Agile and Scrum practices. The assessment found that while over half of projects used some variation of Scrum, very few teams fully practiced the core Scrum principles. Root causes identified included viewing adoption as an IT initiative rather than company-wide, accelerated use of offshore contractors, and an "Agile deficit disorder" with difficulties committing to practices. Recommendations included updating training, promoting coaching, educating leadership, and rebuilding the Agile community of practice.
Scrum Journey In Healthcare Day Of Agilealstonhodge
An organizational assessment of a healthcare company's agile implementation found that while over half of projects used Scrum, very few teams truly practiced Scrum principles and most struggled with adhering to key Scrum practices. Common issues included teams taking on multiple concurrent projects in sprints, lack of retrospectives, and risks not being properly identified and managed. The root causes were identified as viewing the adoption as an IT initiative rather than company-wide, over-reliance on offshore teams with less experience, and a lack of focus on truly adopting Scrum rather than just adapting it. Recommendations included improving training, establishing an agile coaching program, educating leadership, and fully embracing Scrum principles and values.
Games become more and more important to help people understand the underlying mindset. They help us try new things and experiment in a safe environment. The question is: what makes a good agile game and how to develop one? Before we developed the game I only knew some models about how to develop them, but it was still mostly an abstract concept for me. In this session I want to tell the story of how we developed the Kanban Pizza Game.
Scrum is an agile framework for developing work. It originated in the 1980s and was refined in the 1990s. Scrum uses short iterations called sprints to incrementally develop work items from a prioritized backlog. A self-organizing cross-functional team works during a sprint to deliver a potentially shippable product increment. Scrum rituals like daily stand-ups, sprint planning and retrospectives provide transparency and opportunities to inspect and adapt the process.
Kanban was originally created as a scheduling system to help manufacturing organizations determine what to produce, when to produce it, and how much to produce. Although this may not sound like software development, these lean principles can be successfully applied to development teams to improve the delivery of value through better visibility and limits on work in process.
This webinar will provide 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 also describe how Team Foundation Server can be used as a foundation for your work visualization and work flow management. Come join us for this free Webinar!
This document provides an introduction to lean principles and kanban. It discusses two pillars of lean thinking: don't trouble the customer and develop people. Lean principles include continuous improvement, respect for people, eliminating waste, and problem solving. Kanban is introduced as a change management methodology that utilizes lean tools like visualizing workflow, limiting work-in-progress, measuring and managing flow, making process policies explicit, and using models to recognize improvement opportunities. Similarities and differences between scrum and kanban are also outlined.
The PPT is about scaling agile across various non-cross-functional teams and the various experiments that were done before arriving at a methodology that worked for the teams.
Moving 75,000 Microsofties to DevOps with Visual Studio Team ServicesVSTS Community MSFT
Lessons learned along Microsoft's DevOps Journey|An overview of the Microsoft DevOps transformation story and lessons learned. Delivered at www.devconf.co.za 2018.
The document provides an overview of agile software development principles and practices. It discusses benefits of agility such as faster time to market and better responsiveness. Common agile frameworks like Scrum and Kanban are summarized. Extreme programming practices for engineering are outlined. The document also discusses scaling agile through frameworks like SAFe and applying lean principles to software development. Overall it serves as a high-level introduction to agile concepts, methods and roles.
Introduction to SAFe, the Scaled Agile Frameworksrondal
Sans doute vous identifiez vous dans une ou plusieurs des situations suivantes:
- plusieurs équipes Scrum travaillent dans votre entreprise, parfois sur un même projet ou des projets connexes
- la coordination entre équipes Scrum n'est pas optimale
- vous-même, ou certains stakeholders, ont besoin d'une vue plus long terme sur vos projets Agile, plus que "juste le prochain sprint"
- sur base du succès de Scrum dans votre entreprise, vous voulez allez plus loin et vous voulez rendre plus agile l'entièreté de votre entreprise
Si c'est le cas, venez découvrir le framework SAFe.
Après une présentation du framework et de ses fondements, vous serez en mesure de mieux le comprendre, et de voir ce qu'il peut apporter ou non à votre entreprise.
Cloud Academy Webinar: Recipe for DevOps Success: Capital One StyleMark Andersen
Capital One transitioned to a DevOps model to improve speed of delivery and reduce handoffs between teams. They started with a SWAT team that automated builds, deployments, and infrastructure for two applications. This proved successful and they expanded automation to more applications. Challenges included trying to automate everything at once and handoffs when automation was returned to application teams. Key lessons included focusing on automation, removing handoffs, training application teams on automation, and delivering working solutions incrementally rather than waiting for perfection.
In the world of agile, there is theory and then there is practice. We like to talk about self-organizing teams, asynchronous execution, BDD, TDD, and emergent architecture. We also talk about cross-functional teams: how analysts, testers, architects, technical writers, and UX designers belong on the same team, right next to programmers. It all sounds nice in theory, but how does this work in reality? What do these people actually do? How do they interact? What does it look like? Is there really a pragmatic way to make this work?
In this simulation, a cross-functional team will actually build a piece of software. Every specialist will have a hand in the process. Every specialist will also act as a generalist. Everyone will add value. And as a team, we’ll get something DONE.
This is your opportunity to see agile development in practice, and to bridge the gap between what agilists say and what teams do. And it’s not as new or as difficult as you think – affinity between testers, BA’s, coders, and other team members has really been at the root of effective development practices all along. Let’s just finally acknowledge that it works, demonstrate its capabilities, and encourage it going forward.
This IS agile development.
Team Foundation Server (TFS) provides a robust, enterprise-grade version control system. But how you use that system will determine your level of success. Much has been written about the 'right way' to branch and merge your code. But the fact is, there is no one single best way. This Webinar will discuss the common patterns used for branching and merging code and, more importantly, why to adopt one. We'll talk through aggregate branching models, trade-offs for release management and development, and how to evolve your existing code into the right branching model. Join us for this session and learn how to define the right branching and merging strategy for your team!
Organizational Design for Effective Software DevelopmentDev9Com
The document discusses organizational design for effective software development. It outlines problems with traditional matrix organizations and introduces team-based structures that can address these. Specifically, it advocates for cross-functional teams that are responsible for entire projects or products, rather than individuals being assigned to multiple projects. This allows teams to be accountable for delivery and improves collaboration, quality and outcomes.
Choosing the right agile approach for your organizationInCycle Software
This document provides an overview of different Agile methodologies including Scrum, Kanban, and Scrumban. It discusses the benefits and processes of each approach and provides guidance on how to choose the right methodology based on factors like organizational culture, project types, and team skills. Tools like Team Foundation Server are presented as a way to support Agile planning and tracking across teams.
DOES15 - Damon Edwards - DevOps Kaizen Practical Steps to Start & Sustain a T...Gene Kim
Damon Edwards, Managing Partner, DTO Solutions, Inc
We all love the aspirational DevOps talks about organizations achieving blistering speed and dazzling nimbleness, right? But what can you do when you look internally at your own organization and everything feels complicated, contentious, and stuck? How do you overcome the silos, the legacy, and the entrenched behaviors that are making your DevOps problems seem so intractable?
This talk is about how to start and sustain a DevOps transformations in large and complex organizations using a methodical — and totally reasonable — Kaizen (Continuous Improvement) approach. This talk isn’t about mythical silver bullets or vague philosophies. This talk is about taking a fresh look at proven Lean techniques and empowering teams to find and fix what is getting in the way.
Capital One transitioned to DevOps by starting with a SWAT team that automated builds, deployments, and infrastructure for two applications. This improved speed and removed handoffs. Challenges included trying to automate everything at once and handoffs when automation was returned to application teams. Key lessons included focusing on automation and API's, reducing handoffs, avoiding silos, and delivering working solutions over perfection.
A 1 Day training that shows you all you need to know about Scrum, the afternoon contains a practical part where we perform several sprints using Lego as our means of production
This document discusses strategies for scaling software development teams while minimizing technical debt. It advocates separating teams into roles including developers, team leaders, and engineering managers. Team leaders are responsible for driving cadence and morale, ensuring deadlines are met, and mentoring developers. Engineering managers focus on skills development and removing barriers. Regular, predictable delivery of features through steady cadence is emphasized over long release cycles to reduce technical debt. Separating concerns like architecture from UI helps determine appropriate processes along the agile-waterfall spectrum.
Are you crazy? Using Scrum, Kanban, SAFe and DSDM in one Company!!!Matthew Caine
All four Agile approaches in combination in one company! What a radical thought, especially with the fearsome flames of the agile methodology wars!
It all started with Scrum versus Scrum. Then Scrum versus Kanban. Then everybody against DSDM. And finally late last year things escalated with the global take-up of the Scaled Agile Framework (SAFe).
Sadly dogmatic Agilistas continue to see just one (or two) of the four approaches as the solution to everyones’ problems. Despite the fact that no single one can be the silver bullet.
Yet despite this dogmatism, Agile and Lean has made a massive difference to people’s lives. Hundreds of thousands if not millions of IT professionals and hobbyists benefit daily from these approaches. So we must put our ego to one side and remember that the approaches are not about a particular methodology: They are about people and results.
By putting people and results first we can illustrate in this session why, how and where all four approaches (Scrum, Kanban, SAFe & DSDM) are applicable. Incredibly we will see that a particular type of organization should consider all four!
To support this discussion, we will examine different types of organization, each with their own set of characteristics. For each we will explore which approaches would be the most appropriate now and in the future plus risks.
ALM with TFS: From the Drawing Board to the CloudJeremy Likness
Managing the lifecycle of software development can be a daunting task, especially after having adopted an Agile methodology that has you moving faster than ever. That is why it is more important than ever to have the right tools in place that allow you to effectively manage all facets of your SDLC from requirements gathering to testing and deployment. In the suite of tools available in the space of Application Lifecycle Management (ALM), Team Foundation Server (TFS) is a stand out. Let us show you how your organization can benefit from the advanced capabilities and unique configurability of TFS to successfully deliver your software development projects on time and on budget.
Similar to Using the Kanban Method with Team Foundation Server (20)
Click through this slide presentation to see an overview of Joel Semeniuk's Exclusive Lecture on How Agile Sparked the 4th Industrial Revolution.
Last month Joel spoke with Scrum Alliance Executives about the concept of Industry 4.0 and how it applies to what we do in our workplaces.
“Accessing data and translating it in real-time to deliver more value is representative of how entire industries are thinking.”
• Has Industry 4.0 already made an impact on your organization?
• Will your company survive by 2020?
• How will you change in an economy driven by value?
Let us know your thoughts on Industry 4.0
Watch the video and learn how Agile is reshaping Manufacturing 4.0.
Too busy to watch? Listen to the audio
Upgrading to Team Foundation Server (TFS) 2012 – What You Need to Know! (07-2...Imaginet
Microsoft Visual Studio 2012 brings a number of new features into the integrated ALM toolset. With new features like PowerPoint Storyboarding, Integrated Code Review Features, Stakeholder Feedback, and a newly integrated Developer / Operations Workflow, you will quickly find many reasons to upgrade to Visual Studio and Team Foundation Server 2012! In this webinar, we’ll briefly discuss the breadth of new ALM features. Come join us for this free Webinar!
Getting Started With Coded UI testing: Building Your First Automated TestImaginet
This training seminar will demonstrate how to record tests run against various types of application user interfaces using Microsoft Visual Studio's Coded UI Tests and how to replay them at any time. Additionally, we will explore how to embed validations, either simple or elaborate, to ensure your application is producing the correct results. Learn how to improve the quality of your applications by having a repeatable set of Microsoft Coded UI Tests available to ensure defects don’t go unnoticed!
In 2010, Microsoft released a bold new features to support management of virtual test environments. “Lab Management” provided the ability to easily spin up test environments, perform automated build and deployments, run automated tests, and collect diagnostic data. Unfortunately, many teams were discouraged by the infrastructure requirements. Now, with Visual Studio 2012 and standard environments, even small teams or groups that can’t use Microsoft’s Hyper-V can still benefit from lab management. This session will demonstrate how to configure your existing environments for many of the same compelling features formally available only with Hyper-V. Come join us for this free Live Web Workshop!
Getting Started with Visual Studio’s Coded UI Testing: Building Your First Au...Imaginet
This training seminar demonstrates how to record tests run against various types of application user interfaces using Microsoft Visual Studio’s Coded UI Tests and how to replay them at any time. Additionally, we explore how to embed validations, either simple or elaborate, to ensure your application is producing the correct results. Learn how to improve the quality of your applications by having a repeatable set of Microsoft Coded UI Tests available to ensure defects don’t go unnoticed!
In 2010, Microsoft released a bold new features to support management of virtual test environments. “Lab Management” provided the ability to easily spin up test environments, perform automated build and deployments, run automated tests, and collect diagnostic data. Unfortunately, many teams were discouraged by the infrastructure requirements. Now, with Visual Studio 2012 and standard environments, even small teams or groups that can’t use Microsoft’s Hyper-V can still benefit from lab management. This session will demonstrate how to configure your existing environments for many of the same compelling features formally available only with Hyper-V. Come join us for this free Live Web Workshop!
Quality Coding: What's New with Visual Studio 2012Imaginet
The newest release of Visual Studio 2012 is rich with new tools that enhance standard developer activities. In this session, we’ll review and demonstrate some of these new features, such as Unit Testing, Code Reviews, Code Clones, and other developer tools. Come join us for this free Webinar!
New SharePoint Developer Tools in Visual Studio 2012Imaginet
Imaginet is offering one week of free SharePoint consulting services. To enter to win, interested companies should provide their company name, key stakeholders, contact information, description of business challenge, key considerations, desired outcome, and project budget and timeline to sharepointcontest@imaginet.com by April 30, 2013. The free consulting does not include travel or expenses.
Quality Coding: What’s New with Visual Studio 2012Imaginet
This document provides an agenda for a webinar on quality coding features in Visual Studio 2012. The webinar will review new unit testing, code review, code analysis, and code clone detection tools. It will also cover quality improvements for requirements, manual testing, exploratory testing, and automated testing. Attendees will see demonstrations of features like the unit test runner, code reviews, and exploratory testing in Microsoft Test Manager.
The Newest of the New with Visual Studio and TFS 2012Imaginet
By itself, Visual Studio 2012 included many compelling new features not available in prior releases. But Microsoft hasn’t stopped. Since the production release in August 2012, Microsoft has continued to release more new capabilities. In this session we’ll walk through some of the latest and greatest enhancements that you can use in your Visual Studio and TFS 2012 environment.
The Newest of the New with Visual Studio and TFS 2012Imaginet
By itself, Visual Studio 2012 included many compelling new features not available in prior releases. But Microsoft hasn’t stopped. Since the production release in August 2012, Microsoft has continued to release more new capabilities. In this session we’ll walk through some of the latest and greatest enhancements that you can use in your Visual Studio and TFS 2012 environment.
How Microsoft ALM Tools Can Improve Your Bottom LineImaginet
Microsoft's ALM tools like Visual Studio and Team Foundation Server can help improve an organization's bottom line by addressing common application development inefficiencies and issues. The document outlines scenarios where ALM tools could help such as inconsistent processes, lost work, and quality being an afterthought. These issues waste time and money. Implementing ALM best practices and tools can help capture opportunities by improving visibility, automating processes, and enforcing standards to develop higher quality software more efficiently.
Upgrading to TFS 2012: What You Need to Know!Imaginet
Microsoft Visual Studio 2012 brings a number of new features into the integrated ALM toolset. With new features like PowerPoint Storyboarding, Integrated Code Review Features, Stakeholder Feedback, and a newly integrated Developer / Operations Workflow, you will quickly find many reasons to upgrade to Visual Studio and Team Foundation Server 2012! In this webinar, we'll briefly discuss the breadth of new ALM features. Come join us for this free Webinar!
Getting Started with Coded UI Testing: Building Your First Automated TestImaginet
This document provides an overview and agenda for a four-day instructor-led course on using testing tools in Visual Studio 2012. The course covers recording and writing automated tests using Coded UI, adding validations, best practices, and an overview of the Coded UI tools and APIs. It also demonstrates converting existing manual tests to automated tests and adding assertions during recording.
Upgrading to Team Foundation Server (TFS) 2012 – What You Need to Know!Imaginet
This document provides an overview and agenda for upgrading to Visual Studio and TFS 2012. It discusses requirements and options for upgrading client tools and servers. It covers project compatibility, prerequisites for the TFS 2012 server upgrade, and the general upgrade process. Migration options are presented for moving from other ALM tools, version control systems, and work item tracking systems. Next steps discussed include planning the upgrade, leveraging experience, and executing the upgrade.
Why should your business focus on Application Lifecycle Management? What benefits will you see to your overall business? How does ALM impact your bottom line? View this slideshare to discover all the answers!
Streamlining Testing with Visual Studio 2012Imaginet
This is an overview of the Visual Studio 2012 ALM testing tools, including using Microsoft Test & Lab Manager to manage your testing and using test automation to automate your UI testing. The use of Test Lab will be discussed as a means of automating the creation of virtual environments for testing purposes. Deploying to VM environments during build will be demonstrated and facilitate a robust developer/tester lifecycle. Come join us for this free Live Web Workshop!
In 2010, Microsoft released a bold new featureset to support management of virtual test environments. "Lab Management" provided the ability to easily spin up test environments, perform automated build and deployments, run automated tests, and collect diagnostic data. Unfortunately, many teams were discouraged by the infrastructure requirements. Now, with Visual Studio 2012 and standard environments, even small teams or groups that can't use Microsoft's Hyper-V can still benefit from lab management. This session will demonstrate how to configure your existing environments for many of the same compelling features formally available only with Hyper-V.
This document provides an agenda and overview for a webinar on quality coding features in Visual Studio 2012. The webinar will cover new tools for unit testing, code reviews, code analysis, and code clones. It will also review features for quality in requirements, development, and testing such as storyboarding, test environments, and exploratory testing. Attendees are encouraged to join the free webinar to learn about and see demonstrations of these Visual Studio 2012 features for improving code quality.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Northern Engraving | Nameplate Manufacturing Process - 2024Northern Engraving
Manufacturing custom quality metal nameplates and badges involves several standard operations. Processes include sheet prep, lithography, screening, coating, punch press and inspection. All decoration is completed in the flat sheet with adhesive and tooling operations following. The possibilities for creating unique durable nameplates are endless. How will you create your brand identity? We can help!
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframePrecisely
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Using the Kanban Method with Team Foundation Server
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
– Accedited 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
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
• Crammed in
• Technical debt
• Technical innovation vanishes
• Can’t quantify either
Disengaged people!
• A problem only people
can solve
6. Another Problem
Why is this still a
problem?
We’re great
problem solvers
• But not our
problems
8. What We’ve Tried So Far
What’s Prevalent
– Chaos
– Waterfall
– Scrum
Still Looking…
– Chaos is … chaotic
– Waterfall not well suited
to knowledge work
• Large batch, single
pass, long duration
workflow
– Scrum is well suited but
book methods are
prescriptive without
understanding context
– Adoption itself is hard!
10. The Kanban Method is…
…an approach to incremental, evolutionary
process change for organizations.
http://en.wikipedia.org/wiki/Kanban_(development)
11. Kanban Method
So Why The Kanban Method kaizen
• Designed to…
• Be context sensitive
• 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
12. Kanban Method
agile
• 4 principles
Kanban Method • 6 practices
lean
… and it’s easy to get started
13. 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
14. 6 CORE PRACTICES
visualize
limit WIP
manage flow
make process policies
explicit
develop feedback mechanisms
improve collaboratively
15. The Benefits I’ve Seen
Benefits of Agile plus…
• Deeper understanding of
demand and capacity
• Constantly improving teams
• Empowered to innovate
• Scientific approach
(PDSA • LMB • OODA)
• Exposed Constraints
• Self-imposed
• Team & Organization scope
• Can be rectified once exposed
Happy People
16. Better teams = Better Business
• Predictability
• Agility
• Risk Management
• Governance
• Change Management
17. Solutions Are Just Waiting to be Discovered
• Work is understood!
– Designed to understand demand
– Discover capacity
– Give people the time
improve the system
• People are engaged!
– Self-directed teams that
are empowered
– Own the opportunity to improve
– The mountain of work
is no longer on their shoulders
• Solving Our Problem
– Our problems are
mostly process related
– Learning-focused approach
to improving our processes
19. 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.
20. 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/
25. Where to Start
1. Find a Leader
2. Get Foundational
Knowledge
3. Visualize Your Work
4. Limit your WIP
5. Focus on HIGH Quality
26. Call to Action
• Engage
• Attend our Accredited Core Kanban class with our
Visual Studio day
• Reach out to Dave
• Join the Community!
– Lean-Kanban University
– Lean Kanban North America 2013 in Chicago!
– Limited WIP Society
– kanbandev group (Yahoo)
– Your local Kanban User Group
27.
28. Thank you
http://www.imaginet.com
http://visualstudio.imaginet.com
twitter: @justimaginet
http://www.leankanbanuniversity.com http://tfs.visualstudio.com
30. 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
31. 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
ALM Assessment Workshop
• One week on-site workshop
• 25% discount when ordered in the next 2 weeks*
* Only 1 discount allowed per customer per 6-month period
32. TFS / Visual Studio 2012
Upcoming Fall Workshops & Webcasts:
• Approaches to Kanban with TFS
• December 6 (1:00-2:30pm CT)
• December 20 (1:00-2:30pm CT)
• Streamline Your Testing with Visual
Studio 2012 Testing Tools
• December 13 (1:00-2:30pm CT)
• Getting Started with Coded UI
Testing: Building Your First
Automated Test
• December 17 (1:00-2:30pm CT)
33. ALM Planning & Implementation Services
ALM Planning Testing
• ALM Assessment & Envisioning Workshops • Manual Testing with Test Manager Quick
(3 or 5 days) Start (5 days)
• VS & TFS Migration Planning Workshop • Visual Studio Testing Tools Quick Start
(5 days) (10 days)
• Microsoft Dev. Tools Deployment Planning • Visual Studio Automated Testing Quick Start
– TFS Deployment Planning (5 days) (5 days)
– Visual SourceSafe to TFS Migration Planning (3 Days)
• Visual Studio Load Testing Quick Start
– Visual Studio Quality Tools Deployment Planning
(5 days) (5 or 10 Days)
TFS Adoption or Upgrade Builds
• TFS 2010 Adoption Quick Start • Automated Build & Release Management
(5 or 10 days) Quick Start (5 days)
• TFS 2012 Adoption Quick Start • Automated Build Center of Excellence (CoE)
(5 or 10 days)
• TFS 2010 Upgrade Quick Start (10 days)
Database
• TFS 2012 Upgrade Quick Start (10 days)
• Visual Studio Database Tools Quick Start
(10 days)
Remote Support
• Remote Support for TFS & Visual Studio Integrations
• Team Foundation Server (TFS) & Project
Lab Server Integration Quick Start (10 days)
• Visual Studio Lab Management Quick Start • TFS & Quality Center Integration/Migration
(10 days) Quick Start (10 days)
Email us at:
34. 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
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 is not built in to how we workNot 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:Visualize – create a visual representation of the flow of work through the systemlimit 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 processmanage 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 systemmake 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 operatingdevelop 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 model-driven experiments/scientific method) – The last practice is to use observation and models to drive improvement activities. This is often described as using a scientific method to guide our improvement activities. Using the 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.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.
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.And 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