Applying Lean, Agile and DevOps for better business outcomes

In this session we will take a look at DevOps through a ‘Lean’ lens. If one takes a look at the principles behind DevOps, one sees the roots of Lean. These lean roots, when studied and well understood, provide a framework to start measuring and then using those measurements to instrument the delivery pipeline and eliminate the bottlenecks in the pipeline, making it more efficient and productive.

The goal of DevOps is to deliver software to production, in an efficient manner, minimizing risk, and striving for continuous improvement. Applying Lean principles and especially Lean measurements to a delivery pipeline or even better, the entire DevOps lifecycle, helps progress towards these goals, in a proven, and mathematically astute manner. Development teams and organizations that have adopted Agile have already started on this journey for Dev-Test. DevOps extends this Lean and Agile thinking to the entire delivery cycle, and all the stakeholders – from ‘Line of Business’ to Production.

This session will explore the key principles of Lean and Lean Measurements, how they applied to Agile, and how they can be extended to DevOps.

 
21 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • Lean Principles
  • Agile Principles
    • Lean and Agile
  • DevOps origins
    • The evolution from Agile to DevOps
    • The Lean roots of DevOps
    • DevOps and Lean principles
  • DevOps - Lean Software Delivery
  • Applying Lean Measurements for Continuous Improvements
  • Driving Better Business Outcomes

Learning Outcome

This session will explore the key principles of Lean and Lean Measurements, how they applied to Agile, and how they can be extended to DevOps.

Target Audience

