Setting agile teams for success – Use of Operations Research to improve agility

While there is a good amount of literature on how an existing agile team can self-organize to deliver higher business value, very little has been said about how to use learning from one team on another or how to set new agile teams for long term success.

In our organization, a typical engagement lasts for 6-8 weeks, leaving very little time for team ramp-up. Setting teams for success was not aspirational but a core ingredient to our service delivery. We explored the field of Operations Research (OR) and applied some of the techniques to software engineering. In this experience report, we are going to share how we leveraged OR concepts such as “Queueing Models” and “Network Optimization” techniques to identify

- What should be the ideal size of a story to deliver optimal value

- What should be the optimal team staffing for a given scope of work

- How to get more predictability on release plans of agile projects

While our research in this field has been tailored to a very specific type of work we do, the concepts and learning can have wider application.

 

 
 

Outline/Structure of the Experience Report

Session Outline (prefer a 60 mins slot):

- Who are we, where we come from? (2 mins)

- The problem we set out to solve (3 mins)

- Intro to the OR concepts we explored, how we mapped them to Software engineering? (10 mins)

- Volunteer driven game to illustrate the OR concepts (20 mins)

- The data driven insights we derived from our experiment, how we applied these insights (10 mins)

- Recap of Key learnings (5 mins)

- Q&A (10 mins)

 

Learning Outcome

For program managers/ Functional Managers running multiple agile teams

- How to get better predictability during release planning

- How to staff a right sized team for a specific project

 

For Product Owner:

- What is the right size of a story? How to be more scientific about (instead of going by purely gut feel) what granularity the team should aspire for?

 

For Agile Coaches:

- A whole new scientific perspective of looking at software engineering

- A potential new area of further research

 

Target Audience

Product Owners, Program Managers running multiple agile teams, Agle Coaches driving agile transformation

schedule Submitted 7 years ago

Public Feedback


    • Bhuwan Lodha
      keyboard_arrow_down

      Bhuwan Lodha - Building a Team Backlog: The Power of Retrospectives

      Bhuwan Lodha
      Bhuwan Lodha
      VP - Digital
      McKinsey & Company
      schedule 7 years ago
      Sold Out!
      45 Mins
      Experience Report
      Intermediate

      “Inspect and adapt” is one of the basic tenets of continuous improvement, and agility in general. Holding retrospectives is one of the core processes that allows teams to look back and reflect on their progress. However, over time, teams may focus only on the product work and lose interest in their own improvement as a team. Kanchan Khera and Bhuwan Lodha believe that one approach to solving this problem is to bring the rigor, structure, and discipline we use for maintaining healthy product backlogs to team improvement by creating a “team backlog”—items the team needs to do to improve itself. The team backlog introduces three keys to successful and sustainable team improvement—a structured framework, visibility of its impact, and creative ways for building the backlog. Just as a healthy backlog is the basis for a great product, so a healthy team backlog helps create great teams.

    • Ted Tencza
      keyboard_arrow_down

      Ted Tencza - Creating a Great Engineering Culture in an Agile workplace.

      Ted Tencza
      Ted Tencza
      Head of Engineering
      Prospa
      schedule 7 years ago
      Sold Out!
      45 Mins
      Talk
      Beginner

      Company culture, or its DNA, is one of the most important factors to determing if a company succeeds.  Many companies claim to have great company culture.  But what does this mean, how can you know if your company has a great culture, and how can you go about improving the culture?  This talk will explore what great companies have in common, and share experiences I have had in helping to develop engineering culture during my career.    

      Will also explore how Agile principles help to foster creating the best possible culture for your organization.

    • Vibhu Srinivasan
      keyboard_arrow_down

      Vibhu Srinivasan - Coding with Geeks- De Code the secrets behind TDD, BDD and ATDD

      90 Mins
      Tutorial
      Intermediate

      This session is a coding sessiont that takes a problem and shows clearly what is the difference between TDD, ATDD and BDD. Ths session uses code for the server layer as well as UI layer.

      This session is not for you if you do not code. If you do code, please bring your laptop as we delve into the details of all these styles of programming techniques.

      We will rotate between ATTD, TDD and BDD periodically and show it at use in different layers. This session will be using Java , Rails, Scala and C# together so that you can see how you can benefit do these techniques even when coding in different languages.

      We look at common pitfalls and wrong beliefs that programmers have when it comes to these concepts

      This session is purely keyboard and you will have to bring a laptop.

    • Vibhu Srinivasan
      keyboard_arrow_down

      Vibhu Srinivasan - Working at a lean startup

      20 Mins
      Experience Report
      Beginner

      I have had the oppurtunity to build and be part of a few successful and failed startups. One such succesful startup was my association with a startup called Evri.com. I have also consulted as a developer and coach for a gaming company called BigFishGames which went to become a largely succesful gaming company making one game a day today. 

      In this session I would like to tell the story of what happened at Evri and Big Fishgames that made them succesful. 

      This is a lessons learned, observatiosn shared being part of this startup as a developer. This session also looks at what makes a good product. Is product creation a pure idea of a bunch of geeks working together or something more than that. 

       

      Come see and learn