Everything Is Better When We Stick Together: Building Team Working Agreements

schedule 02:00 PM - 03:30 PM place Esquire

Whether a team is brand-new or seasoned veterans at working together, explicitly defining and/or refining a team working agreement will help the team to align on how they will work together effectively to meet their common goal. In this fast-paced hands-on session, participants will go through the process of building a team working agreement using LEGO Serious Play (LSP).

Creating a team working agreement helps team members set the stage for effective communication and high performance by making assumptions about ‘what really matters to us’ and ‘how we will work together?’ explicit and negotiable.  Great working agreements address some difficult topics - what values do we share? how do we want to deal with conflict when it comes up? how will we handle problems within the team? - which are often challenging to discuss openly and honestly, especially when a team is first assembled.  

This session will show you how to use LEGO Serious Play to encourage a frank and fearless discussion in order to kickstart these discussions so that a team can quickly create a powerful set of simple guiding principles for working together.  Participants will learn about the importance of team working agreements in creating team cohesion and common understanding of shared values and operational guidelines, and experience hands-on how to use the LEGO Serious Play cycle of build-share-reflect to have a participatory discussion to identify shared values, explore reactions to conflict, and build a set of simple guiding principles.

 

 
7 favorite thumb_down thumb_up 1 comment visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

This will be a very interactive workshop composed primarily of facilitated exercises and minimal presentation elements.

  • Intro to team agreements
  • Intro to LEGO Serious Play etiquette
  • Builds - who am I? what's my superpower? how do I perceive conflict? how do we work together? how do we agree to disagree?
  • Closing, Q&A

Learning Outcome

Participants will:

1) learn about the importance of team working agreements in creating team cohesion and common understanding of shared values and operational guidelines

2) explore perceptions of conflict within the team and consider how to address conflict before it happens

3) experience hands-on how to use the LEGO Serious Play cycle of build-share-reflect to have a participatory discussion to identify shared values and build a set of simple guiding principles.

 

 

Target Audience