All

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • George Dinwiddie
    By George Dinwiddie  ~  3 years ago
    reply Reply

    Hi, Sanjeev,

    As a member of the review team, I'm quite interested in this proposal, but I have some questions.

    First, I note that the slides submitted as examples end with what looks like advertisement, to me. Advertising IBM's reference architecture and solution is not appropriate for this conference. I realize that these slides do not represent the outline you've proposed, but I wanted to make that clear.

    Second, DevOps means different things to different people. In your video, it seems that you mean a collaborative handoff between development and operations. I've also seen it include operations on the development team, on the one hand, and either Ops or Dev directing the work of the other on the other hand. Will your session mention this aspect?

    I also note that the slides (e.g. slide 23) shows monitoring only in the production environment. How, then, is the monitoring capability tested? Should not the staging environment also be monitored, both to detect situations that monitoring will detect, and to test the monitoring code itself?

     - George

    • Sanjeev Sharma
      By Sanjeev Sharma  ~  1 year ago
      reply Reply

      Hello George,

      Thank you for your review of my proposal. 

      • Yes, the slide deck has references to IBMs tooling. The AgileDC presentation will be tool agnostic. As you can see from my video, which does not mention any tools, I am confortable to talking about DevOps without referenceing any tools
      • As per the video itself, the definition of DevOps I adhere to is a holistic veiw - one of collaboration and communication between all stakeholders in the application delivery team, from Lines of Business to Development to Operations, and everyine inbetween collaborate to make the application development and delivery process more lean and efficient. I will compare this approach to a 'NoOps' approach where Ops team is embedded in Dev
      • Slide 23: The concept of Continuous Testing and Continuous Monitoring are to be carried out throughout the delivery process. The Dev and Test environments should be monitored in order to validate that they are 'production-like' and perform as desired.

      In my presentation I will also go into some of the history and evolution of DevOps, and how it has come from 'Lean' and 'Agile' roots to it's current form.

      I have much more content on DevOps on my blog: http://sdarchitect.wordpress.com/understanding-devops/. I am also the author of the 'DevOps For Dummies' book, published by Wiley. A link to the eBook is on my blog.


  • Liked Amy Silberbauer
    keyboard_arrow_down

    Amy Silberbauer - Transforming How We Deliver Value: Agility at Scale

    Amy Silberbauer
    Amy Silberbauer
    Solution Architect
    IBM
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Beginner

    Continuous delivery in software development allows us to deliver incrementally, get quick feedback, and react. A key enabler is the adoption of agile techniques and methods; key inhibitors in the enterprise are size, scale, and complexity. In particular, within large government organizations, teams face immense challenges in both the adoption of Agile and Lean principles but also scaling that adoption to an enterprise level. The Rational ALM organization is a typical enterprise, and our teams have (mostly) adopted agile principles. But agility at enterprise scale is not the same as team-based agile development. Now we must coordinate work across multiple interdependent teams to deliver value, rather than focusing on developing a single product or application. Amy Silberbauer shares her experience of adapting SAFe in an enterprise organization and describes the struggles, mistakes, and successes throughout that process. Amy identifies the key challenges, including the need to identify value, provide the right data for various audiences, and the inherent required culture shift. Learn how to avoid some common pitfalls as you and your own organization embark on this same transformation.

  • Liked Paul Bahrs
    keyboard_arrow_down

    Paul Bahrs / Jason Hamilton - Faster than a speeding bullet – less risk than a water fall!

    60 mins
    Case Study
    Intermediate

    Faster than a speeding bullet – less risky than a waterfall!

    Government programs and agencies follow structured guidelines for just about everything. Guidelines reduce risk and control the value of products and services provided. It should come as no surprise that government organizations generally follow very structured processes for systems and software delivery too. However, the reality in today’s world is that change is inevitable and structured processes don’t harmonize well with change. Programs find themselves driven towards a more continuous engineering approach, where requirements evolve, stakeholders are engaged and an on-demand understanding of engineering artifacts optimizes decision making. These practices are key to Agile development which several government organizations have embraced in order to cope with rapid change and ever-rising citizen expectations.

    In this talk we will present real government case studies of agile adoption for systems and software engineering. We will discuss the objectives, adoption, application and outcomes for each case study and then open the discussion for Q&A.

  • Liked Roger Snook
    keyboard_arrow_down

    Roger Snook - Mobile citizenware development: just HOW do you balance speed and quality?

    60 mins
    Talk
    Beginner

    Mobile is driving the apps economy and has dramatically moved the needle of acceptable quality and speed. Citizens, consumers and employees expect apps that give them access to information as they need it, delivered in a truly engaging mobile experience. Even in the world of compliance and contracts, development teams must adapt to the lifecycle demands of rapid, high quality app delivery.  Nearly ALL mobile dev teams today are using Agile methods. Teams must frequently release new versions of mobile applications in response to feedback from users and testers while maintaining a focus on the regulatory environment in which the mobile app exists. To keep up with user demand, short development cycles are required by mobile, development and operations teams resulting in the need for DevOps practices. This presentation will explore the benefits of collaborative development, continuous testing, and continuous release and deployment in building compliant mobile apps that are engaging and responsive to the public and employees.

  • Liked Reedy Feggins, PMP
    keyboard_arrow_down

    Reedy Feggins, PMP - Scaling Agile Planning to Support Large Distributed Programs

    60 mins
    Talk
    Intermediate
    Many organizations have embraced agile practices only to realize that Scrum and Extreme Programming (XP) cover the development teams’ practices, but they do not usually scale to the rest of the organization. Disciplined Agile Delivery (DAD) and Scaled Agile Framework (SAFe) provide approaches for adopting agile development at enterprise scale. Programs that attempt to scale agile methods often encounter enterprise challenges: process and documentation culture, underestimation of planning effort, and managing a complicated infrastructure. In this session, we will discuss how to executed a scaled agile program using a combination of Disciplined Agile Delivery (DAD) and Scaled Agile Framework (SAFe). Using 2 case studies (small 50 software project, large 300 person organization) we will show attendees how to plan, track and delivery faster with more predictability using a hybrid process.
  • Liked bchaplin1
    keyboard_arrow_down

    bchaplin1 - Minimizing Technical Debt Via Agile Metrics and Techniques

    bchaplin1
    bchaplin1
    Metrics Architect
    Chaplin Solutions
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    Automate and mine those code quality statistics from Sonar and use Agile techniques to transform your team and codebase!

    Studies show that poor code quality can cut your velocity in half as early as the second release.  But there's hope.  Yes, you can make your deadlines and still have little or no technical debt.  

    Using proper metrics 50% of the 100 committing developers had no tech debt and 100% test coverage for all their code submitted in 2013.  

    Use key code quality metrics to manage your team's quality and ensure your second release is just as productive as the first.    

  • bchaplin1
    bchaplin1
    Metrics Architect
    Chaplin Solutions
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    Instrument your console error logging, ETL the data, automate Splunk error log analysis and integrate it into your ticketing system for an accurate and fast feedback loop which can reduce your production errors by 80%  Quickly indentify and route problems as they are noticed in a a development environment well before acceptance test or production.  Track production error trends so new production errors are spotted within minutes, routed to the correct engineer and resolution begun immediately.