Why Kanban May Be Your Most Effective Tool for Improving Efficiencies in Operations and Maintenance, Business Process Management, and COTS Implementations

Are you finding the demands to your team overwhelming and the process chaotic? Are your customers saying your team takes too long to deliver or that they have no idea what your team is busy doing? Do you have a growing backlog with requests months to years old? Are people with critical skills not available when you need them? Do you feel like priorities are changing all the time? On top of your ever-growing delivery workload, are you able to develop the capabilities of your team?

The situations above reflect common challenges for software development teams and for IT Organizations in both private and public sectors.  Kanban is being used worldwide as a management method that helps teams pull themselves out of these sinkholes and dramatically reduce work delivery times, increase productivity and improve project visibility. The method’s rapid success is based on its adaptability to existing situations and on its evolutionary capabilities to evolve along with the challenges it must solve. When implemented correctly, it is relatively easy to adopt, encounters minimal resistance to change and quickly enhances morale and trust in organizations.

This presentation aims to provide an introduction to Kanban core practices and why they work and practical insights into where the method might best fit within your organization or agency.

 
6 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • Introduction
  • Overview of Kanban Practices
  • Implementation Approaches
  • Observed Benefits
  • Recommendations
  • Q&A

 

 

 

Learning Outcome

  • What is Kanban and how is it best applied?
  • Why a Kanban approach could be a great fit to your agency’s work flows and culture either by itself or as an enhancer of other practices including Scrum, Incident Management and Portfolio Management
  • How Kanban is used to control Work in Process (WIP) leading to shorter delivery times, higher throughput, reduced firefighting and higher levels of trust with customers.
  • Why Kanban is an optimal approach for more efficient Operations and Maintenance (O&M) activities, COTS implementations, upstream and downstream business process improvements

Target Audience

