Agile transformations are no child's play. There is inertia, restlessness, impatience and the constant desire to run away. Traits that anyone who has been a parent to little kids has encountered, and learnt in their own way how to handle.

This session looks at parallels between parenting and trying to influence teams through an agile transformation. We look at some of the things that successful parents do that can be done by leaders trying to take their teams through a transformation.

Because if teams sometimes behave like children, the leader needs to be a parent too!

 
5 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

- What are some of the challenges teams facing in an agile transformation?

- What frustrates the leader?

- What frustrates a parent?

- What do successful parents do?

- Bringing Parenting into Agile transformations

Learning Outcome

This session provides some food for thought for leaders struggling with the people element of their transformations. At the end of the day, teams are made of people and the success of any Agile transformation hinges on their engagement and involvement into the process.

This session mixes humor with some intuitiveness to share insights into some things parents do which are equally helpful when working with teams and getting them to follow your path.

Target Audience

Business leaders, Managers, Scrum masters

Prerequisite

Nothing in particular. An open mind and some experience with managing people through an agile transformation.

schedule Submitted 5 months ago

Comments Subscribe to Comments

comment Comment on this Submission

  • Liked Aarron Walter
    keyboard_arrow_down

    Aarron Walter - Story First

    45 Mins
    Talk
    Intermediate

    Story is a profoundly important device to unite design teams around a shared product vision. This powerful communication tool helps us retain information and empathize with others. As companies scale and teams sprint through product iterations, it’s easy to lose sight of how your product should fit into the lives of your customers. The best way to keep everyone pointed in the right direction is with a clear, compelling story—a story that will unite and guide teams towards success.

    But how do we fold storytelling into our design practice? Aarron Walter uses real-world stories of product teams at Disney, Apple, Airbnb, Twitter, and more to show how storytelling improves team communications and elevates design practice.

  • Liked Bernie Maloney
    keyboard_arrow_down

    Bernie Maloney - Wipeout! Make *New* Mistakes

    Bernie Maloney
    Bernie Maloney
    Agile Coach
    Persistent Systems
    schedule 6 months ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    Ever feel like the market moves faster than your marketing team? Or, wonder how flexible your finance (& leadership!) teams would really be if self-direction glitched and blew $1M? Organizations introduce Agile believing it will lead in part to greater responsiveness and resiliency. Yet, why do so many fail to achieve those outcomes?

    It isn’t just that they’re structured and operated by default along hierarchical lines rather than by design for iterative work. Achieving the full benefits of Agile comes from shifting the culture and mindset of a whole organization, sometimes as radically as encouraging it to “Make New Mistakes.” This very philosophy was a driver in the fastest division in HP’s history to reach $1B, a hardware division that was focused on manufacturing operations, with razor thin margins, and markets that changed 3x faster than the development lead time.

    Through a series of short stories and exercises, attendees will explore 5 practices from that business which led to roaring success. We’ll probe their parallels in Lean / Agile practice. With each one, you’ll briefly self-inspect the state of your own organization, as well as create a backlog you can use to adapt in your “real world” beyond the conference.

    Do you have, or want, a vision that takes you beyond high performing teams, to a high performing, resilient business? Come hear how you can help your organization shift from mechanics that “do” Agile, and walk away with a feel for what’s possible when not just development, but a whole organization surfs the flow of “being” Agile.

  • Liked Vishal Prasad
    keyboard_arrow_down

    Vishal Prasad - SLICE - The Experimentation Framework

    45 Mins
    Talk
    Intermediate

    Agile Principle # 12 defines that at regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. From Scrum to Kanban and other agile frameworks, this is accomplished through retrospectives and continuos improvement processes. The key to being a successful agile practitioner is to identify areas of improvement and then experiment ways of improving it. But it doesn't stop there; positive improvements ultimately become success stories for other teams and motivates them to experiment with newer ideas which eventually leads to innovation. A negative outcome isn't bad either since it adds to the experience of situations where ideas may not apply. Thus the key to this process lies in being a child, an explorer, and inculcate an experimentation mindset. The SLICE framework addresses this in the following way:

    • S hare: Share an area of improvement
    • L earn: Explore the area for ways of improvement
    • I mplement: Search & apply the learning to identify the success factors
    • C ollateral: Publish blogs, white papers, presentations, etc. as observations of the implementation
    • E xpansion: Grow, Seed, and Split in order to explore new venues for success

    In this workshop, I create an environment that inculcates an experimentation mindset and utilize the SLICE framework to drive the exploration.

  • Liked Alhad Akole
    keyboard_arrow_down

    Alhad Akole - Rubber Meets the Road!

    Alhad Akole
    Alhad Akole
    Agile Coach
    Shell India Markets Ltd
    schedule 5 months ago
    Sold Out!
    45 Mins
    Talk
    Advanced

    Session is for Lean Agile Leaders which will help them manage portfolio Agile way.

    Lean Agile principles when applied to portfolio management, will help you keep pace with fast changing business by giving you a disciplined approach to implementing you strategic vision as realistic work plan.

    Keeping up with the new pace of change requires light weight processes and an adaptive mindset.

    It will cover the following main pillars of Agile Portfolio Management

    - Work Management

    - Capacity Management

    - Financial Management

    - Value Management

    - Continuous planning

    - Continuous Visibility

    APM session will help you look at the portfolio in different way; and help you outpace changing business.

  • Liked Nilesh Kulkarni
    keyboard_arrow_down

    Nilesh Kulkarni - Outcome Based Agile Coaching

    45 Mins
    Workshop
    Intermediate

    Session name - Outcome based agile coaching

    We all want to become good agile coach. But what does that mean? How do you get better outcome from your agile coaching sessions? In this session, participants will experience how to improve outcome of your coaching session. Some areas we will focus in this session are output Vs outcome, why, what, how of coaching, how to make coaching outcome etc.

    This will be a hands on workshop with very minimal guidance from facilitator. Participants will have experiential learning through the activities to understand how to align agile coaching to deliver maximum impact on business outcome.

  • Liked Gaurav Rastogi
    keyboard_arrow_down

    Gaurav Rastogi - Agile Vendor Management Manifesto

    45 Mins
    Talk
    Executive

    Want to discuss and share the Manifesto which a group of coaches including myself have written.

    Please refer to www.vendormanagementmanifesto.org for details

    1.1 The Governance
    The delivery team is governed by contracts. There are 2 types of contract we will be considering
    •The Master Contract : This is a contract signed between the Customer and Supplier Management teams and governs the entire set of Scrum projects being executed.
    •The individual work order level contracts: This is a contract which will govern the detailed work to be done by teams.

    This manifesto will take into account both the type of contract

    1.2 The Roles
    The roles covered under this Manifesto are as follows
    The Customer Management This is the management team of the customer
    The Vendor Management Team Vendor Management team will work on behalf of the Customer Management team in preparing the contract and negotiating the same with the Supplier’s management
    The Team The team will consist of multiple Scrum teams working on the projects governed under the Master Contract. They will end up working under the individual Work Orders signed up with the customer.
    The Supplier Management The Supplier Management team will negotiate the terms and conditions of the Master Contract of the contract along with the The Customer Management team (and the Vendor Management team).

    1.3 The Objective of this Manifesto

    The Objective of this Manifesto is to define guiding principles around the Customer-Supplier working environment with regards to working on Scrum projects. The assumptions made are
    •The environment is customer-supplier (i.e. an outsourced environment)
    •The environment is distributed and may not be co-located
    •The environment involves multiple vendors

    The Customers and Suppliers are integrated elements of a working environment in a project. The Customers and Suppliers will work together with a common goal and that is “Producing Value for the End Customer”. This manifesto supports the Agile Manifesto Value “Customer Collaboration over Contract Negotiation”.

    There are 12 principles which will support the Agile Value and are presented below in a format of Left over Right. The items on the left are valued more than the ones on the right.

  • Liked Pavel Dabrytski
    keyboard_arrow_down

    Pavel Dabrytski - Psychology of Coaching: Understanding Science of Change

    Pavel Dabrytski
    Pavel Dabrytski
    Agile Coach
    Think Agile
    schedule 5 months ago
    Sold Out!
    90 Mins
    Workshop
    Advanced

    In October 2016 I received a call, "Hey dude, I don’t know nothing about Agile, but I need to become an Agile coach a-s-a-p – my company just got a new contract." I laughed for a second, explained that it takes a bit longer than a week to learn to coach, and wished him luck. I also knew that, shortly, he would be walking into his customer's office in this new role.

    Agile Coach is the new black! But how can you, a good coach, stand out from the crowd of less competent peers? Let me offer you this workshop to explore the science of coaching and the ways in which it works. We start with concepts of neuroplasticity and the brain processes of creating new neuron pathways. Then we move to motivation and learn which type is the best. Finally, we finish with the discussion on brain activation states which we practice in a few short exercises. By understanding the new field of coaching psychology, you will become a better practitioner.

    I am an affiliate member of the Institute of Coaching at McLean Hospital, the Harvard Medical School affiliate. I studied coaching psychology at Harvard Extension School.

  • Liked Laxman
    keyboard_arrow_down

    Laxman - Playshop on Strengthening Customer Centricity through Digital Transformation

    90 Mins
    Workshop
    Intermediate

    Business organizations are seeing seismic changes, and the business
    landscape is continuing to evolve. In an age of rapid digital
    transformation, customers are choosing a myriad of ways to interact
    with your organizations. It is thus imperative that organizations stay
    ahead of the curve to achieve its strategic goals in service excellence.

    The playshop will be dynamic, highly engaging using a Hands-
    On, Minds-On Learning approach to producing a deeper, more meaningful understanding through an experiential process.

    Building a customer-centric organization by pushing customer-centric
    culture to the next level. Customer Centricity is all about a Customer
    Centric Culture. The responsibility of Customer Centricity in an
    organization is with the employees.

    Customer-centric culture aligns your product and service with current and future needs of a defined set of customers to maximize mutual long-term financial value. It depends on an organization’s capability to understand, predict and respond to customer, market and competitor dynamics. A Customer-Centric Culture transcends individual departments and functions; it integrates the way all employees behave and perform.

  • Liked Peter Scobie
    keyboard_arrow_down

    Peter Scobie - The Team Playbook: A Recipe for Healthy Teams

    Peter Scobie
    Peter Scobie
    Program Manager
    Atlassian
    schedule 5 months ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    The benefits of a high performing team are endless. They are autonomous, empowered, responsible and effective.

    At Atlassian, we've pioneered the Team Playbook, which is our way of scaling teams by getting smarter, not bigger, and driving a culture of continual improvement. Utilised by hundreds of teams within Atlassian, we've made our secret sauce not so secret. Don't come to this session for a lesson on theory...come to this session to hear the philosophies and principles of the Team Playbook from Peter Scobie, Program Manager/Team Doctor. You'll leave this session invigorated, engaged and ready to take action.

  • Liked Fennande van der Meulen
    keyboard_arrow_down

    Fennande van der Meulen / Maartje Wolff - How to build good habits in an Agile Team

    90 Mins
    Workshop
    Beginner

    Introduction

    Culture eats strategy for breakfast, said Peter Drucker. We all agree to that. If our organisational culture is not building up to our goals, we will never reach them. The main question is, how can you create an organisational and team culture that contributes to your goals, to productivity and success? The key for change is to form the right habits, within our agile teams. Like exercising regularly and losing weight you can develop habits for being healthy, happy, more productive and successful at work. Therefore it is important to understand the human nature and its potential for transformation. In this workshop participants get all the insights and best practices to develop habits for an happy and fulfilling (work)life and organisational culture.

  • Liked Kiran Chhabra
    keyboard_arrow_down

    Kiran Chhabra / Atulya Mahajan - The Subject They Don’t Teach : What’s Post-Deployment

    45 Mins
    Talk
    Intermediate
    When we talk about Agile methodologies then focus on just delivery is not enough. There is life beyond delivery, and very often a product makes or breaks its destiny during that phase.
    The Devops process itself is more than Continous Integration/Deployment, and it is important to know the other Cs of Continuous Monitoring and Continuous Operations as well.
    We will share a case study for a team that had to sustain fast-paced releases with a large customer base. Agile, Continuous Integration and Continuous Delivery were not just fads for them but needs for survival.
    This system turned out to be a big success story and thus we went ahead and replicated the model in the rest of the organisation.
  • Liked Mangalam Nandakumar
    keyboard_arrow_down

    Mangalam Nandakumar - Why story points make no sense for a product company

    45 Mins
    Talk
    Advanced

    T-shirt sizing. Fruit Sizing. Planning pokers. You might be familiar with any or all of these estimation (relative sizing) techniques. Story points based estimations (along with velocity mapping) is touted as a predictable method to plan for software delivery. Teams are expected to get a good sense of the effort needed to deliver a piece of work by comparing estimates with references of similarly complex work they have delivered in the past.

    The accuracy of point based estimates fares more or less in the same range as sheer gut feel. So, the natural inclination for software teams is to try and make it more accurate than gut feel. Thereby, we obsess with breaking functionality into smaller byte sized stories. We freak out when there is "scope creep". We debate endlessly about ideal days vs. person days. We fuss over the specific visual representation for the burn-up or burn-down.

    Does it matter anymore how many days the team spent chipping hard at a feature that added no value to the business? Have we made agile teams into mini waterfall teams by focussing on the wrong metrics? Can product companies afford this?

    Process heaviness in product companies can cost a lot. We need to find better ways to invest in success metrics. We need to change the conversation from productivity to value add.

    My talk intends to challenge prevalent estimation practices and contest their validity in product companies. I will also introduce ideas around capturing relevant business metrics and sizing stories using business value.

  • Liked Henny portman
    keyboard_arrow_down

    Henny portman - Will the project manager and PMO disappear in the agile world

    Henny portman
    Henny portman
    Partner
    HWP Consulting
    schedule 6 months ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    I will focus on a possible transition of organizations who are introducing the agile way of working. Starting with a traditional project setup using permanent PMO (portfolio level) and a temporary PMO (project level). What will happen if the keep the team together as an agile team. What does that mean for the project manager. I will continue my story by adding an agile team. Coordination between the teams can be managed by a scrum of scrum. Still no need for a project organization with a project manager and a project board and no need for a temporary PMO. I add more teams and the coordination asks for a project manager. What dos this mean for a PMO? We can continue and institutionalize the coordination by using frameworks like Nexus, S@S, SAFe et cetera and has an Integration Manager, a Roadmap Manager or a Release Train Engineer and Product managers and Product Owners. I will add some new to be created teams (aks for a Project Manager to organise) et cetera. I will end with an overview and positioning of different agile frameworks and the role of the permanent PMO (focus portfolio management and Center of Excellence) in an agile world.

  • Liked Sandip Shah
    keyboard_arrow_down

    Sandip Shah - What to do when order to follow is: ‘You need to follow Agile from now on!!!’

    Sandip Shah
    Sandip Shah
    Project Manager
    Allscripts
    schedule 5 months ago
    Sold Out!
    20 Mins
    Demonstration
    Beginner

    Purpose of the session is to discuss about Agile implementation approach and acceptance

  • Liked Anil Vasudevan
    keyboard_arrow_down

    Anil Vasudevan - Agile Culture Index

    Anil Vasudevan
    Anil Vasudevan
    Development Manager
    Allscripts
    schedule 4 months ago
    Sold Out!
    20 Mins
    Talk
    Beginner

    There are many measurement tools for Agile Teams Productivity and Adaptability to Agile. I am introducing a totally different measure for Agile teams. It is called the Agile Culture Index. It is a score for the team for the Agile Culture they build and follow. It is more of being Agile than doing Agile. It is more about the bonding in the team, openness in team, trust in team, readiness for facing any challenges as a team etc. It is more about people part of it than the practices or process, rightly aligned with Agile Manifesto value “Individuals and Interactions over processes and tools”

    The objective of this measure is to understand the Agile Culture adaption and Agile Mindset of the team and help for continuous improvement.

  • Liked Sharmila Patwardhan
    keyboard_arrow_down

    Sharmila Patwardhan - Dont resolve the conflicts !!

    45 Mins
    Talk
    Intermediate

    In the management theory, we have always study about "conflict Management"

    We have also learnt the techniques of conflict resolution.

    But is it necessary to resolve conflict? In today's world, its important to live with conflicts. In fact inviting conflicts in a team is a way to innovate.

    If you don't have conflicts in your team, worry about it.

    So rather than worrying about resolving the conflicts, learn to handle them.

  • Liked Sandeep Yadav
    keyboard_arrow_down

    Sandeep Yadav / Nisha Yadav - Building Blocks for Agile Transformation in Digital World

    45 Mins
    Talk
    Executive

    Today's enterprises operate in highly complex and uncertain digital environment and Agile adoption is highly challenging in such large organizations.

    Digital transformation typically involves implementing digital technology to any aspect of the business, introducing disruptive technologies or moving from paper to digital. Enterprises are focusing on leveraging digital channels which include search engines, social media platform, email platform, mobile platform and their websites to find and connect with the current and prospective customers. Digital transformation accompanied by Agile transformation provides an opportunity to improve processes with customer centric approach and not just technological upgrade. Digital technologies can facilitate process change however they are not central to the change. Agile can assist the organisation in working out how the new system might shape better processes and vice versa.


    While the context for each Digital-Agile transformation is different and there are several scaling models available, the components of the Agile implementation road map which ensure outcome are of universal nature.


    In this session we will cover our model for building the roadmap and the activities to be carried out by Agile leaders and Agile Coaches for successful Agile implementation at scale for Digital transformations. The model covers why to? How to? What to? When to? and Duration? for each component on the roadmap. The model will lay foundation for crafting the Agile implementation strategy and also to write the Agile implementation business case for any Digital transformation. The model is based on our practical experience of large scale Agile implementations.

  • Liked Sandip Shah
    keyboard_arrow_down

    Sandip Shah - Agile – For Maintenance Projects

    Sandip Shah
    Sandip Shah
    Project Manager
    Allscripts
    schedule 5 months ago
    Sold Out!
    20 Mins
    Experience Report
    Beginner

    Purpose of the session is to share experience of implementing Agile in Maintenance teams and have discussion to learn about challenges faced by others and guide them or learn from them

  • Liked Amritha George
    keyboard_arrow_down

    Amritha George - Agile has become boring and its good!

    Amritha George
    Amritha George
    Quality Head, IDC
    ABB
    schedule 6 months ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Agile transformation used to be a buzz word , six or seven years back in IT with only selected, elite groups doing it. But with agile explosion, having a daily scrum meeting has become common place with least expected groups like executive C-suite doing agile. How is this possible? This is mainly due to wide variety of options available in agile and obvious benefit from getting faster feedback.

    Take any team with a pain point, you can offer options like Scrum, KANBAN, Lean- agile, Scaled agile, DevOps, Scrum ban and lot more.

    How it helps your organization? For an organization to be truly agile, all functions need to be agile, not only your software development teams.