schedule 10:30 AM - 11:15 AM place Esquire

Great teams make great products, but what fuels this greatness? It's the common understanding and passion for the product but more importantly the singularity of purpose and the feedback loop and how the users are responding to the teams work. 

The new world of product development is no longer about scope management and delivering the project on time and within budget but it's now more about hypothesis validation and learning from the users and their behaviors.

The dynamics of product development is changing.  As more and more organizations are moving towards maturing their agile software development approach the traditional barriers of roles are being broken creating new opportunities and fostering a shift in the mindset. Instead of being tied down to scope management and delivering the project on time, Agile teams are focused and inspired by hypothesis validation and learning from the users and their behaviors.

In this case study we will go over how a portfolio of 12 SCRUM Teams adopted a more outcome approach and how they shifted their mindset from project delivery in Agile way to adopting the Experiment-Measure-Learn-Repeat loop which plays a crucial role in teams overall motivation, performance and moved from being SCRUM Teams to "Product Teams".

We will also see how we experimented with different team formats and how exposing the team members to different events and user research changed the way they perceived the information of the problem they were solving via features and user stories.

 

 

 
3 favorite thumb_down thumb_up 8 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • Introduction
  • Share interesting facts & stats about teams understanding of Product & Purpose 
  • Experiment We ran to know teams understanding of Overall Product Development process & knowledge outside the boundaries for SCRUM Framework 
  • How we exposed the team to the Before & After elements of SCRUM Framework and the effect it had on their motivation 
  • Show how we got the teams involved with the PO in observing the users and solving the product problems together and how their focus shifted from Output to Outcome!
  • How we changed the dynamics of the team and reshaped them from SCRUM team to a Product Team 
  • How we made the team participate in all parts of BUILD-MEASURE-LEARN loop
  • Questions & Answers

Learning Outcome

  • Team Members will learn why its important to be part of talking to customers and observing users to build a better product
  • Product Owners will learn how involving engineers early on while talking to users helps bring out creativity, better solutions and motivate the team members
  • Product Owners & Scrum Masters will also learn to involve team members in right events during vision creation, hypothesis generation and user validations to bring more diverse set of ideas to table and in your backlog to experiment.
  • Agile Coach & Scrum Masters will learn how to guide & coach your teams beyond "Build" part and also in to "Measure" & "Learn" part of the Build-Measure-Learn loop.
  • Leaders & Executives will learn how in an agile organization and for Agile teams its less about managing and more about mentoring, learn how you can guide the team through "Pivot or Persevere" decisions.

 

Target Audience