Change agents, managers and leaders interested in improving delivery of services, stakeholders responsible for O&M processes

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Andrea
    Andrea
    Agile Coach
    Santeon
    schedule 3 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    Project success =  f (listening, feedback, intentionality, practices) 

    To make your agile practices and processes come to fruition, you need to cultivate an environment that promotes listening, learning, inquisitiveness, intentionality and top notch feedback that everyone is comfortable with. 

    Agile projects succeed when there are frequent high-quality reinforcing feedback loops. I will share communication models based on Clean Language questions of David Grove and the Systemic Modelling techniques of Caitlin Walker that can greatly increase clarity, sense of purpose and listening skills within your team and collaborative endeavors.  These include: Clean Questions, Clean Feedback, and Clean Setup.

    This is a hands-on, try it out, concrete practice session.

  • Liked Max Saperstone
    keyboard_arrow_down

    Max Saperstone - Implementing Effective Testing for Behavior Driven Development using Cucumber-JVM

    60 mins
    Talk
    Intermediate

    Behavior Driven Development allows for high level, plain English tests to be written, and to describe and exercise a system. Unfortunately it is difficult to have these tests encompass all interfaces of a software system, and to reuse them in multiple scenarios. Specifying these tests to run at different levels and times without duplicating work is non-trivial, and frequently produces lots of rework. This presentation will focus on cucumber to provide a robust framework for BDD, but any BDD framework can easily be substituting following guildelines and practices covered in this talk. This is not your typical Cucumber tutorial. We will mostly be focusing on how to utilize Cucumber's flexible structure in combination with the Java language how to write singular tests to run over multiple testing interfaces. This framework will build on the Cucumber basics to provide a generic model that also builds on the standard reports, giving additional information for debugging and traceability purposes. Test runners and inputs will also be discussed, to understand how to create more dynamic testing scenarios.

  • Liked Alexei Zheglov
    keyboard_arrow_down

    Alexei Zheglov - Lead Time: What We Know About It and How It Can Help Forecast Your Projects

    60 mins
    Tutorial
    Intermediate

    The session is about just one metric, but a very important one - lead time.  Simply put, lead time is the time between the start of work and delivery.  And there is a catch: if the work has to wait in a queue or if we switch from it to work on something else, the clock keeps ticking until we deliver.  Lead time has proven to be a difficult metric to game.  Even when people try, they often end up delivering faster, with less delay - win-win.

    We will look at examples of real-world lead time data for several different types of work from different companies.  We will discuss the very recent new insights into lead time distirbutions.  Those will then lead us to building useful probabilistic delivery forecast models for your process.  Building such models is surprisingly easy and takes surprisingly few data points.  The models, in turn, enable better decisions.

    Are your ready to embrace the probabilistic approach?

  • Liked Jeff Nielsen
    keyboard_arrow_down

    Jeff Nielsen - The Power of Commitments

    Jeff Nielsen
    Jeff Nielsen
    SVP of Engineering
    3Pillar Global
    schedule 3 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    Doing what you say you will do, when you say you will do it, is one of the key ways to build a relationship of trust. Conversely, nothing erodes trust more quickly than a couple of missed deadlines or broken promises.

    The ability to make and keep commitments is one of the hallmarks of a true Software Craftsman. Likewise, the most effective teams harness the power of commitment to forge strong and healthy partnerships with their customers. This is a surprisingly rare skill, but one that can be learned and improved.

    In this session we'll look at the different kinds of commitments we make as individuals and teams. We'll distinguish between commitments and predictions. We'll reflect on why we sometimes commit when we shouldn't and vice versa. Most importantly, we'll practice some crucial "commitment conversations." 

  • Liked Gene Gotimer
    keyboard_arrow_down

    Gene Gotimer - Developing Security In with Static Analysis

    Gene Gotimer
    Gene Gotimer
    Technical Manager
    Coveros, Inc.
    schedule 3 years ago
    Sold Out!
    60 mins
    Experience Report
    Beginner

    Security is a lot like quality and performance. You can’t tack them on at the end of the development cycle and expect it to be effective. All of them have to be built in along the way, in every phase of every cycle. But even though many companies claim that security is a priority, that doesn’t always translate to supporting security initiatives in the software development process. Security code reviews are often overlooked or avoided, and when development schedules fall behind security testing is often dropped to help the team "catch up". And there is almost never any money in the budget for buying new tools.

    So the first step of building secure applications has to be making security part of the regular development process, but at the same time there isn't time or budget to do so. Developers have to get some quick, easy wins with security without expending a lot of time, money, or effort. Like any agile practice, continuous and rapid feedback is critical.

    Static analysis tools look at source code or compiled code, looking for common errors, unused variables, style and formatting variations, and similar items. Most modern languages have a selection of open-source static analysis tools that can scan source code looking for predictable problems. SQL injection, cross-site scripting, and hard-coded passwords are common vulnerabilities that can often be detected by static code analysis. Static analysis tools can also look at the third-party libraries that the source code depends on, identifying components that have known vulnerabilities.  

    With a continuous integration practice, it is easy to run some of these static code analysis frequently, beginning early in the development cycle. We can make these tools part of the developer's normal routine, heading off potential security problems before it is too late. 

    Gene talks about his experiences with using open-source static analysis tools to build security into the development process without spending much time or effort, but still adding plenty of security value. 

  • Liked Alexei Zheglov
    keyboard_arrow_down

    Alexei Zheglov - Five Very Important Numbers And How They Can Help Improve Your Knowledge-Work Organization

    60 mins
    Tutorial
    Intermediate

    This session will be about five numerical characteristics of a process.  (Call them "metrics", but beware we will be discussing only those that are difficult to game.)  I chose five of them that are not often discussed,  rarely measured, and even less frequently used in making decisions.

    This happens partly because of inertia.  In the better-studied world of manufacturing physical products and services, for example, one of these quantities approaches 100%, another one is almost always (ideally) zero, and yet another one is a single number rather than a statistical distribution.  You don't even have to think about them.  But when the customer value is created in the brains of intellectual workers rather than on the assembly line, the five quantities we will be discussing reveal non-trivial insights.

    We will discuss what you can do to measure them when you return to your office on Wednesday.  We will also discuss how you can practially use the new knowledge, starting on Thursday, to find new leverage for improvement, find time for work that is important, but not urgent, balance capabilities of your organization with the demand placed upon it, deal with uncertainty, and forecast the delivery of your projects and other commitments.

     

  • Liked shentonfreude
    keyboard_arrow_down

    shentonfreude / Paul Boos - Making a Better Salad: Behavior-Driven Development with Lettuce

    30 mins
    Tutorial
    Intermediate

    Is your organization still using brittle GUI driven-tools to ensure applications can be tested? Do you find these difficult to map to the user stories that describe product owner/business needs? One of the current Agile practices to doing this is Behavior-Driven Development (aka Acceptance Test-Driven Development) and writing user stories and acceptance criteria in a Specifications by Example format.  This has real power in that business people can understand the tests and the delivery team can ensure the code meets the tests, thus they serve as an example.

     

    This tutorial will give a short background on Specs by Example/BDD and the show you how to write such tests in Lettuce.  You will gain a deeper understanding of how you can apply this to writing your applications.

     

  • Jeffery Payne
    Jeffery Payne
    CEO
    Coveros, Inc
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    It's a falacy that software built using an agile process cannot be made secure but this statement is often heard.  Reasons given by naysayers often include: Sprints are too short to integrate security analysis, agile doesn't value formalizing the architecture/design and security analysis needs this, and agile doesn't value the types of documentation necessary for security to be validated.  In this presentation, Mr. Payne dispells these myths and discusses an approach for integrating security analysis into an agile development process.  Participants will learn how to identify both bugs and flaws during agile software development and how disciplined continuous integration / continuous delivery significantly assists the security process. Topics discussed within an agile context will include: secure requirements, threat modeling, architectural risk analysis, secure code review, security testing, penetration testing.  Examples of building and deliverying secure software for both commercial and government agencies will be given.

  • Liked Leslie Lowman
    keyboard_arrow_down

    Leslie Lowman - The Art of Being Agile When All About You Are Not

    Leslie Lowman
    Leslie Lowman
    Senior Consultant
    CC Pace
    schedule 3 years ago
    Sold Out!
    30 mins
    Talk
    Beginner

    Ever feel like your team is fighting an uphill battle when it comes to working with support teams, like Dev Ops or Procurement, to complete a project? Has your team ever wanted to just go buy servers for themselves just so it gets done while they are waiting on server delivery from a supporting team? Well, you are not alone!!

    When it comes to working within government agencies, as well as other private organizations, this is the way most Agile teams end up working. It is all about the project team moving toward being Agile while other teams are not. What does that mean for your project and team? Will things get done? Are there other options? 

    This session will take a look at how it feels to work with non-Agile support teams, focusing on working with government agencies, when your team is trying to be Agile.  We will dive into a world of “what-ifs” and “how tos” that will get you thinking about alternative ways to work within the boundaries of what you can control and how to migrate through the things you can’t.