Think Agile Retrospectives are Boring? Think Again: Let's Create a Whole New Set of Activities

Last year, I was at an Agility Day in New Jersey for my company (ADP). During this day of fun, we uncovered and created new ways of improving retrospectives and new retrospective activities.

You don't have to always do "Start, Stop, Continue" or "Pluses and Deltas". There are plenty of activities that are more creative and more joyful for teams and groups!

In this workshop, we will follow a powerful technique to brainstorm ideas, filter down to the best ones, and then try them out on each other to uncover new and more effective retrospective activities. Come prepared to contribute to a new group of retrospectives!

Gamestorming - Divergent Emergent Convergent

We will go through a divergent process, and emergent process, and a convergent process in creating our new retrospective techniques. These and other powerful techniques will be utilized from the book Gamestorming to harness the power of the participants to create powerful and useful retrospective activities.

 
31 favorite thumb_down thumb_up 4 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

02 mins: Introduction to Agile Retrospectives
08 mins: Sharing and descriptions of some of my new Retrospective activities
05 mins: Instructions on the how the workshop will work
15 mins: Divergent Activities - brainstorming techniques to identify key elements and activities that may work
05 mins: Share back of what each group uncovered
15 mins: Emergent Activities - discussing and analyzing of elements and new activities
05 mins: Share back of what each group determined
15 mins: Convergent Activities - filtering and selecting of new activities
10 mins: Explaining and walk-through of new activities from each group
10 mins: Open Q & A

Learning Outcome

By the end of the session, each attendee will be able to:

  • Facilitate your own creation of new retrospectives (or something similar) with your company
  • Use a handful (or more) of new retrospective activities created by the group
  • Understand the elements needed for an effective and joyful retrospective

Target Audience

scrum_masters, scrummasters, product owners, managers, leaders

Prerequisite

Think of the elements needed for an effective retrospective, not the specific activities. Be prepared to offer your suggestions!

