After revolutionizing the automobile industry, Lean principles have been successfully applied to different knowledge areas including software development. This workshop is intended to master Lean concepts like Waste, Push&Pull systems, systems thinking, Kaizen etc. & practicing cross-functional collaboration, self-organisation and safe-fail experimentation! In this interactive game, the participants will work in a small production lines, experiencing problems and applying Lean practices to overcome them.

 
 

Outline/structure of the Session

Workshop for ~60 mins..

Works in 3 iterations.. each iteration learning & trying new principles & practices & learning to use them in the subsequent iterations..

End of each iteration will have a small retospective to reflect on learnings

Learning Outcome

Lean concepts like Waste, Push&Pull systems, Systems thinking, Kaizen etc. & practicing cross-functional collaboration, self-organisation and safe-fail experimentation..

Learning to implement them in the IT world. Folks in the IT industry who are looking for ways to increase the efficiency & thoughtput of their teams..

 

 

Target Audience

Folks in the IT industry who are looking for ways to increase the efficiency & thoughtput of their teams.. BAs, PMs, Dev-leads, Coaches

Requirements

  1. To build 3 production lines - 
    • 4 small tables to be set up per production line (hence 4*3 = 12 tables)
    • each table to accomodate 3-4 participants
  2. 4 lego boxes OR some stationery to develop the 'task to build'
  3. a white board/flipchart to mark the progress of the group
schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Niranjan N V
    By Niranjan N V  ~  2 years ago
    reply Reply

    Hi Sneha,

    Thanks for the interesting workshop. Would be keen to attend.

    Regards

    Niranjan

    • Sneha Kadam
      By Sneha Kadam  ~  2 years ago
      reply Reply

      Hi Niranjan, Thank you for showing interest :)

      Looking forward!

  • Naresh Jain
    By Naresh Jain  ~  2 years ago
    reply Reply

    Hi Sneha, thanks for the proposal. Since this very workshop will be presented at the Agile Pune 2014 Conference, we would like to see something different. Request you to reconsider this proposal.

    • Naresh Jain
      By Naresh Jain  ~  2 years ago
      reply Reply

      Sneha, we've got very good reviews of your workshop from Agile Pune 2014 Conference. We would like to consider this proposal for 2015 conf as well. Thanks.

      • Sneha Kadam
        By Sneha Kadam  ~  2 years ago
        reply Reply

        That's good to know Naresh, thanks. I'd like to run it for the 2015 conf. as well. Let me know!


  • Liked Krishnamurty VG Pammi
    keyboard_arrow_down

    Role of Scrum of Scrum meetings in achieving Transparency and Speed - Experiential insights on what it takes to reflect “shared team goal” in scaled agile framework

    Krishnamurty VG Pammi
    Krishnamurty VG Pammi
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Are you in need of stepping up “Transparency” & “Speed” in your scaled agile framework? Are you experiencing the difficulty that most of your scrum teams are focusing on their individual team specific goals and thus missing “whole-team” thinking towards “Shared Project goals”?

    Learn our practical case study on how our teams could able to establish “Transparency and Speed” through realizing the connect among our “Daily Scrum”, “Scrum of Scrum”, “Scrum of Scrum of Scrum” events on a happening project that comprises of 18 scrum teams belonging to 10 business components located at 4 different countries.

    Experience how our teams are able to instil the sense of urgency among the virtual teams and understood the noble purpose/role of “scrum of scrum” events in resolving cross site dependencies promptly through our 3 step framework “Plan, Perform and Adapt”

    (1)    Plan:  Easy to use planning practices adopted by our teams to make our scaled “scrum of scrum” agenda simple and relevant.

    (2)    Perform: Ground level challenges resolved by our teams and how our team could able to implement the agenda set in achieving transparency, speed and thus quality.

    (3)    Adapt: Practices our team implemented in responding to the change and adopted “whole team thinking” in achieving“ shared project goals”

    Scrum of Scrum events helped our team progress quickly and easily. Our team could able to coordinate and integrate their work effectively. The interesting thing is that our teams could able detect the risks early in this game and came up with apt response strategies to address them.  

    Keeping the discussions short and focussed in these events comes with practice and preperation. Our teams are kept current with “cross team dependencies”, “Risks with response plan”, “Issues and their progress” and “number of added stories and defects since we last met”.  Our teams leveraged Visual communication channels when it comes to “scrum of scrum of scrum” across different sites.

    Come and experience our case study and take-a-way “useful” learnings to make your scaled agile project achieve “Transparency”, “Speed” and thus “Agility” with teams reflecting “whole-team thinking” and working for “Shared project goals day after day….

  • Liked Vijay Bandaru
    keyboard_arrow_down

    Scrum Master Experience Report

    Vijay Bandaru
    Vijay Bandaru
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    This presentation brings a different perspective for the Scrum Masters and helps them to become more powerful Scrum Masters through their enhanced soft skills. I am going to cover how the teams evaolve, how the change is resisted, how the teams behave, how Scrum Master can handle all these effective to make the teams deliver working software every sprint continuously.

    The information explained below is from my experience as Scrum Master and Coach. Below are the points that will be covered in the presentation:

    Primarily I am planning to cover the anti patterns that will push the teams back and where the Scrum Master can support the teams with his knowledge, experience and interpersonal skills. For example please find below some scenarios:

    1. In effective sprint planning: Team might miss some of the tasks while doing the sprint planning part 2 so they will anyway identify them during the development of the stories so these tasks take additional time which is not budgeted. So they will have to miss some stories which will impact the sprint goal. So I encourage the scrum masters to collect all such unidentified tasks on a separate colr sticky notes and during retrospective discuss with the team to see how much % of the capacity is gone for that tasks. At the same time are there any tasks in that list can be repeatable tasks (Eg: Code review) so this will help the team to come up with a tasks checklist which will help the teams to do effective sprint planning part 2 

    2. Partially ready stories pushed into the sprint: Sometimes product owners push the stories that are not fully ready and the team cannot say "No" in this case either the story gets changes during the sprint or it cannot be finished due to unknown factors. So Scrum Master to encourage the team to have a proper DOR (Definition of Ready) and get a working agreement between the PO and team so that they will work around it whilst they understand "Responding to change over following a plan"

    3. Cross functional behavior: Team generally does not want to become cross functional because they are fine with what they are. Scrum Master has to bring a change in their thought process and get them agreed to become cross functional. For this it takes time so SM has to also manage the management expectations with respect to set the expectation in the dip in productivity

    4. Pale retrospectives: This is another area where Scrum Master has to provide support to teams and get the liveliness and make the teams high performance teams

    5. Timeboxing: Most of the teams do not respect this important guideline. Again SM has to get the importance of this characterstic in to the teams and get them aligned towards this. So there are some examples which I can quote such as if different people arrive at different timings, how much time is wasted and how many times we need to recap on the points already discussed, how much gap created etc

    6. Stop starting and start finishing: This will cover to complete the stories/tasks that you are working before you pick up something. In general the teams pick up many items at a time and complete them close to 100% but not 100% so this will impact the sprint goal. In such case the SM has to provide inputs to the team to pick as few as possible but close them as soon as possible so this way the value delivery at the end of sprint is guaranteed

    7. Lack of importance for quality: In the hurry of completing the stories the team at times give less or no importance to the quality. So the probability of escaped defects or getting rejection for the stories is high. So the Scrum Master has to educate the teams to strictly define/refine/follow the Definition of Done for each story. I saw many teams having their DOD in the tools like VersionOne but not infront of their eyes. 

    8. I know when I see it: Information radiators. This will be the key for the teams to adjust their pace as per the principle #8. So creating big visible information radiators and updating the underlysing details frequently will bring attention in the team and they naturally tend to adjust their delivery mode as per the requirement 

     

  • Priti Biyani
    Priti Biyani
    schedule 2 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    We do have test pyramid in our project to gain confidence on the code we will be delivering. We have also smoke tests, which will give us quick feedback. Still I'm saying Automate all the things!

    What??

    Well, yes! In agile world, there is a theme of ruthless automation. But in my opinion, we don’t push this principle nearly enough.

     

    In this talk, I will share some of my expereinces and some interesting things which we never thought we could automate. Yes, We can automate everything!

  • Liked sailee
    keyboard_arrow_down

    UI Automation : Safety Net to Trap Net!!

    sailee
    sailee
    Radhakrishnan
    Radhakrishnan
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    At the BEGINNING Of the project: Yay!! Lets automate and cover all test scenarios!! Lets work towards increasing the test coverage !!smile

    After 1 year: Regression suite is too bulky!! I can't maintain it anymore!! Its too flaky!! frown

    Does this conversation ring a bell? Well, this is a common scenario in projects. The UI test automation starts as a saftey net and then becomes a trap net! 

    Heavy Functional tests layer → Long execution time → Low confidence → Problem of Maintainence

     

    This talk will address these problems in an Agile project. Some solutions that worked in our team. How working as a Team would help prevent these problem?

     

  • Radhakrishnan
    Radhakrishnan
    schedule 2 years ago
    Sold Out!
    20 mins
    Talk
    Beginner

    Given you have a PRODUCT to test

    When you start testing it

    Then STOP testing it

    And start USING it


    In this talk I would like to address how important it is for the whole team to use to product to see the good, the bad and the ugly side of the product you are building which are otherwise unknown to the team until they go live.

  • KK Sure
    KK Sure
    Sheril Jebasingh
    Sheril Jebasingh
    schedule 2 years ago
    Sold Out!
    20 mins
    Case Study
    Intermediate

    Traditionally, in software development, user experience (UX) wasn't valued as much as developing of the software itself. But this has changed rather radically. However, creating an enriching user experience in an agile fashion is still challenging. Most of the agile engineering practices in use are around building software but seldom address UX. When building a product in an agile fashion, UX in an incremental fashion becomes important.

    In this talk, we will present our experience of creating UX in an incremental fashion for a virtual wallet. We will also talk about the different challenges we faced such as, educating various stakeholders on the value of incremental UX, building collaboration between developers and experience designers and abstracting design components, along with the solutions we devised to tackle these challenges.

  • Pooja Salpekar
    Pooja Salpekar
    schedule 2 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    “When deploying and administering large infrastructures, it is still common to think in terms of individual machines rather than view an entire infrastructure as a combined whole. This standard practice creates many problems, including labor-intensive administration, high cost of ownership, and limited generally-available knowledge or code usable for administering large infrastructures.”— Steve Traugott and Joel Huddleston

    Server infrastructure has traditionally lagged far behind our development practices in terms of code quality, testing, continuous integration and continuous development.

    When you write your Chef recipes or Puppet manifests or any other CM, you are coding, and every code is prone to defects. All of us understand the benefits of test-driving the application code. The same applies to your infrastructure code. Testing becomes even more significant in case of deployments spanning large clusters of nodes.

    Test-driving allows the infrastructure teams to have confidence that their configuration changes are being applied as intended across many different systems, and having the intended effect. This allows the whole system to be trusted, and then updated without fear for introducing breaking changes or otherwise causing instability.

    The objective is to cover agile lifecycle of infrastructure code and provide a quick demo of how to test drive infrastructure management code. 

  • Shiva Krishnan
    Shiva Krishnan
    schedule 2 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    My journey as an agile coach has been a great learning experience.

    In this session i intend to share some key learnings that contribute to effective coaching.

    I have aggregated my presentation under the following topics:

    • Coaching with Compassion vs coaching for compliance - why it is important to understand the team's needs instead of running the coach's transformation agenda. How do we involve teams in the transformation?
    • The coach’s mindset defines his/ her coaching - Many times coaches are not able to identify team problems due to their own biases. How can a coach be aware of such biases and overcome them?
    • Making your coaching visible - A common failure in transformations is that coaches are unable to make their progress visible. We will look at some interesting techniques to make  coaching progress visible
    • Involving stakeholders -How do we involve stakeholders other that the teams? why is it important?
    • Coach for a coach - Every coach needs a mentor . How do we effectively utilize mentors? what role do they play in a coach's growth?
    • Celebrating success - We often fail to talk about our successes and acknowledge teams. How did we do this in our organization?

    In each topic i will be sharing my experience, learnings and techniques that i used to overcome challenges.

  • Shiwangi Prasad
    Shiwangi Prasad
    schedule 2 years ago
    Sold Out!
    45 mins
    Tutorial
    Beginner

    As a tester in an agile model of software development team, I felt the need to have an automated mechanism of getting fast feedback on my growing application. This talk is to share my learnings on the set up, configuration and various processes followed in this automation. The benefits of having a CI and automated test runs, their set ups will be shown through a demo.

     

  • Liked Sreedevi Vedula
    keyboard_arrow_down

    The Practical Pyramid

    Sreedevi Vedula
    Sreedevi Vedula
    schedule 2 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    An Ideal Test Pyramid is an invaluable technique to succeed with agile. However, it is challenging to have this ideal pyramid in practical projects for several conditions in the projects, like legacy code bases. To have a good test pyramid, several best practices of software development need to be followed. This talk discusses the practices that help in implementing test pyramid and the challenges faced by many teams in doing that and suggestions on how to overcome them.

  • Liked Sophie Freiermuth
    keyboard_arrow_down

    Prioritizing user stories: using value to users as a key criteria

    Sophie Freiermuth
    Sophie Freiermuth
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    Product development in agile is always at risk of favouring velocity and developer's skills.

    Favouring velocity means that when it's time to select stories, the team will elect to do many short stories to keep velocity on the rise, or stable.

    Favouring skills mean that easy implementation may be selected, or sometimes tricky solutions which will give the developper the satisfaction of solving a difficult problem.

    The outcome of the story's execution and value to users is an important criteria, and I'd like to introduce you in this session to a technique that helps prioritize against two sets of criteria: technical difficulty and value to users.

    Using Personas, a tool from product design which I will explain, and a simple grid, this technique makes prioritization incredibly easy - which then enables the team to focus on getting stories done, rather than figuring out which stories.

  • Liked Sophie Freiermuth
    keyboard_arrow_down

    Integrating UX into the Agile Development Cycle - A case study over 3 projects

    Sophie Freiermuth
    Sophie Freiermuth
    schedule 2 years ago
    Sold Out!
    45 mins
    Case Study
    Beginner

    User Experience design is a product design discipline which sits throughout a product's lifecycle, from inception to development to maintenance and all the way to retirement. Waterfall enabled the discipline to have ample time and produce extensive design, in a "big design upfront" approach which rarely involved technical capabilities, and resulted in difficulties in build. The adoption of agile by product development team has offered UX a unique opportunity to work in a much more joined-up manner, and expend the design into the development, enabling the entire team to react to change.

    As a UX designer, I have over the last 7 years developped a solid appreciation of working embedded in an agile development team, and would like to share my experiences through 3 specific projects, sharing my learnings to help development team on-board the UX practitioner, their tools, practices and skills.

    This session will be a case study over 3 projects, highlighting the learnings and steps of the integration of UX into the development cycle. I'm taking Alistair Cockburn's sequence of SHU-HA-RI to detail the progress of my practice and will pay great attention to sharing sufficient context that my experiences and outcomes can be translated to your own projects and team setups.

  • Vijay Bandaru
    Vijay Bandaru
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    I was part of a Large Scale Agile transformation in my organization and I was one of the Agile coaches there. As part of transformation we have created LeanOps teams to manage the technical debt, production incidents with a focused concentration. This article covers the following:

     

    - Why the trasnformation required?

    - What are the structural changes implemented?

    - LeanOps inception

    - Lean Ops working Model

    - Challenges with the LeanOps

    - How we addressed those challenges?

    - Goal oriented approach

    - Q & A

  • Liked Chirag Doshi
    keyboard_arrow_down

    1000 Words - Illustrating Project Challenges with Visuals

    Chirag Doshi
    Chirag Doshi
    schedule 2 years ago
    Sold Out!
    80 mins
    Workshop
    Intermediate

    A project can face varied challenges through its life, foreseen and otherwise - runaway scope, high defect volumes, depressed velocity, and many more. Addressing many of these first requires recognition of the problem and then action from one or more sets of project stakeholders. Telling the story with simple visuals can be a very powerful way to articulate a challenge (the what), the potential root causes (the why) and the options available to fix it (the now-what). Teams typically already track a lot of data related to throughput, quality, scope and cost. Creative use of this data combined with simple, hand-crafted visuals can be much more effective than hundreds of bullet points. In this hands-on workshop, you get to exercise your visual thinking and visual communication skills. We introduce some simple visual thinking techniques like Look-See-Imagine-Show, and then let you apply them in a project simulation, so that you can practice hand-rolling simple visuals that speak volumes (no fancy tools needed!).

  • Michael Harris
    Michael Harris
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    For agile to work at scale in enterprises, there needs to be clarity around the hierarchy (or lack of hierarchy) of roles across teams and products to ensure sound governance and, perhaps more importantly, to offer career (and salary!) progression.  This presentation will propose a competency-based approach for the development of skills and competencies of the workforce, and thus creating a sustainable transformation in an enterprise. We will include experiences of implementing those components of the proposed model that have already been tried and tested.  Feedback will be sought from the participants.

  • Liked Alexey Pikulev
    keyboard_arrow_down

    “Help Me Do It Myself!” Growing a self-organization by using the Montessori Method

    Alexey Pikulev
    Alexey Pikulev
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    “Help Me Do It Myself!” Montessori is an innovative, child-centered approach to education, developed a century ago by Dr. Maria Montessori who was struck by how avidly the children absorbed knowledge from their surroundings. The goal of the Montessori method is to foster a child’s natural inclination to learn, where Montessori teachers guide rather than instruct, linking each student with activities that meet his interests, needs, and developmental level. But is this method only suitable for children?

    In this talk, I will demonstrate how to apply the Montessori education method in growing self-organized teams. We’ll discuss what Leaders may find useful and how to adapt this methodology in the day to day work of your organization.

  • ShriKant Vashishtha
    ShriKant Vashishtha
    schedule 2 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    Way back in 2008, when I started working in Agile, there was enough material available on Scrum and. However when it came to distributed aspect of it, people were still struggling with it. Based on working for years in this fashion, I realised that communication, trust, transparency and innovation are the core fundamental values towards successful distributed Agile implementation.

    In other words, as most of the problems were caused by softer aspects of skills (misunderstanding, miscommunication, non-availability of people, mistrust etc), humanizing the distributed team experience looked like the key for successful distributed Agile implementation.

    Based on working with distributed teams over the years, we discovered some distributed Agile patterns. Some of them got blogged from time to time. Those already available in form of blogs are as follows:

    The session is to share the these patterns and more (when to go for distributed Agile and when not etc)

  • Sriram Narayan
    Sriram Narayan
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    Good engineering practices and fail-fast, iterative, low-ceremony processes help achieve team level agility. They are necessary but not sufficient to scale agility across the IT organization. In this talk, I'll address what else is needed and why. In particular, I'll address:

    1. Why plan-driven IT projects are a bad idea why we need value-driven projects instead
    2. Why a matrix org is a bad idea for IT and why we need cross-functional teams instead
    3. Why IT budgeting needs to change from being project-based to being team-capacity based
  • Liked Pooja Uppalapati
    keyboard_arrow_down

    Scaling Agile in a Mainframe Product Development Organization

    Pooja Uppalapati
    Pooja Uppalapati
    Ravindra Chebiyam
    Ravindra Chebiyam
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    Agile transformation in any organization will go through myriad of challenges that involves people, existing organization culture, technology/domain etc. Instead of seeing these challenges as obstacles, if you view them as opportunities to grow and improve, transformation will be more impactful and long-lasting. If neglected, the very same obstacles would severely damage the motivation and trust of employees.

    In this experience report we would like to walk you through the agile transformation journey in a Mainframe product development enterprise by unraveling the challenges and the remediation steps that has helped us in keeping this journey alive. Specifically we would like to touch upon 

    1. Self-organizing teams
      • Resistance to change
      • Culture shift
    2. HR
      • Lack of role clarity and
      • Effective R&R in agile space
    3. Agile Engineering Practices adopted in Mainframe product development
      • Unit test automation
      • Continuous Integration

    Along the presentation we’ll highlight few anti-patterns and the effects of ignoring them.

  • Liked Vinod Kumaar R
    keyboard_arrow_down

    Build it like sports teams

    Vinod Kumaar R
    Vinod Kumaar R
    schedule 2 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    Is it easy to get a crash course in football by Pele or Maradona for a week and produce a world cup winning football team?

    Answer is NO. Then why do lots of people in the corporate world think of hiring scrum trainers & expert developers to train their team for a week and then expect their team to undergo a transformation at a magical scale?

    German football team made it a point to transform their team and it took them a lots of years before they were able to reach the pinnacle. A quick side by side comparison of what is causing agile transformation to fail.

    Vision

    Football: Someone was there owning this entire transformation, the German football association spent a lot of time identifying talent in their teens and groomed them.

    Office: In the corporate world switching jobs every few years have become common, but there is no passing on of the context, resulting in the new person taking charge, starting from all over again, as well as frustrating existing good performers who have to rebuild the perception.

    Infrastructure

    Football: Players expecting state of the art training facilities, fitness programs and new shoes are not a luxury, it is a necessity.

    Office: Computers have become so cheap compared to the salaries, yet the policy of providing the best tools and good work environment are archaic.

    Coach vs Management

    Football: Coaches are given their due powers to help the team achieve the goal. It is very easy for anyone to comment on how professionals should play their game, there would be no use adhering to the metrics if the team cannot win. Winning is the only measure for management.

    Office: Often coaches are seen as part of the management or management tries to heavily influence coaching which results in a team which will work either for metrics or to please higher ups without the actual result that it had aimed for.

    Training

    Football: Just the ability to kick the ball does not make a footballer. Training will be introduced to increase physical strength & stamina, better mental wellness, injury prevention, tactics and strategy.  A heavy investment is made in the training facilities.

    Office: In the software industry a generation is about 2-3 years. Computer science degrees are nowhere near what is state of the art in the industry. At many places the on boarding process is either very shallow or not up to date with the recent developments, leaving people to learn most of the things hard way. Given too many things to learn and the information overload, this results in inefficient learning and application of knowledge on the job. We need to prepare people to find answers that are not available on Google.

    Team composition

    Football: Rookies don’t learn by watching greats from the bench, instead they play along with the veterans. Every sports team makes sure to have the right composition with a mix of rookies, emerging players and veterans. That is how they sustain a winning team.

    Office: Architects and Leads often do not code or are not part of the team every day, this means that most of the time the team just looks up to for advice or waits for reviews. There should be a good mix of people at all experience level so that there are enough people to try new things, enough people who have mastered few things and enough people who challenge change.

    Above all – Persistence