Scrum Master, Product Owner, SCRUM Team Members, Executives, Leaders, Managers

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Tathagat Varma
    By Tathagat Varma  ~  1 year ago
    reply Reply

    Kalpesh - the proposal looks good, and might be relevant for the audience. We were wondering if you could include some cast study based on your own work or experience that helps people understand the transition form theory to practice, that will be a great way to have a session. Would you be able to bring such real-world experiences or case studies to the session?

    • Kalpesh Shah
      By Kalpesh Shah  ~  1 year ago
      reply Reply

      Hi Tathagat,

      Sure, in-fact this talk came about after implementing this approach and observing teams operating in this environment, I can definitely convert this talk into a case study. I haven't mentioned the organization name due to proprietary reasons by we have successfully implemented this approach with a portfolio of 12 SCRUM Teams and in my talk I will be referencing to the learning's, benefits and challenges from those teams. I will be bringing data (metrics), pictures and success stories as part of this talk.

      Please do let me know if you need any additional information.

      Thanks,

      Kalpesh

      • Naresh Jain
        By Naresh Jain  ~  1 year ago
        reply Reply

        Thanks Kalpesh. Please update your proposal accordingly and we'll accept it shortly after that.

        • Kalpesh Shah
          By Kalpesh Shah  ~  1 year ago
          reply Reply

          Hi Naresh,

          Made the updates, let me know if that works or if you have additional comments/thoughts.

          Thanks,

          Kalpesh

          • Naresh Jain
            By Naresh Jain  ~  1 year ago
            reply Reply

            Hi Kalpesh,

            Thanks for updating the title of the proposal. However

            1. the session type, still shows it as a talk.
            2. the outline, still feel very much like a talk instead of a case-study.
            3. the learning outcome, seems very ambitious for a 45 mins case-study.

            Request you to please update your proposal to reflect a case-study with very specific learning outcomes based on your experience from the case-study.

            Thank you.

            • Kalpesh Shah
              By Kalpesh Shah  ~  1 year ago
              reply Reply

              Thanks Naresh.

              I have made the changes, please let me know if that works or if you have additional comments/thoughts.

              Thanks,

              Kalpesh

  • Srinath Chandrasekharan
    By Srinath Chandrasekharan  ~  1 year ago
    reply Reply

    I had a look and it looks promising. Can you add more content around the exercises you have mentioned as well as on the proposal for a better evaluation

    Regards,

    Srinath

    • Kalpesh Shah
      By Kalpesh Shah  ~  1 year ago
      reply Reply

      Thanks Srinath.

      The excercise in this talk is about asking the teams "Where do User Stories Come From?" and "What Happens once the Features or Product is Delivered?". These simple questions expose how limited knowledge team members have about the events outside the boundries of SCRUM framework. I have conducted this excercise with many teams and the variety of answers, very often within the same team, is quite suprising and makes a compelling case for involving teams in few critical events outside the SCRUM ceremonies. 

      As part of this talk I highlight that teams need to be part of events like Outcome Definion, Hypothesis design and MVP definition to better understand the motivation and "WHY" of their work and also be part of deciphering the analytics data to know whether their work made an impact. Teams that particiapte in these events create far more better products and bring lot more creative ideas to the table. 

      Thanks,

      Kalpesh


  • Liked Anand Murthy Raj
    keyboard_arrow_down

    Anand Murthy Raj - Philips - Enterprise SAFe Transformation Journey

    20 mins
    Case Study
    Advanced

    About the company

    Philips is a healthcare multinational company that focuses on building complete health care products and solutions for emerging markets, in addition to developing solutions and products for global markets, across the three sectors Healthcare, Lighting and Lifestyle. Using the expertise of its nearly 2000 engineers in Bangalore and aligning the marketing and sales teams the campus is responsible for creating and rolling out a complete set of products that include a whole host of solutions for global customers. It also contributes to global solutions in critical health care component development for connected consumer devices and renewable energy.

    Executive Summary

    Beginning of 2014, an external survey brought out the issues wrt time to market and code quality. Taking the survey results positively, the Leadership embarked on an Agile/SAFe journey with pilot projects. The results were amazing and with the currently learning from the pilots, the organization is running 25+ deployments within. The journey has started and Agile release trains are delivering periodic value to our customers at defined frequencies.

    Background Objective/Challenge

    Product quality, consistent & predictive delivery and quicker time to market are the key challenges the organization is trying to address today. Continuous Innovation is constrained due to the above issues and hence there is need to find a new way of product development which can meet the dynamic business needs, foster people engagement and deliver meaningful products to the world.

    Target

    ScaledAgile has been used as a framework for product development across the organization global. The whole organization is undergoing a transformation from waterfall way of working to the SAFe agile way of working and roadmap is till 2019.

    Agile Initiative

    The Framework used for the transformation can be summarized into 4 major steps

    1. Develop products in the Agile way with focus on Basic Agile practices (Scrum)
    2. Establish Product Ownership with focus on Enabling Scaling aspects (SAFe practices)
    3. Establish a release pipeline with continuous integration (supported by Automation)
    4. Adopt a DevOps Culture with focus on Continuous delivery (to production environment)


    This includes a comprehensive diagnosis of the various business processes, agile practices and behavior, engineering practices, delivery maturity and recommendations for the transition. A coaching and tooling plan is also an outcome of the diagnostics.

     Measurable Impact

    • Predictable Releases to customers (hitting the market with features every three months with features and business criticial bugs with less than 2 weeks with all the regulatory compliance)
    • Capitalization
    • Feature planned vs Feature delivered per program increment > 80%lose
    • Defect reduction co t 45%
    • Team velocity – Baseline vs actual.
    • Very high sense of ownership and high levels of engagement

    Transformation team Profile

    Global team

    • Agile Capability program manager -1 FTE
    • Agile Deployment Program Management – 1 FTE
    • Communication expert – 1 FTE (Today we are 0/1)
    • Coordination - 1 FTE
    • Enterprise Agile Coaches – 16 (Today we are 9 /16)

     

  • Liked Evan Leybourn
    keyboard_arrow_down

    Evan Leybourn - If you need to start a project, you’ve already failed #noprojects

    45 mins
    Talk
    Beginner

    I want to be controversial for a moment and propose an end to IT projects, project management & project managers. I propose that the entire project process is flawed from the start for one simple reason. If you need to run a project, you've already failed.

    By definition, an IT project is a temporary structure to govern and deliver a complex change (such as a new product or platform) into an organisation. However, to be truly competitive, an organisation needs to be able to deliver a continuous stream of change. Managed properly, this negates the need for a project and the associated cost overheads.

    This is fundamentally what #noprojects is. The approach, structure, tactics and techniques available to successfully deliver continuous change. At its core, #noprojects is predicated on the alignment of activities to outcomes, measured by value, constrained by guiding principles and supported by continuous delivery technologies.

    This presentation will introduce you to #noprojects. You will learn how to define an outcome and create an Outcome Profile. You will also learn how to manage change within the context of an outcome through the Activity Canvas.

  • Liked Ran Nyman
    keyboard_arrow_down

    Ran Nyman - Large-Scale Scrum Introduction

    Ran Nyman
    Ran Nyman
    CEO
    Gosei LTD
    Naveen Kumar Singh
    Naveen Kumar Singh
    Professional Scrum Trainer (PST)
    agilemania.com
    schedule 1 year ago
    Sold Out!
    480 mins
    Tutorial
    Intermediate

    Large-Scale Scrum (LeSS) is a framework for scaling agile development to multiple teams. LeSS builds on top of the Scrum principles such as empiricism, cross-functional self-managing teams and provides a framework for applying that at scale. It provides simple basic rules and guidelines on how to adopt Scrum in large product development.

    In this tutorial, we focus on LeSS framework and see how you can scale Agile development to big organizations. We will start by looking at basic assumptions behind scaling and what different approaches there. Then we learn how LeSS deals with scaling in big groups and finally how LeSS can be adopted for existing organizations and what changes it bring in.

  • 90 mins
    Tutorial
    Intermediate

    There is a lot of discussion around user stories, and it is probably one of the most frequently used words in any agile team. For something that is talked about so much in your team, and when the quality of understanding around the user story is directly proportional to creating a successful product, do you know how well your agile teams understand these user stories? What views do they have about these user stories, and what aspects of these user stories do they care about most?

    In this session you will learn and experience three techniques to aid collaboration within your team members and learn to reach a common understanding of the product and user stories that everyone will support. These techniques include role playing in a very different way to help us explore how user stories can help team members see them from a perspective never thought of before.

    This session you will learn and experience through three different exercises how to decipher information your team wants to develop a common understanding of the product and expectations from each other. This session is helpful to product owners, team members, scrum masters and leaders in any organization.