schedule Submitted 1 month ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Jon Tracy
    By Jon Tracy  ~  4 weeks ago
    reply Reply

    I always enjoy your sessions, Paul.  Looking forward to this one.  I would love to hear your thoughts about the book too.

    • Paul J. Heidema
      By Paul J. Heidema  ~  4 weeks ago
      reply Reply

      Thank you, Jon.  Your encouragement and support mean a lot - this is how many of the things that I share have come about, through the kindness of my friends and colleagues in the larger agile community. Plus, this session will be so much fun!

  • Temsila Malik
    By Temsila Malik  ~  1 month ago
    reply Reply

    Look forward to attend this session.

    • Paul J. Heidema
      By Paul J. Heidema  ~  1 month ago
      reply Reply

      Thank you for your support, Temsila. I am too since it will be a group workshop where the quality of the new retrospectives will be created directly from the participants.


  • Liked Sue Johnston
    keyboard_arrow_down

    Sue Johnston - Do Your Product Owners Speak A Foreign Language? Techniques for creating shared understanding

    60 mins
    Talk
    Intermediate

    Effective interactions, between product owners and designers and team members who develop and make those products real, are key to team, product and organizational success. It's reflected in the first value of the Agile Manifesto.

    Still, one of the chief complaints, from both the product side and the dev side, is poor communication. The list of irritants includes: lack of clarity, lack of understanding, lack of time, lack of access, too many meetings, too much jargon, too many badly written user stories and too many people involved.

    Communication isn''t the only obstacle, but it’s a big one - and it can be overcome with no cost or organizational disruption.

    Regardless of the role we play on the team, part of everyone’s job is to create shared understanding. In this session, Marilyn, an experienced product owner and product manager, and Sue, a communication specialist and coach, will share their research about communication gaps in the product-development relationship and approaches that can close the gap.
    Join them to explore tips and ideas to improve communication flow and help teams move from concept to cash.

    NOTE TO TAC TEAM
    Because we are doing some original research on this topic, I would like to include a co-presenter, Marilyn Powers, PEng, who, at the time of posting, is not yet on confengine. Info about her is available at https://www.linkedin.com/in/marilynpowers

    Here is more biographical info about Marilyn:
    Marilyn has more than 10 years experience bringing products and services to market as a Product Manager. As a licensed professional engineer, she has experience working in a variety of fields, from manufacturing to operations to simulation to SAAS software. Currently, Marilyn is a Product Manager at D2L, a leading Ed-tech company, where she works closely with Product Owners, Dev teams, Designers, Senior Leaders and many other stakeholders to deliver quality software tools to educational institutions and corporations who value learning and development. Her expertise is creating shared understanding between diverse groups, be it external customer advisory groups or internal stakeholders.

    Previous presentations or workshops
    Marilyn has presented at a variety of conferences over the past 20 years, the career highlight of which was a live demo on the main stage keynote at the D2L Fusion 2016 conference. Other conference presentations included Online Learning Conference ( New Orleans, LA 2017), Fusion (2015, 2016), Learning Impact Leadership Institute (San Antonio, TX 2016), Industrial Engineering Student Conference (Kitchener, 2016), ModSim World Canada (Montreal, 2010), Montreal Neurological Institute Day (Montreal, 2009), McGill University invited speaker on Haptics (Montreal, 2006). Prior to these presentations, Marilyn was an Instructor of Engineering at Mount Royal University in Calgary, AB.

  • Liked Ahmad Iqbal
    keyboard_arrow_down

    Ahmad Iqbal - Marketing needs Agility too. Here is how to get started...

    Ahmad Iqbal
    Ahmad Iqbal
    Founder
    Playbook Coach
    schedule 1 month ago
    Sold Out!
    60 mins
    Talk
    Beginner

    If your organization is interesting in Agile transformation for technology, then you should also be looking into Agile Marketing.

    Think of your organization like a car. Two wheels which represent Technology, and the other two wheels represent Marketing. Even if you get the Technology wheels spinning faster, unless the Marketing wheels can spin just as fast, your car will be going in circles. Product and marketing go hand in hand when it comes to deriving value from your respective markets.

    As we all know, one of the major keys in Agile is the tightening of the feedback loop. This is why we want shorter sprint cycles, smaller batch sizes, and strive to continuously learn. When it comes to building products, it's the marketing team's job to test the market, size the market, segment the customers in the market, and just generally derive value from the market. But the problem is, most modern organizations are using waterfall-like operating models to run their marketing teams which hand-cuff talented marketers from surfacing new insights.

    Marketing departments are still using waterfall processes because only up until a few years ago, digital marketing was a brand new concept. Large organizations used Print, TV and Radio advertising in their marketing campaigns, which by nature were not trackable. Campaigns were planned well in advance, usually at the start of a new financial year, and themes, content and messaging was approved then too. Because of the lack of trackability, marketing was always considered a cost-centre. Today that has changed.

    Marketing is now quickly being understood as a revenue-driver. New tools are allowing us to track digital campaigns like never before imagined, everything and anything can be attributed to even the most minute detail. Because of this marketing focused companies are able to confidently say that for $(x) of marketing budget input, they are getting $(y) of revenue from customers. This is catapulting Marketing teams to the top of the business group food chain.

    In this session we will discuss the need for Agile Marketing and why marketing should be the focal point for your organization's business agility transformation (hint: it's because marketer's own the customer journey). More importantly, this session will actually dive into the details of how a marketing team would implement Agile using the four stages of the Growth Marketing Lifecycle (GMLC).

    Marketing needs lean and agile processes for many reasons, but here is a summary of the top four points we will cover in detail during the session:

    1. Transparency: CMOs are feeling the pressure to prove their budgets.

    2. Recyclability: How marketing backlogs are actually recyclable, giving you more bang for your transformation buck.

    3. People Investment: Mimicking the skills of the "unicorn" growth hacker through a cross-functional team gives you Voltron.

    4. Continuous Learning: Because today's digital marketing campaigns are so deeply trackable, the learning we can gather from these campaigns is unprecedented.

    How does a marketing group get started with agile?

    There is a four step marketing lifecycle that the audience will walk through with the presenter. It's called the Growth Marketing Lifecycle (GMLC) and it follows four steps:

    1. Goal Orientation: This is where we visualize the marketing team's Funnel Map (similar to a Story Map used by IT teams).

    2. Ideation: This is where we develop the backlog of "growth stories".

    3. Execution & Deployment: Using the scrum methodology to sprint on work items.

    4. Optimize: We look at growth stories that show signs of life, and double-triple down on them in future sprints.

    This session was developed and will be delivered by Ahmad Iqbal, an Agile practitioner and coach. Ahmad has lead the development and marketing of over 4 technology products, and trained over 500 practitioners in Agile Software development and Agile Marketing. Ahmad has implemented this framework successfully at two major Canadian organizations, one major insurance company and one crown corporation.

    NOTE: This presentation will have an interactive app provided to all participants which will allow them to follow the content on their mobile devices.

  • Liked Daniel Doiron
    keyboard_arrow_down

    Daniel Doiron - OKALOA FLOW LAB

    Daniel Doiron
    Daniel Doiron
    President
    Agile Agonist
    schedule 2 months ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    Agility is a mindset. It is not a set of practices that can be installed. But how do you get out of the practices trap, especially when you have to mobilize not just software development and IT teams but the entire organization towards business agility where value is created through meaningful work? How do you engage business teams, users and customers? How do you enable higher levels of collaboration, not just within teams but also across teams? In other words, how do you get individuals, teams and even the entire organization into a flow state where everybody is doing the right thing at the right time by having the right conversations? Rational explanations and models of agility will only go so far. To be truly effective, the agile mindset needs to be experienced, which is exactly the purpose of the new and thought provoking Okaloa Flowlab simulation by Patrick Steyaert, one of agile's better scientific mind.

    Through simulating a conventional work environment that reflects a mechanistic mindset characterized by a focus on resource efficiency, command and control and specialist workers, participants experience which roadblocks need to be overcome. As the team is taking its first baby steps into agile, they will experiment (in 2 or 3 rounds) with policies and practices (e.g. pull of work, cadences, limiting WIP) that enable collaboration, get the team into flow, and allow an agile mindset to emerge. Weaved into the simulations they will discover the fundamental difference between resource efficiency and flow efficiency.

    Participants will step into the simulator after a brief explanation of the rules.

  • Liked Gillian Lee
    keyboard_arrow_down

    Gillian Lee - Minutes to Pin It: How to Get Your Whole Team Agreeing

    90 mins
    Workshop
    Intermediate

    What if your team could share new ideas and make unanimous decisions in minutes?

    Agile teams need to create and agree on many things such as a definition of done, a sprint plan, and what changes they’ll try in the next sprint based on the most recent retrospective.

    How often have you participated in a meetings where few decisions were made? Or where the the loudest person in the room made most of the suggestions and dominated your team’s decision making?

    In this interactive workshop, we will practice coming up with new ideas using everybody’s suggestions and making decisions that the whole team agrees on.

    Learn and practice techniques such as Fist-of-Five, Decider Protocol and Resolution Protocol and Shared Visioning with Lego.

    Make group decisions faster, more aligned with the whole team, and more likely to result in follow-through.

  • Liked Fawzy Manaa
    keyboard_arrow_down

    Fawzy Manaa - How to Lose Dev and Alienate Ops

    Fawzy Manaa
    Fawzy Manaa
    Senior Consultant
    Deloitte
    schedule 1 month ago
    Sold Out!
    40 mins
    Talk
    Beginner

    As many organizations have adopted agile development and are starting to undertake a DevOps transformation to complete the lifecycle, it is not always easy to keep traditionally alienated back office practitioners engaged. In fact, many organizations go about engaging developers, testers, operators, ... in a way that does not align with the spirit of DevOps. Many enterprise DevOps transformations fail because of this very reason, this session will inform the audience of what it takes to create a strong and sustainable movement within an IT organization in today's world where people who perform different functions that are seemingly at odds can come together in the spirit of improving how work is done and delivered.

    The speaker will approach the topic from an anti-patterns perspective, highlighting the symptoms of transformation failure from structural, procedural, and strategic angles and discussing alternative approaches to enable DevOps transformation success.

  • Liked Johanne Boyd
    keyboard_arrow_down

    Johanne Boyd / Carlo Rosales - Why can't the business be agile too? How ADP is incorporating business Agile practices to keep up with technology

    40 mins
    Talk
    Beginner

    Does your business struggle to catch up and understand the technical deliverables from your Sprint Reviews? Is there unnecessary re-work and scope creep because requirements are not properly described by the business? ADP has sought to address these issues by incorporating business Agile practices to keep up with technology. The result? Clearer requirements, strong engagement during Sprint Reviews and a collaborative solution with business readiness aligning with technical deliverables. Join our session to find out more!!

  • Liked Mishkin Berteig
    keyboard_arrow_down

    Mishkin Berteig / David Sabine - JIRA is the Worst Possible Choice

    90 mins
    Workshop
    Intermediate

    A rant, with evidence, on why electronic tools in general, and JIRA in particular, are anti-Agile. Participants will use the Agile Manifesto to evaluate the electronic tools they are currently familiar with. JIRA is used as a case study.

    NOTE: Scrum asks us to have courage. The Agile Manifesto asks us to value individuals and interactions over processes and tools. I hope the organizing committee will consider this proposal despite the risk that it might offend some tool vendors. If we can't speak freely about our experiences with tools, we will fail as a community.

  • Liked thomasjeffrey
    keyboard_arrow_down

    thomasjeffrey - Scaling Agile without the scaling framework

    thomasjeffrey
    thomasjeffrey
    President
    Agile By Design
    schedule 1 month ago
    Sold Out!
    60 mins
    Talk
    Advanced

    Increasingly Agile adoption has focused on how to operate larger enterprises with agility, and run larger and larger initiatives, at scale.

    In many cases, organizations have turned to explicit agile scaling frameworks to address their needs to coordinate increasingly larger efforts to deliver value in a way of that does not sacrifice feedback and self organization . Often these frameworks attempt to address the complexity that comes with large scale by adding extra process and procedure. Prescriptive advice is prescribed in the form of additional roles, stages, gates, and methods. This approach to scaling bears more than a little similarity to the heavy weight methods of the past, but in this case merging agile terminology with much of the same framework bloat and bureaucracy we have seen in the past.

    As a a result adoptees struggle to understand how to fit these frameworks to their context, and seasoned coaches struggle to wrestle out the good bits.

    During this session I will discuss a different approach to scaling agile, one that places an emphasis on both mindset and practice. I'll pay particular attention to the topic of leadership, organizational design, and the role management has to play in designing a system of work that allows larger efforts to work with an agile mindset without being forced into a one size fits all process framework.

    A key part of the discussion will be to showcase how core agile methods and techniques can be extended and expanded to successfully manage coordinated agile deployments that range from hundreds to thousands of FTEs. I'll present these techniques by using real examples of agile deployments I have been a part of during my work with ScotiaBank's agile journey.

    Key Scaling Practices covered will include:
    - The design components required to structure your organization based on demand
    - How to continuously de-scale your organization
    - "Get Out Of the Boardroom" style governance and leadership
    - Operational cadences and Impediment Escalation Flow
    - Managing the flow of value at the Business Technology Asset level
    - Moving the conversation from stories to domains
    - Streamlining finance and budgeting to align to the agile mindset

    I hope to illustrate ways that both management and knowledge workers can select techniques that allow them to scale agile as needed to support ever larger initiatives without succumbing to a one size fits all framework that does not adapt constant change.

  • Liked Taimur Mohammad
    keyboard_arrow_down

    Taimur Mohammad - Delighting the Customer at the First Point of Interaction

    Taimur Mohammad
    Taimur Mohammad
    Coach
    Agile By Design
    schedule 1 month ago
    Sold Out!
    40 mins
    Experience Report
    Intermediate

    The first interaction with a prospective customer often makes or breaks the sale. In today’s age of instantly obtaining products and application at the touch of a button (e.g. mobile apps), the last thing that customers expect is a long, complicated process. Truly delighting the customer requires moving towards instant gratification. How do you re-organize traditionally separate business and technology groups so that the focus is on delighting the customer?

    A group within a leading financial institution identified this as a goal and looked at lean-agile principles and practices to rapidly iterate on delighting the customer and bringing business & technology processes seamlessly together. While delivery was set up using what we’ve come to as good lean-agile principles and practices, how the product backlog was managed provided the rapid feedback, innovation and pivot/pursuits required to truly delight the customers.

    In building the product backlog a number of practices were introduced to make it dynamic and ever evolving.

    • Kanban connected the customer to the product backlog which connected to the delivery engine
    • Product metrics and cost of delay were used to create hypotheses to prioritize MVPs
    • Rapid feedback through various customer and proxy customer interactions were leveraged to feed the customer backlog
    • Monthly releases ensured a constant flow of new features to enhance the customer’s experience
    • Story decomposition ensured the customers feedback was being directly communicated with the delivery team

    The result? While the client is still on its journey the results have been overwhelmingly positive. Key metrics indicate greater customer satisfactions, increased speed to completion and simplified internal processes.

    In this talk we’ll discuss how we’ve taken various product management related practices and stitched them together to connect the customer to the delivery engine. We’ll provide practical examples that we’ve seen work in our experience and engage in a discussion with the group to connect their questions to our examples.

  • Liked Taimur Mohammad
    keyboard_arrow_down

    Taimur Mohammad / Sean Deschamps - Surviving Disruption with Agile: Innovate or Die

    40 mins
    Experience Report
    Intermediate

    Lean-Agile is easily & often associated with customer centric products and solution. The “customer facing” nature of the product allows for thin slicing, feedback and iteration which in turn leads to greater business agility and customer satisfaction. While there have been many exceptional case studies that demonstrate this, applying lean-agile to non-customer facing solutions has often been dismissed. Why is this? The risk is too high to thin slice? There’s no way to get customer feedback? There’s no way to deliver using iterative approaches?

    Over the last 16 months a group within a leading financial services client was brought to a cross roads. Their traditionally stable market was on the verge of being disrupted due to emerging innovation and competition from smaller, more nimble competitors. They knew to operate the same way would result in significant losses in market share over the next decade. To survive, they had to lead the innovation. Change was becoming the norm, and their focus shifted from being solely focused on final solutions, to also re-thinking how they got to these solutions.

    Enter lean & agile principles and practices. Initially dismissed because this client’s business model operated as the backbone of the institution. Much of the work they did was in facilitating payment origination and transaction settlement systems. Applying lean & agile required some significant tailoring.

    In this talk we will discuss this client’s journey, how they changed the entire culture within the organization to focus on survival through agility. We’ll discuss how common lean-agile principles and practices can be applied and tailored to support transforming legacy eco-systems with back-end facing solutions where the concept of a real life "customer" is quite foreign. We'll visit our experiences in encouraging the transparency that is synonymous with an agile approach and how that fostered better partnerships and trust across many groups. We’ll explore how a culture of learning has established early wins for the client and set them on a path towards leading innovation, agility and empowered being first to market.

  • Liked Tyler Motherwell
    keyboard_arrow_down

    Tyler Motherwell - Divide And Conquer

    40 mins
    Experience Report
    Intermediate

    Conway’s Law tells us that the products an organization produces will mirror the communication structures within themselves. Many organizations struggle to organize in a way that facilitates both agility and bringing quality products to market. However, this is a problem that exists, not just within IT, but across the entire enterprise. Imagine you’re the (somewhat mythical/revered) business. How do you organize yourselves in this brave new world? Many of the common patterns (systems, application/application layer) that we commonly apply in technology aren’t good fits.

    In this session, you will learn how to use a structured method to organize your most important resource (your people) around your most important goals. Additionally, you will learn about team types outside of your typical cross-functional team! We will use an actual industry case study to help illustrate usage, as well as give inspiration to how you might do the same in your organization

  • Liked Sam Tabbara
    keyboard_arrow_down

    Sam Tabbara - How to transform culture in large enterprises

    Sam Tabbara
    Sam Tabbara
    Senior Consultant
    Agile By Design
    schedule 1 month ago
    Sold Out!
    40 mins
    Experience Report
    Intermediate

    Most important factors in any Agile transformation are the ability to react and change quickly, which are most often associated with startups than large enterprises. To really win and transform an organization there are core elements that need to be mastered and executed at the culture level. We will cover these elements and provide you real use cases where transformations both succeeded and failed to meet their potential to prove the relationship.

  • Liked Alistair McKinnell
    keyboard_arrow_down

    Alistair McKinnell - Don't Settle for Poor Names

    60 mins
    Talk
    Advanced

    I get frustrated with code that is sprinkled with poorly named classes, methods, and variables.

    Whenever I work on a team or coach a team, I put a lot of energy into choosing good names and sensitizing my teammates to the power of naming.

    I've noticed that developers spend most of their days reading code rather than writing code. I suspect you've noticed too. Creating understandable code is a high leverage activity for any team. And naming is where I start.

    The core of the session is an example that illustrates the process and power of choosing good names. The example comes from a recent project. There will be code.

    I will connect the example to specific techniques and patterns for choosing good names and share resources that you can use right away.

    My goal for this session is to sensitize you to the power of naming.

  • Liked Alexandra Ursea
    keyboard_arrow_down

    Alexandra Ursea - SCARF Model - How to collaborate with and influence others and succeed

    Alexandra Ursea
    Alexandra Ursea
    Independent Consultant
    N/A
    schedule 1 month ago
    Sold Out!
    60 mins
    Talk
    Advanced

    Have you ever been in a position in which you were actively engaged in a massive organizational transformation or personal one? Have you struggled with it? Have you tried different leadership styles or approaches but you were still discontent with the results?

    Perhaps the greatest challenge facing leaders in organizations is to create the kind of atmosphere in which people feel treated fairly, promote autonomy and creativity, foster certainty whenever possible, draw people together to solve problems and find ways to raise the perceived status of everyone.

    If you are a leader, every action you take and every decision you make either support or undermines your objective. Every word or glance is loaded with social meaning. Your gestures and sentences are noticed, interpreted and magnified for meanings you may never have intended.

    This is why leading is so difficult!

    Humans cannot think creatively, work well with others or make informed decisions when their threat responses are on high alert. Leaders who understand this and act accordingly could make a very positive impact in their organizations.

    David Rock,CEO of Results Coaching Intl and co-founder of the NeuroLeadership Institute developed a model known as the SCARF model (Status, Certainty, Autonomy, Relatedness, Fairness) to describe the social concerns that drive human behaviour and which leaders could benefit from to smooth organizational transformation.

    The SCARF model provides a means of bringing conscious awareness to people’s core concerns and shows how to attune your actions to better effect.

    This session will address the foundations of the SCARF model, the five domains of human social experience: Status, Certainty, Autonomy, Relatedness, Fairness as well as the broader application of this model.

  • Liked Louise Heldoorn
    keyboard_arrow_down

    Louise Heldoorn - How Kanban Propelled our DevOps Team to New Heights

    Louise Heldoorn
    Louise Heldoorn
    Lead Release Engineer
    ADP
    schedule 1 month ago
    Sold Out!
    40 mins
    Experience Report
    Beginner

    Description/Summary
    Development Operations is a team that has requests from many sources, many of which have conflicting priorities. How do we move from being reactive, switching priorities, getting buried with stress of delivering on time with high quality to being proactive, innovative highly productive.

    In this session I will walk through the journey my team took to move from reactively treading water to becoming an extremely innovative highly efficient development operations team.

  • Liked Paul J. Heidema
    keyboard_arrow_down

    Paul J. Heidema / Iaroslav Torbin - The Agile Coach Program: Scaling from 20 Teams to Over 60 Teams

    40 mins
    Experience Report
    Intermediate

    The number of agile teams that I support went from 20 (too many) to more than 70 (absurd) in a few months. What could I do? How could I help them?

    From this need came the Agile Coach Program that Paul created and facilitated at ADP with a small group of individuals - one was Iaroslav Torbin. These participants already support (or wanted to support) teams (be they using Scrum or Kanban) and the individuals around them. This is the story of that journey and the results.

    Feedback from the program:

    • "The agile coach program has been a valuable experience both personally and professionally. It was a fun, interactive and engaging."
    • "I really enjoyed being a part of this program. With its interactive and constructive parts."
  • Liked Paul J. Heidema
    keyboard_arrow_down

    Paul J. Heidema / Iaroslav Torbin - Vital Behaviours of Successful Scrum Masters and How to Make Them Stick

    90 mins
    Workshop
    Intermediate

    Agile failure is most felt by Scrum Masters. Why do so many fail to properly support their teams? Why do so many fail to inspire meaningful change in the level of leadership? Why do so many fail to guide transformation in their organisations?

    In this workshop, we will harness the knowledge and experience of the participants!

    Influencer Book

    Why?
    Because everyone can contribute to the learning of the entire group. It will dynamic, full or energy, and joyful - woohoo!

    Who can benefit the most from the session and the power of harnessing the group?

    • Scrum Masters that are struggling to do this role well
    • Leaders that are not seeing the results needed for an effective Scrum team through a weak/unskilled Scrum Master
    • Agile coaches that are coaching Scrum Masters without meaningful or consistent results
    • Project managers trying to make the transition to becoming a successful Scrum Master

    This workshop will use concepts and the model from the book "Influencer"

    Prepare to work together to co-discover the Scrum Master vital behaviours!

    Many people are taking on the mantle of Scrum Masters across agile teams around the world. Unfortunately, many of them have come from more traditional work structures that don't develop effective Scrum Masters. There is a misconception about the purpose of a Scrum Master. Often the Scrum Master becomes the facilitator or the project manager. This has to stop. Effective leaders, agile coaches, and Scrum Masters take advantage of vital behaviours in supporting scrum masters or by building mastery within these behaviours.

    Influencer - the model

    During this workshop, participants will go through a series of exercises to identify the purpose of a Scrum Master, how we can measure success, identify potential vital behaviours, learn from others to determine the vital behaviours, and then create a sound influence strategy to enable effective Scrum Masters and the work that they do. This workshop will use concepts and the model from the book "Influencer" (by Joseph Grenny et all) which details the three (3) keys to a successful change initiative and uses the six (6) sources of influence.

    Prepare to work together to co-discover the Scrum Master vital behaviours!

  • Liked Stuart Oakley
    keyboard_arrow_down

    Stuart Oakley - Multiple Intelligence Theory - An Agile View on How It’s Used

    Stuart Oakley
    Stuart Oakley
    Scrum Master
    Dealertrack
    schedule 1 month ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    Agile teams are always working to discover how they can work best together. By exploring Dr. Howard Gardner's Theory of Multiple Intelligence, we can discover new ways of understanding our teams. With this understanding, we can better adjust how we work to improve teams.

  • Liked Shahin Sheidaei
    keyboard_arrow_down

    Shahin Sheidaei / Shawn Button - Community-Driven Change

    40 mins
    Talk
    Beginner

    Many organizations flatten management structure when they transform to agile. It soon becomes obvious that important activities done by managers are still needed.  A community can fill these gaps. They can provide morale, governance, learning, and mentorship, recruiting and hiring, mutual support, coordination, sharing, innovation and more!

    Unfortunately few companies manage to create a strong community. Even fewer empower that community to fill these gaps. This means they are missing the ultimate benefit of community: a strong, empowered community can transform the organization itself!

    Join Shahin and Shawn in this interactive session to explore communities in organizations. Examine the benefits of building great communities. Learn how to spark the community, and how to support it as it evolves. Hear stories of communities empowered to improve the organization. Learn how to make a community into a driver of positive change.

  • Liked Mike Bowler
    keyboard_arrow_down

    Mike Bowler / Ellen Grove - Running with the Mob: Extreme collaboration with Mob Programming

    90 mins
    Workshop
    Intermediate

    Mob programming is collaboration taken to the extreme, eliciting the best from every member of the team. In this session, you will experience the dynamics of mob programming and learn how to use this technique successfully in your own environments.

    After mobbing with well over thirty teams, we've seen definite patterns emerge, that we'll discuss here.