Any team member or their managers

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • ☕ J. B. Rainsberger
    By ☕ J. B. Rainsberger  ~  1 year ago
    reply Reply

    I love the idea of this session, both the style and the content, but the first sentence especially put me to sleep. I recommend leading with a problem that working agreements solves, such as articulating what we agree to do to avoid awkward arguments when one of us isn't doing it or making it clear when we're not all rowing in the same direction. I think that this is an under-developed skill and I want to see this session pull in a lot of people. By the necks, if necessary.

    What wonderful thing will happen when we start systematically articulating working agreements? What horrible thing lurks around the corner if we don't?


  • Liked Rajat Talwar
    keyboard_arrow_down

    Rajat Talwar - Pains and Gains of being a Full Stack Developer

    45 mins
    Experience Report
    Intermediate

    As the industry is shifting towards an Agile (Continuous Delivery) style for developing products and services, (whether startups or large established organisation), everyone today has to thrive by innovating and adapting to the latest trends in technology. They have to keep themselves ahead in the race to delight customers. Full stack developers are key players in experimenting and delivering value consistently using varied tools and technologies throughout the stack.

    In this session I'll be share my journey of how I became a full-stack developer. Hopefully this will help others understand how they can target and plan to gradually become a full stack developer in their respective teams.

    Also I'll highlight the following topics:

    • What is the importance of a full stack dev?
    • What tools/resources/languages in my experience work best for full stack developers?
    • Downsides of being a full stack developer!
  • Liked Ellen Grove
    keyboard_arrow_down

    Ellen Grove - Games for Learning about Conflict Resolution

    90 mins
    Workshop
    Beginner

    Scaling Agile across the enterprise can also scale up or create new organizational conflicts: groups that are accustomed to working in their own silos struggle to find ways to identify their shared interests and collaborate effectively.  Equipping team members with effective conflict resolution skills is important in helping everyone navigate change successfully.

    Conflict isn’t inherently a bad thing – it’s inevitable when people are working closely together on things that they care about. In fact, diverging viewpoints can bring new insights to help teams move forward and create something new. Dealing with conflict head-on is challenging for many people, yet few organizations and teams spend time explicitly considering “how will we work together when things get rocky?” Teams need to build the skills to be able to navigate through rough times together and come out with win-win solutions.

    This workshop will present useful models for considering conflict supported by games teams can use to develop and practice conflict resolution skills. The models address underlying drivers of conflict, modes for responding to conflict, assessing conflict severity to determine appropriate interventions, and the patterns of principled negotiation. The games build on the concepts to help participants gain insight and develop important skills in a non-intimidating and memorable way.

  • 20 mins
    Experience Report
    Intermediate

    The role of Leadership in organisation's Agile transformation is a critical piece. Yet many organisations struggle to find the right balance between top-down vs. grass-root transformation. I would like to share an experience where we were able to achieve fairly good grass-root movement, but had serious challenges building the agile mindset at the leadership level. While the leadership was trying to help with the best of their intentions, certain actions, behaviours and patterns did affect the spirit of agility. If you are keen to hear about typical leadership anti-patterns during agile transformation and some pointers on how to avoid them, this session is for you.

  • 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 Pavel Dabrytski
    keyboard_arrow_down

    Pavel Dabrytski - Agile Economics: Contracts, Budgets, Capitalization

    Pavel Dabrytski
    Pavel Dabrytski
    Agile Coach
    Think Agile
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Advanced

    How much does one story point cost? Is Sprint 0 an expense or an asset? Can you run Scrum with a fixed-cost contract? Agile challenges the existing approach to financial aspects of running projects: i.e. budgeting, forecasting, financial planning and vendor contracts.

    Applying new financial models becomes increasingly important for larger organisations adopting Agile. While they are going through an Agile transformation, they also need to maintain transparent financial governance and reporting. Shareholders would not be too excited about messy Annual Financial Statements.

    Join me if you would like to know more about Agile Economics. No financial degree is required and all the content explained in plain English with plenty of pictures!

  • 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.

  • Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 2 years ago
    Sold Out!
    45 mins
    Keynote
    Advanced

    On Agile teams, collaboration is the way of life. Our leaders want their team members to work closely with each other, have shared goals and even think as one entity. Why? Because we believe that collaboration leads to happier, more productive teams that can build innovative products/services.

    It's strange that companies use the word collaboration very tightly with innovation. Collaboration is based on consensus building, which rarely leads to visionary or revolutionary products/services. Innovative/disruptive concepts require people to independently test out divergent ideas without getting caught up in collaborative boardroom meetings.

    In this presentation, Naresh Jain explores the scary, unspoken side of collaboration and explains in what context, collaboration can be extremely important; and when it can get in the way or be a total waste of time.

  • Liked Ellen Grove
    keyboard_arrow_down

    Ellen Grove - Lifting Off

    Ellen Grove
    Ellen Grove
    Agile Coach and Trainer
    Agile Partnership
    Steve Holyer
    Steve Holyer
    Agile Coach Trainer and Consultant
    Steve Holyer and Associates
    schedule 1 year ago
    Sold Out!
    480 mins
    Workshop
    Intermediate

    Using play to build a better beginning through Agile Chartering

    Better teams create better outcomes.  A liftoff (as described in the book Liftoff by Diana Larsen and Ainsley Nies) at the outset of a new endeavour helps teams set the stage for betterness by cocreating a shared understanding of purpose, establishing alignment and understanding the context of the work they will do together.  While the activities to include in a Lift Off will vary according to team and context, the practice of Agile Chartering - collaboratively developing a lightweight yet effective roadmap for the project and the team - is key to aligning and inspiring people to do better work together.

    The purpose of an Agile Chartering workshop is to give all stakeholders of a project a voice and the opportunity to co-create a common understanding of the project dynamics, its purpose and context. It creates co-ownership of the project within the project team and thereby higher commitment to the project goals.

    In this workshop, we will explore the objectives of Agile Chartering and foster a playful approach to doing this work. We'll talk about what kinds of games can be used to cocreate Purpose, Alignment and Context with a team, and run at least one game that can be used for each of the elements of an Agile Charter

  • Liked Sean Dunn
    keyboard_arrow_down

    Sean Dunn - To Estimate or #NoEstimates, That is the Question

    45 mins
    Talk
    Intermediate

    The #NoEstmates twitter hashtag was intended by Woody Zuill "..for the topic of exploring alternatives to estimates [of time, effort, cost] for making decisions in software development. That is, ways to make decisions with ‘No Estimates’."  Based on twitter traffic it has been successful at generating activity.  It's a bit debatable as to whether it has really spawned much exploration.  In this talk Todd will actually do some exploration using real data from over 50 projects at companies ranging from startups to large enterprises.  In addition to the analysis of the data, Todd was able to build a simulation model of the software development process to both replicate the data to and explore the conditions under which estimates add value and when they do not.  Based on the findings from the data and the simulations, along with an analysis of the types of business decisions that organizations need to make, Todd will provide some pragmatic advice for estimators and #NoEstimators alike.

  • Liked Krzysztof Czajka
    keyboard_arrow_down

    Krzysztof Czajka - How fudge candies catalysed feedback and engagement? Case study of successful experiment.

    20 mins
    Experience Report
    Advanced

    What is it about?

    This is a story about building appreciation and feedforward culture in the organization.

    I am going to talk about a bottom-up experiment based on Jurgen Appelo's Merit Money, conduced in the biggest e-commerce company in Poland - Allegro Group. It is a story about learning throughout an Agile experiment to get the most out of it. Primarily the experiment was intended to challenge the existing bonus system based on forced ranking. It turned into appreciation and feedback system with some sweets involved. 

    This feedback system has grown to more that 230 people involved from 3 different physical locations and still grows virally. We made a structure in which there is a coordinator in each location. If at least part of scrum team plays the game, SM is the first line contact. He distributes credits and exchanges them for sweets. Also cooperates with coordinator who is responsible for making sure system works well in his location.
    Iterations are now 2 weeks. We introduced a requirement that credit has to be filled in with short description what you thank for, in order to be exchanged. This was to promote written thank you’s and avoid situations where people hand over credits just to get sweets.
    Also every quarter we change credits appearance so that the previous credits cannot be exchanged for sweets. This is to set a time box and “flush the system”.

    Is it for me?

    Do you feel your team could be more engaged in their work? Trying to get rid of silos in your organization? Then this is for you.

    Get inspired by this simple game, in which there are several instant feedback loops, fun, gambling and sweet prizes.

    Oh, I forgot... and you'll find an answer on why we call it Fudge Candies.

  • Fabiola Eyholzer
    Fabiola Eyholzer
    CEO
    Just Leading Solutions
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    Inspired, empowered, and engaged people are the heart and soul of Agile – and HR.

    Transforming your organization into an agile enterprise is no small deed. And it does not matter where you are on your way towards embracing agility on all levels. There will be a time when you need to align your people solutions with the mindset and demands of agile people and organizations. We will talk about how to turn your Human Resources into Agile People Operations and boost your agility. 

    Join this session to

    • gain valuable insights into the world of Human Resource Management
    • recognize the impact of Agile HR practices through stories and examples
    • discover why Agile needs HR and vice versa
    • learn about People solutions in Agile Enterprises
  • Liked Dan R Greening
    keyboard_arrow_down

    Dan R Greening - Develop Agile Managers, or Agile Dies

    Dan R Greening
    Dan R Greening
    Managing Director
    Senex Rex LLC
    schedule 2 years ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    We need good agile managers, if we hope to sustain rapid adaptation and innovation. Agile managers deliver coherent chunks of value, rapidly adapt to changing circumstances, and experiment with new approaches. Because they depend on their teams to support their own agile needs, they demand agility from their teams.

    Management talent is rare, and agile management talent even rarer. Gallup has surveyed thousands of managers, finding that low-talent managers, unfortunately a majority, create dysfunctional teams, build unsupported products and produce little sustained value. So developing high-talent agile managers matters.

    Agile managers adopt five agile base patterns for themselves: they measure economic progress, proactively experiment to improve, limit work-in-process by time and costradiate collective responsibility, and collaboratively solve systemic problems. It turns out these patterns have analogues in high-talent (non-agile) manager talents. That’s a relief, because we can focus agile manager development on extending the talents good managers already have.

    In this workshop, we'll explore agile manager characteristics, and management dysfunctions. We'll create approaches to move good general managers to good agile managers. We'll explore strategies for dealing with mediocre managers, whether they are peers or superiors. And we'll learning how to improve our own management agility.

    This talk comes from well-documented experience. I have held management roles from Team Lead through VP Engineering and CEO. At Citrix, Skype, Amway and other large companies, I used agile to help manage a 24-member user-experience department, three different agile coach teams and a 50-member data science department. Much of this work has been described in conference papers and detailed blog posts.

     

  • Liked Nilesh Kulkarni
    keyboard_arrow_down

    Nilesh Kulkarni - Scaling agile - what, how, when

    Nilesh Kulkarni
    Nilesh Kulkarni
    Senior manager PMO
    Allscripts
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    This session will focus on what are the aspects organizations should consider when they want to scale agile implementation in organization.  There are several frameworks out there like SAFe, LeSS, Spotify, and so on. what is it that organization is trying to achieve and how a systematic approach of scaled agile implementation can help the organization.

    Attendees will be able to understand what aspects should be considered before organization decides to scale agile.  How to scale agile and when to do it largely depends on what organization is trying to achieve. Each organization is operating it in different way so there is no defined formula or framework that will work for all. But guidelines from this session will help the members to identify their needs and then take further action.  These guidelines can help the organization to successfully scale agile irrespective of which framework is selected.

     

    Areas covered in this session are:

    • what are the driving principles while scaling agile

    • Where to start

    • Which Framework should I select?

    • Organizational changes

    • Role of managers?

    • Scaling communication

    • Scaling engineering practices

    • Scaling Product Management role

    • Roll out plan

    • Implement the plan

    • Grow and evolve

    This session will be mix of talk, case study and experience report.

  • Liked Prasad
    keyboard_arrow_down

    Prasad - Movers & Shakers of Enterprise Agility

    Prasad
    Prasad
    Prasad
    HolleyHolland
    schedule 1 year ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    With business agility being the new watchword in senior management circles, many enterprises are looking for ways to adopt this into their technology practices. However, it is imperative for such an initiative to go beyond the mere adoption of agile in a few projects.

    To run an effective enterprise there are different  systems and applications in every value streams.  There is no one size fit for all. There could be a broad pattern/ classification  like 'Money making applications' 'Applications which bring efficiencies to their operation' and 'Applications which are critical from a regulation and compliance perspective'.

    My session is going to focus on experience and patterns that helped in  achieving Agility in the above categories of applications   with respect to  key 'Movers & Shakers' in the system.  

  • Liked Dan Montgomery
    keyboard_arrow_down

    Dan Montgomery - OKRs - Building Strategic Agility in Your Enterprise

    90 mins
    Workshop
    Executive

    Agile is a radical evolution in how we think about work flow – AND how we engage people’s intelligence and commitment in the process. So now we’re doing a faster, better, more engaging job of ….. What? And Why? The “What” and “Why” questions are the stuff of strategy – purpose, vision, customer value, competitive advantage and sustainable financial performance.

     OKRs (Objectives and Key Results) are the missing link between agile practices and alignment with the larger mission and purpose of your enterprise. Developed in Silicon Valley and adopted by industry leaders including Intel, Google and LinkedIn, OKRs are the framework for individuals and teams to set their own goals and align agile action with overall business strategy.

     In this workshop, we will explore

    • How business strategy is evolving from a waterfall model to an agile approach
    • Extending the idea of “cadence” to include ceremonies for enterprise-wide strategic conversations that create “line of sight” for individuals and teams
    • The use of OKRs as goalposts for strategic alignment and agile action
  • Liked ShriKant Vashishtha
    keyboard_arrow_down

    ShriKant Vashishtha - Specification by Example Explained

    45 mins
    Talk
    Intermediate

    What if you could write functional tests without writing a single line of application code? What if those tests are written in plain English (so that anybody could understand) but still it's executable spec or source-code? What if you could generate the documentation from live production source code? Now you don't need to update the requirement doc all the time.

    What's Specification by Example? Is it different compared to BDD? Who all participate in defining these specifications? Are functional tests and functional specifications same? These are the questions this session tries to answer.

  • Liked Shervon Fernandopulle
    keyboard_arrow_down

    Shervon Fernandopulle - Emotional Intelligence 3.0 - Building Relationships in a Distributed Setting

    45 mins
    Talk
    Intermediate

    Agile manifesto highlights the importance of individuals and interactions over processes and tools and customer collaboration over contract negotiation, which implies the importance of human relationships over rationality. Research by Danial Goleman and scholars from Yale University have proven how critical is the role of Emotional Intelligence in building relationships and overall performance of individuals and teams in corporate setting.

    Understanding people and their emotions will be challenging, controlling self-emotions will be the next step and building relationship by controlling emotions of the other would be more challenging. But understanding emotions in a distributed setting when people don’t face each other will be the most challenging scenario. But people will remain emotional; hence Emotional Intelligence remains extremely important even in a distributed setting to understand each other and build relationship.       

    During this session I will discuss about the concept of emotional intelligence, latest research findings, how emotional intelligence could be applied by individuals and teams, challenges in a distributed setting and different approaches we have used to make people understand from a distance.

  • Liked Vinay Krishna
    keyboard_arrow_down

    Vinay Krishna - BDD - an effective way to collaborate among 3 amigos - Testing is just a by product

    Vinay Krishna
    Vinay Krishna
    Agile / DevOps Practitioner
    Self
    schedule 2 years ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    A common misinterpretation is that BDD is another way to automate the functional testing or just a synonym to Acceptance Test Driven Development (ATDD). However, it’s not correct understanding. BDD doesn’t talk about testing rather it focus on development which is driven by expected behaviour of application/system. It helps to share the understanding by examples among three amigos (BAs, Developers and Testers) and helps to explore unknown. It describes what business/end users want the system to do by talking through example behavior.

    In this workshop, the actual concept of BDD is explained using case study of various real-time projects. It also covers the myths, challenges, benefits and best practices along with tools used to adopt it.

  • Liked Vijay Bandaru
    keyboard_arrow_down

    Vijay Bandaru - Let's solve a practical problem together using Lean Principles

    Vijay Bandaru
    Vijay Bandaru
    Agile Coach
    IVY Comptech
    schedule 2 years ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    This topic has popped up in my mind through an observation of a practical problem I found yesterday. I thought to apply some lean principles to resolve this problem. I am proposing the problem statement here in this forum and the idea is to have an interactive workshop to come up with possible solutions to address this problem using Lean thinking/principles. Here are the details.

    Yesterday I visited Hyderabad Zoo (Nehru zoological Park) along with my cousins families. We are 12 members including adults and children. Earlier till November 2014, visitors cars were directly allowed inside with an additional fee of 200 rupees per car. I visited the Zoo before 2014 November and it was an awesome experience going by our own car and stop wherever you want for however long you want. Now, as they stopped allowing private cars inside, they arranged electric cars rides inside the Zoo. Below is the process and problem statement that I observed.

    1. The fee for one adult is 50 Rs and child is 30 Rs for Electric car

    2. Tickets will be given only at the entrance of the Zoo that is located outside the compound wall (You will not know how many members are waiting for electric cars inside)

    3. Tickets once sold cannot be refunded or exchanged

    4. There are limited electric cars available to cater the crowd (I got the info that around 25 cars)

    5. Each ride takes 40 minutes. It will stop at various locations where you can get down the car and visit the animals and come back to go to next stop

    6. Each car can take up to 12 members including the driver (

    7. You have to get onto the car at only one starting location and get down at the same point after the ride is complete. If you want to give away the ride in between its fine up to you

     

    The problems I observed and want to solve these problems by applying lean principles:

    1. At the time of buying the tickets:

         a. I did not have any clue on how many cars are there inside

         b. How long each trip takes

         c. How many members are in waiting

         d. Whether I can take the car and leave it at some place and visit the animals and by the time I come back after my visit there can be some other car available to take me to next stop or not

    2. I had to wait more than 1.5 hours to get my turn to have a car available

    3. The driver told that if I can give him 300 Extra we can take our own time to visit and he will not mind (this is the primary cause of the long queues I observed)

    4. Weekend visitors are more than 2 times of weekday visitors

    5. The queue is not properly managed so at times I observed people are joining in the middle of the queue and making it even more worst

    What I want to resolve:

    1. Reduce the waiting time

    2. Address the loophole of extending the ride by giving bribe to the car driver

    3. Address the queue management inconsistencies

  • Liked Krishnamurty VG Pammi
    keyboard_arrow_down

    Krishnamurty VG Pammi - Lean Scrum - The need of the hour

    Krishnamurty VG Pammi
    Krishnamurty VG Pammi
    Agile Coach
    IVY Comptech
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The 2015 state of scrum report published by Scrum Alliance states that the outlook of scrum is highly favourable. Virtually all consider it likely that their organization will use scrum in future. While this is good, the survey also noted one of the key challenges observed by survey respondents as “Product owners and teams were just not willing and/or enthusiastic about Scrum best practices”. Thus, although scrum methodologies have greatly increased productivity, scrum is not without its problems. We need to quickly address this gap.

    Keeping scrum values at the core, scrum methodology is mostly visible to teams on the ground in terms of three pillars (1) Scrum roles (2) Scrum artifacts and (3) Scrum events. While Scrum has kept scrum roles and scrum artifacts lean, it has empowered teams on the ground to learn the art of performing scrum. Scrum prescribed guidance on scrum events with clear purpose, frequency, maximum duration and recommended attendees. It recommends teams to learn the art of performing scrum events through their experience stating “scrum is easy to understand and difficult to implement”

    While some scrum teams mastered this art, I find most of the scrum teams are still struggling in this process. I come across situations where teams are not finding scrum events interesting primarily because they find these events unproductive. The result is that we see less interactions and cooperation from the teams during scrum events. This is impacting basic agile manifesto “Individuals and interactions over processes and tools". In net, there is no surprise when product owners and teams were just not willing and/or enthusiastic about Scrum best practices.

    Lean Scrum is the need of the hour. As part of lean scrum, we will adopt scrum methodology at the core and we implement lean framework to address the pain areas witnessed by teams

    As part of this talk, I will share my experiential insights on

    1. Outlook of scrum is highly favourable. Although scrum methodologies have greatly increased productivity, scrum is not without its problems. We need to quickly address these gaps
    2. While scrum has kept scrum roles and scrum artifacts lean, it has empowered teams on the ground to learn the art of performing scrum events. Are we keeping these events lean and Valuable?
    3. Lean scrum – The need of the hour
    4. What is Lean Scrum
    5. Anti-Patterns/Most frequently faced challenges/ wastes experienced by scrum teams in each of the scrum events (case findings based on my experience)
    6. Where do the scrum teams stand on "expected scrum patterns" in each of the scrum events (case findings based on my experience)
    7. Leverage "Lean Framework" to craft scrum events towards value generation. How to draw "AS-IS" and "TO-BE" Value stream management maps for two scrum events.
    8. Leverage "Lean framework" to help scrum teams to learn the art of performing scrum events through realizing value and enhancing their reach on "expected scrum patterns".
    9. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software” The term value is increasingly becoming starting point of what we do. We need to keep questioning everything we do using customer value generation as the yard stick

    Unless, we drive scrum events towards value generation by continuously eliminating waste/ anti patterns, there is no surprise that “Product owners and teams were just not willing and/or enthusiastic about Scrum best practices” as observed by "The 2015 state of scrum" report.

    This is where Lean-scrum could prove to be powerful...