Introducing Scrum to a team that thinks they are already doing it
Even those who are certain that teams should do Scrum in its entirety might give a team some flexibility on their first day. This activity will kick off a new team - that isn’t necessarily new to Scrum - with the practices that they choose to start with. Over time, you can create the environment where they see the benefit of embracing more.
We introduce the team’s way of working with a workshop that gives a team autonomy. Instead of “eat everything on your plate”, start with the elements they already value. Rather than debating or enforcing every detail, you will know where to focus your efforts. Hold your expert card for the practices that really matter.
This activity will also give you insight into the team’s misconceptions. There are aspects of Scrum that they may not realise are included. There are also well established practices that aren’t Scrum at all. Some are useful, some are not.
First, let’s find out what they are not intending to do. Then figure out why. Is a team avoiding practices because of unique characteristics of their work or work environment? Does the system need to change in order for this team to practice Scrum? Or have they just jettisoned the aspects that are too hard to understand? If they have tried something in the past that “didn’t work” why was that? What did success mean to them?
Are the team’s variations reasonable adaptations or do they contradict Scrum values and purpose?The Scrum Guide is really short and teams will benefit from doing everything in it. This activity will help you get there.
Outline/Structure of the Presentation
1. Introduction: what is the problem we are trying to solve?
2. How does this practice address the problem?
3. Short activity to try it out.
The overall kick-off activity presents the team with a set of virtual stickies to organise into categories. The set of stickies includes the roles, events and artifacts of Scrum. There are also stickies that aren’t Scrum (e.g., Jira, velocity and story points). The pack also includes practices that are required in the organisation.
In the overall activity, the team puts practices into different categories: “We don’t know what this is” “We have to do this” or “We want to do this” and “We don’t want to do this”.
Once the team has categorised everything, the Coach or Scrum Master explains what the non-negotiables are and moves the stickies into the “We have to do this” bucket. For example, if the team puts the “Review” card in the category of “We don’t want to do this”, the Coach or Scrum Master will explain that this card needs to go into the category of “We have to do this”.
Anything that is not part of Scrum is negotiable. Activities that are required in the organisation go into “We have to do this”.
The short activity is a fifteen minute subset of the activity. The purpose is to give the audience a taste of what the kick-off activity is like. They will each be given five cards to categorise. Cards will be collected into the categories and the presenter will review.
The facilitator allows the team to place the stickies where the team wants them to go first. Afterwards, the facilitator overrides anything that needs to be included from day one. The facilitator is usually the Scrum Master or Coach and they represent the interests of the stakeholders.
4. What is in it for me?
This activity helps tease out misconceptions and gives the Scrum Master or Coach insight into where they are likely to get resistance and where more teaching is required.
Learning Outcome
A new activity to use in team kick-offs to help establish ways of working with team autonomy.
Target Audience
This session is designed for people who are working directly with Scrum teams like coaches and Scrum Masters.
Prerequisites for Attendees
The activity is designed for people with some experience in Scrum. If nobody on the team has any knowledge of Scrum, it will not work. However, Scrum has been around long enough that it’s not unusual to be introducing Scrum to a team that thinks they are already doing it. People often think they have experienced Scrum but what they have experienced isn’t in the Scrum Guide.
schedule Submitted 10 months ago
People who liked this proposal, also liked:
-
keyboard_arrow_down
James Zhang - Building on human-centred facilitation
40 Mins
Presentation
Beginner
We’ve all been there… having to sit through painful meetings and workshops that leads to more confusion, lack of clarity and frustration with a poor use of everyone’s time.
But, we’ve also been to those sessions that have been well facilitated where you think and say, “wow, I can’t believe the day has gone by so fast” and “that was a fantastic session, it really helped..!”
I want to help people and organisations have more of the latter by sharing my principles and practical tips on how to improve yourself to becoming a master facilitator – this is based on taking a human-centred approach by valuing every individual, including yourself. I’ll be using my “facilitation tree” to help everyone visualise what’s needed to always produce fruitful outcomes where value is created and people are valued.
-
keyboard_arrow_down
Lakshmi Easuwaran - Customer driven product development
Lakshmi EasuwaranGeneral Manager - Head of Orchestration & Shared TechnologiesTelstraschedule 10 months ago
40 Mins
Presentation
Beginner
How can executive management build customer-driven product teams?
Agile product development practices provide a pathway to realize the co-creation of desired product outcomes between customers and development teams. Quickly and frequently obtaining feedback on real products directly from customers give them a direct voice into their own value stream. However, orienting your teams and leadership to build and react to quick feedback iteratively is a significant challenge to any organization taking this on. This presentation will provide an overview of core fundamental techniques that bring customers and teams together.
-
keyboard_arrow_down
Catherine Seal / Brady March - Building accessibility and inclusion into your agile practice
Catherine SealAgile/Ways of Working CoachTelstraBrady MarchAgile Coach - Accessibility Senior SpecialistTelstraschedule 10 months ago
80 Mins
Workshop
Intermediate
The aim of this interactive session will be to challenge participants’ thinking about diversity, accessibility and inclusion and provide some practical tools and approaches to help address barriers and biases and make their teams truly inclusive. While Catherine and Brady have a particular interest in disability inclusion, the approach we will be taking you through will be equally applicable to all types of diverse teams.
Catherine and Brady are both active members of Telstra's Employee Representative Group, Telstrability, as well as having experience as coaches and in the accessibility field.
-
keyboard_arrow_down
Kit Friend - Preparing to Sprint - it's not just all about the planning session
40 Mins
Presentation
Beginner
Teams who roll into Sprint Plannning with a whole bunch of unshaped work set themselves up for pain - but how can you create a relaxed funnel of preparation ahead of the sprint without falling into the trap of waterfalling it? Join this session to discuss common techniques that might help!
-
keyboard_arrow_down
Craig Smith / Michael Huynh - Have we Outgrown the Scrum Master and Product Owner Roles?
Craig SmithGlobal Agility LeadSoftEdMichael HuynhAgile coachShell Energy Australiaschedule 10 months ago
40 Mins
Workshop
Intermediate
The Scrum Master and Product Owner roles (along with the developers) are well understood and described in the Scrum Guide. As organisations begin to mature and scale, a lot of anti patterns start to emerge with these roles, as well as adding traditional roles (such as change, release and project management) and additional agile roles (such as Agile Coach and Release Train Engineer). Given the simplicity of the three roles in the Scrum Guide for a single team versus the challenges of scaling, do we need to take another look at the key roles to help solve the confusion that so many organisations continue to face?
Join us as we ponder the question of whether we have outgrown the roles of Scrum Master and Product Owner or whether we just need more clarity on what these roles actually mean in the context of true business agility.
-
keyboard_arrow_down
Sam Bowtell - The Art and Science of Facilitation in 10 simple steps
40 Mins
Experience Report
Beginner
Facilitation is both an Art and a Science. The Science is the logical preparation and delivery, with the Art being how you navigate and adapt that delivery to the participants in the moment. Sam will share his ten simple steps from his 20 years of facilitation experience on how to prepare for and deliver a memorable facilitation experience. Expect an interactive, fun session that we set you up for success working both virtually and face to face
-
keyboard_arrow_down
Carl Hubbers - Using feedback to identify opportunities for growth
40 Mins
Experience Report
Intermediate
Over several quarters I asked hundreds of developers three simple questions about their product owners.
- Would you recommend them to another team?
- What's one thing they are doing well?
- What's one thing they could do better?
With thousands of qualitative and quantitative responses I have data that shows what scrum teams most want from their product owners.
-
keyboard_arrow_down
Josephine Stephenson / Tomy Oonnoonny - “A Matter of Trust” - coaching and scrumming in a global environment
Josephine StephensonWays of Working CoachTelstraTomy OonnoonnyWays of Working CoachTelstraschedule 10 months ago
40 Mins
Presentation
Intermediate
Coaching and scrumming across cultures can present both challenges and opportunities. Trust in a Scrum Team binds together the three pillars of Scrum: Transparency, Inspection, and Adaptation (ref: What is Scrum? | Scrum.org). Being integral to Scrum, trust helps the scrum values of Courage, Focus, Commitment, Respect, and Openness to thrive. How often do you think about how culture and trust intersect? "Trust is important because it is the foundation around how human relationships revolve" (Build trust with Scrum | Scrum.org) and it is built on experience gained ie empiricism.
The aim of this session is to explore, when working in distributed and hybrid multicultural teams, across different geographies and time zones, how can you ensure trust continues to be built by understanding culture.
- How do you know what is building and what is eroding team trust?
- How often do you ask the team what cultural differences can build team understanding?
Drawing on feedback, from Australian and Indian-based coaches and scrum leads, we will share experiences and thoughts on how we can improve our scrum practices when working with hybrid teams. Team retrospectives, sprint planning, and stand-ups all provide opportunities to continue to build team connections by better understanding the people and places where we work
As a result of a collaborative learning pod, based on Lyssa Adkin’s “Coaching Agile Teams”, we became aware that team conflict and a breakdown of trust may come from a lack of cultural understanding. As a result of this, we conducted a survey with coaches and scrum leads to gain insights.
We will show how scrum events can be improved by continually building trust and connection by understanding each other’s culture more.
-
keyboard_arrow_down
Peter Woolley - The Daily Scrum - Spark the Conversation
40 Mins
Presentation
Beginner
Are your virtual daily scrums flat, quiet and at best repetitive?
Cameras off, no sounds and what was once considered an awkward silence is now normal.
You tried the three questions and you got three predictable and repetitive answers. You recognised the stale questions, stale answers, tried alternatives - team goals, what I helped with, does anyone need help?
BUT what happens if its still very quiet.
How do we find our Mojo, our grove?Where's the energy, how do we find it and go with it.