Beyond User Stories : Take Your Team to Next Level of Awesome!!!
Great teams make great products, but what fuels this greatness? It's the common understanding and passion for the product but more importantly the singularity of purpose and the feedback loop and how the users are responding to the teams work.
The new world of product development is no longer about scope management and delivering the project on time and within budget but it's now more about hypothesis validation and learning from the users and their behaviors.
The dynamics of product development is changing. As more and more organizations are moving towards maturing their agile software development approach the traditional barriers of roles are being broken creating new opportunities and fostering a shift in the mindset. Instead of being tied down to scope management and delivering the project on time, Agile teams are focused and inspired by hypothesis validation and learning from the users and their behaviors.
In this case study we will go over how a portfolio of 12 SCRUM Teams adopted a more outcome approach and how they shifted their mindset from project delivery in Agile way to adopting the Experiment-Measure-Learn-Repeat loop which plays a crucial role in teams overall motivation, performance and moved from being SCRUM Teams to "Product Teams".
We will also see how we experimented with different team formats and how exposing the team members to different events and user research changed the way they perceived the information of the problem they were solving via features and user stories.
Outline/structure of the Session
- Share interesting facts & stats about teams understanding of Product & Purpose
- Experiment We ran to know teams understanding of Overall Product Development process & knowledge outside the boundaries for SCRUM Framework
- How we exposed the team to the Before & After elements of SCRUM Framework and the effect it had on their motivation
- Show how we got the teams involved with the PO in observing the users and solving the product problems together and how their focus shifted from Output to Outcome!
- How we changed the dynamics of the team and reshaped them from SCRUM team to a Product Team
- How we made the team participate in all parts of BUILD-MEASURE-LEARN loop
- Questions & Answers
- Team Members will learn why its important to be part of talking to customers and observing users to build a better product
- Product Owners will learn how involving engineers early on while talking to users helps bring out creativity, better solutions and motivate the team members
- Product Owners & Scrum Masters will also learn to involve team members in right events during vision creation, hypothesis generation and user validations to bring more diverse set of ideas to table and in your backlog to experiment.
- Agile Coach & Scrum Masters will learn how to guide & coach your teams beyond "Build" part and also in to "Measure" & "Learn" part of the Build-Measure-Learn loop.
- Leaders & Executives will learn how in an agile organization and for Agile teams its less about managing and more about mentoring, learn how you can guide the team through "Pivot or Persevere" decisions.
Scrum Master, Product Owner, SCRUM Team Members, Designer, Analytis, Executives, Leaders, Managers
schedule Submitted 1 year ago
People who liked this proposal, also liked:
The Geek's Guide to People - Shifting from Output to ImpactSue Johnston
schedule 11 months agoSold Out!
The stereotype of technical professionals as inarticulate, socially inept geniuses inventing problems to solve is unkind and inaccurate. Yet the Dilbert image persists. So do jokes like the one about the engineer sentenced to death on the guillotine, who watches the instrument of death malfunction, then tells the operators how to fix it.
Why do people make fun of engineers? Do people wired and trained to analyze and solve problems and focus on the mechanics of a situation frustrate those whose brains are wired differently? And how does the engineer’s way of dealing with individuals and interactions - that first value of the Agile Manifesto - sometimes get in the way of team collaboration and productivity?
In this interactive session, we'll show a little empathy for engineers and other analytical folk whose neurological wiring makes them seem different from the rest of humanity. We'll also explore how those with the engineering mindset can develop their own empathy and consciously adopt behaviours that amplify their value to their teams and organizations, make them more effective leaders - and make their own lives easier by positioning themselves for understanding.
Join Sue in a lively exploration of what can happen when engineers and technical professionals shift their mindset from solving problems to creating impact.
You will leave this session with an appreciation of
- How to make your ideas meaningful to others by taking their perspective
- How shifting your language from "What?" to "So What?" helps people connect the dots
- Why giving up the need to be smart may be the smartest thing you ever do
- Techniques you can use to take someone else's perspective.
Standup Poker: How One Hack Revolutionized Our Daily Stand Up and Teams Mindset !!!Kalpesh Shah
schedule 1 year agoSold Out!
One the most significant ceremony of any Agile Team is Daily Standup where the team members get together and plan for their day. But quite often the daily standup turns into a zombie status update meeting where team members come together to blurt out their updates and walk away to their desk without ever maximizing the benefit of that meet up.
In this session I will share a case study of how we created a simple experiment that turned into Standup Poker and revolutionized our Daily Standup. This technique helped us uncover true insights of teams progress and got the team talking about strategic planning and plan to remove any impediments as a "team" on daily basis to accomplish their sprint goal and commitments.
We learnt that when team members started using this technique, hidden impediments and dependencies started to emerge and team members organically started to re-plan and prioritize their work to accomplish the Sprint Goal. Product Owner also found great value in this technique as this helped them see the teams true progress and engage with the team to re-prioritize user stories and even take a story out of the sprint if required. Scrum Masters started to observe a trend in the confidence level over the span of the sprint and brought that information to Sprint Retrospective to discuss and brainstorm ways to improve and keep the confidence levels high throughout the sprint. The discussions and observations due to Standup poker resulted in teams committing better and more confidently during Sprint Planning and got into the rhythm of always accomplishing their sprint goal, but more importantly they started improving everyday and got into "continuous improvement" mode.
The content, exercise and message of this session highlight the agile principles of individuals and interactions over process and tools and fostering the mindset of continuous improvement.
In this session we will share examples, stories and experiences from trying the Standup Poker and how this simple technique converted a bunch of individuals into a TEAM !!!
Fixed deadline and 2 hour sprintsArdita Karaj
schedule 11 months agoSold Out!
It is common to work on projects that have a hard deadline. These deadlines are not always fictional and time really matters. Frequently, there is a big discussion if Agile is the right approach for these cases. Can we deliver what is requested without a detailed planing, task breakdown, milestones on a Gantt chart?
In this talk, I will bring examples from my experience volunteering at GiveCamp for several years. Over one weekend volunteers create digital solutions for non-for-profit organizations using 2 hour sprints, MVP deliverables, prioritization, collaboration and an environment in which you feel proud of what you do. If you think this can't happen in your organization, come to this session and challenge me!
Managing Agile - How an agile transformation can be the key to becoming a great managerMatt Dominici
schedule 11 months agoSold Out!
Your company has proclaimed the following, in a "Managers Only" email:
“We are going agile! We’re restructuring the department into small, self-organizing, cross functional teams. Each team will have a Product Owner who will prioritize the work, and a Scrum Master who will make sure we’re working well. We’ll be announcing all of this at a company-wide meeting this Friday!"
“Wait a second,” you think to yourself… “that’s my job! What do I do now? Should I start working on my resume? WHAT IS HAPPENING TO ME?!"
While many companies will initially make mistakes in trying to address these concerns, the ones that truly succeed in their transformations have managers who share some common shifts in focus.
In this talk, I will cover how managers in an agile environment can now focus on being a great manager - and in so doing, accelerate their teams’ progress towards high performance.
Just imagine! Now that you are unburdened from the drudge of day-to-day “cat herding”, you can focus on the long term health and efficacy of your teams.
Imagine actually having the time and agency to focus on your employees’ professional development. Actually having the time to deeply think about and change team composition. Having the freedom to address environmental issues that your teams bring up. And perhaps most importantly, you can now spend time removing impediments for your teams.
An agile transformation is not something to be afraid of! Great managers see Agile as an opportunity to have an even larger, more meaningful impact on their companies.
Running with the Mob: Extreme collaboration with Mob Programming
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 over two dozen teams, we've seen definite patterns emerge, that we'll discuss here.
Putting the Moose on the Table: Make your retrospectives more effective using LEGO SERIOUS PLAY techniques
In order for teams to step into high performance. it's critical that they develop the practice of having effective conversations about what is and isn't working. Yet in practice, the retrospective meeting is often the least-valued of the agile events: team members feel that their retros are boring, repetitive, and superficial.
In this workshop, we will teach participants how to design and deliver a really useful retrospective using LEGO SERIOUS PLAY. We'll cover the basics of this powerful facilitation technique, and give advice about how to build your own SERIOUS PLAY kit using pieces easily available at the local toy store. We'll also offer practical suggestions for how to design a retro that gets everyone talking (and building), and results in the team agreeing on action.
The participants will leave with a powerful retrospective technique that they can immediately use with their teams.
An Engine for Change - coaching leadersAndrew Larosa
schedule 10 months agoSold Out!
How do you scale agile across an IT organization with 10,000+ people and hundreds of teams? Over the last several years, many large organizations have made their attempt at transforming their IT groups into "agile" teams. I want to use this opportunity to share my experiences and the latest approach to tackling massive Agile transformations.
Too often, teams ask for agile coaching without knowing what agile means. Here are a couple of quotes from email questions I received recently, "A project that we are just embarking on has the potential to be done in Agile", or, "Could you please guide me through the Certification process for Agile. I have a few projects underway that will be managed under Agile methodology."
Usually, there are many definitions of agile when working with large organizations. I find that I am spending most of my time dispelling myths rather than getting to high-value coaching. I will share 3 tactics for jump-starting a large agile transformation:
- The Missionaries - focus on creating some really good examples for the rest of the organization to reference and use as the example for success
- Foundational Understanding - possibly the hardest tactic; focus on widespread education with a goal to create the same language when we talk about Agile, Lean, Scrum, Kanban, etc.
- Leader (and team) Coaching - by far the most important tactic; agile coaches must transcend team coaching and build a sustainable and scalable coaching approach by transferring their own coaching capabilities to the organization’s leaders to make a large agile transformation stick.
It might sound crazy or unreasonable to create coaches out of leaders. But that's not the point. The objective is to build agile coaching capability in these leaders. This will benefit the greatest number of teams and increase the likelihood of widespread agile adoption. No leader will be perfect.