Scrum is a project management framework and does not specify a set of how-tos or checklists that some other development processes define. Since Scrum can be implemented in various ways, it is easy—and often common—to misinterpret Scrum’s guidelines and make mistakes while implementing it. A new team, in their eagerness to “go agile” and adopt Scrum, often succumb to common pitfalls. Being aware of these mistakes is the first step toward avoiding or resolving them. Sumedha Ganjoo discusses and shares examples of some common mistakes that she notices new teams making. Examples include shared and unclear Scrum roles, excessive estimation, accumulating technical debt, failing to capture non-functional requirements including quality, and not having an effective retrospective. Scrum offers the opportunity to incorporate feedback iteratively, and watching out for these mistakes enables us to deal with them sooner. Learn about these mistakes, review your processes, and determine if you can improve the way your team does Scrum.

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

Outline/structure of the Session

Introduction

Agile adoption, gauge room experience, audience participation

 

Common mistakes to be covered:

  1. Sharing Scrum Master and Product Owner, especially when switching people from waterfall roles like project managers to agile roles.
  1. Excessive Estimation
  1. Not focusing on technical debt
  1. Not focusing on quality and other non-functional requirements
  1. Teams where only one person (Scrum Master) is trained or passionate about Scrum and Agile practices.
  1. Following the Scrum guidelines too strictly [Shu ha ri]
  1. Focusing too much on tools
  1. Micro managing and over reacting
  1. Not having a [good] retrospective

 

Quick Retrospective Exercise

Learning Outcome

The audience will learn about common pitfalls when adopting Scrum. This will help them avoid or fix these mistakes. This talk facilities discussions and knowledge sharing in peers who are transitioning or have transitioned from Waterfall to Scrum.

Target Audience

Scrum Master, Product Owner, Scrum Beginner, Project Manager, Recent Scrum Adopter

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Manjit Singh
    keyboard_arrow_down

    Manjit Singh - The Power of Mindsets and Questions in Agile Coaching

    45 mins
    Talk
    Intermediate

    “The important thing is not to stop questioning.” –Albert Einstein, because “every question missed is a crisis waiting to happen.” Discover the technique to ask the questions to make breakthrough differences in decision- making, problem-solving, innovation & culture. Typically, questions open thinking, while answers often close down thinking. Question Thinking is a tool for moving beyond limitations in perception and thinking and advancing to novel and extraordinary solutions and answers.

  • Liked Brian Sjoberg
    keyboard_arrow_down

    Brian Sjoberg - Let's Sharpen Your Agile Ax, It's Story Splitting Time

    Brian Sjoberg
    Brian Sjoberg
    Agile Coach
    Excella Consulting
    schedule 1 year ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    Do you want to write great User Stories that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration and be potentially shippable to production? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Then we will dive into learning techniques for splitting stories in this interactive workshop. 

  • Liked Andy Bacon
    keyboard_arrow_down

    Andy Bacon - The Super Agile Satchel

    45 mins
    Experience Report
    Intermediate

     

    Are you a Scrum Master that has a strong affinity to sticky notes, dry erase markers, and other tools of Agile facilitation? Are you tired of seeing the same old blue painters tape on every kanban board? Want to learn some new facilitation techniques that you can use in retrospectives or to build awesome information radiators with your team?

    If so, join me for my session on the Super Agile Satchel.

    During the session, I’ll briefly talk about how the satchel came to be and its awesome contents.  Then we’ll jump right in to actual examples of information radiators that I created with the tools the satchel contains.  I'll discuss why choosing the right materials, colors, and sizes are critical to facilitation and creating information radiators that draw attention, are maintainable, and focus the team on what's truly important.

  • Liked Mathias Eifert
    keyboard_arrow_down

    Mathias Eifert - Don’t assume you’re creating value – prove it!

    45 mins
    Talk
    Beginner

    Does your organization find it hard to determine “the right thing” to build? You are not alone – studies show that even in very high performing organizations only 10-35% of initial ideas actually generate business value. Agile development should make it easier to obtain early customer feedback, but in most organizations Agile approaches are limited to software development teams with little connection to the rest of the business. In addition, Agile methods by themselves offer few guidelines on how to translate organizational goals and customer needs into the backlog’s content and relative priorities in the first place. As a result, there is a significant, but often underappreciated risk that Agile teams end up very efficiently building “the wrong thing right.”

    In this session, we explore how Lean Discovery and experimentation can expand the scope of Agile’s “inspect and adapt” feedback loops to systematically identify and validate critical assumptions about our product’s value proposition. Based on the Lean Startup and Lean UX approach to product development as a series of hypotheses about customers’ behaviors and value perceptions, we discuss ways to derive testable assumptions from organizational goals to enable validated learning. Finally, we explore the implications of this approach on project planning and budgeting to support increased business agility.

  • Liked Paul Boos
    keyboard_arrow_down

    Paul Boos - Mind Meld: Why Pair Programming Works

    Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 1 year ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    So why does pair programming (or any form of pairing really) work? Well rather than tell you why, let's experience it! 

    This is a simple 3 round exercise that you can do with your teams and managers to demonstrate the benefits of pairing. It will show the linkage between having a shared mental model through collaboration and ease of integrating the resulting work.

  • Liked Trent Hone
    keyboard_arrow_down

    Trent Hone - DevOps Darwinism: Advancing our Art through Safe-to-Fail Experimentation

    45 mins
    Talk
    Beginner

    Static designs and monolithic structures are brittle and prone to failure. How can we progress beyond them? By understanding the nature of our challenges and applying the right tools at the right time. This talk will describe how to use evolutionary principles to foster changes in your architecture and infrastructure so that you can create antifragile systems.

    Nassim Nicholas Taleb spoke to these ideas in “Antifragile: Things That Gain from Disorder.” Join us as we describe how we can:

    • Move beyond planning for known failure modes and instead develop antifragile systems that are safe-to-fail in unanticipated ways.
    • Leverage the Cynefin framework and its 5 sense-making domains to better frame problems and drive action.
    • Employ microservice architectures to make the variability of our environments work for us, not against us.
    • Gain knowledge more rapidly through multiple parallel experiments.
  • Liked Andrea Goulet
    keyboard_arrow_down

    Andrea Goulet - Vulnerability: The Key To Successful Agile Adoption

    Andrea Goulet
    Andrea Goulet
    CEO
    Corgibytes, LLC
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Software development culture has been dominated by the hero. Rock stars, ninjas, and 10Xers have been the center of attention, giving the skewed perception that great software is the result of a single amazing developer. But this couldn't be further from the truth.

    In this talk, Andrea Goulet, the CEO of Corgibytes, will share her experiences using vulnerability and empathy as drivers for Agile adoption and culture building. 

  • Liked Ken Furlong
    keyboard_arrow_down

    Ken Furlong - Upgrade Your Metrics – Cumulative Flow Diagrams and Beyond

    45 mins
    Talk
    Intermediate

    When dealing with metrics, most Agile or Lean teams begin with a Burndown Chart.  Unfortunately, that is also where most of them stop.  While a Burndown Chart is a great first step, it only provides a small sliver of the information the team has access to.

     

    In this talk, we’ll be starting at the beginning with what a Cumulative Flow Diagram is, how it relates to a Burndown Chart, its advantages, and where it too ultimately stops.  We’ll then look at additional information radiators that the team can easily use based on existing data to provide transparency to stakeholders and the raw material for continuous improvement.

  • Liked Katy Saulpaugh
    keyboard_arrow_down

    Katy Saulpaugh - The Agile Reorg: A Survival Guide

    45 mins
    Talk
    Intermediate

    Reorganizations are notorious for being "a wonderful method for creating the illusion of progress while producing confusion, inefficiency, and demoralization" (credit to Charlton Ogburn). Yet in many cases they are necessary to create the cross-functional, self-organizing teams that succeed the most with the agile mindset. Because reorgs are so painful, many teams and organizations are reluctant to look at team structure at all, and the agile journey is over before it even begins. The result? Organizations and teams are siloed, hierarchical, and process-heavy. If an organization is structured right, it can create fertile ground for a truly agile enterprise. This talk will outline how to approach reorgs for agile teams and minimize the pain using change management techniques.

     

  • Liked kelly snavely
    keyboard_arrow_down

    kelly snavely - Women in Agile and the Confidence Code

    45 mins
    Talk
    Beginner

    This talk is inspired by the book ‘The Confidence Code’ by Katty Kay and Claire Shipman.

    What is confidence and how do you know you have it?   While confidence is partly influenced by genetics, it is not a fixed psychological state.  However, you won’t discover it thinking positive thoughts or by simply squaring your shoulders and faking it.  It requires work and choices: less focus on people pleasing and perfectionism and more action, risk taking and fast failures.  This is why it can seem harder for women because these behaviors aren’t typically the ‘norm’ for women but generally come naturally for men.

    In this talk we will explore the roots of confidence and the gender gap between men and women.  To ground the learnings, we will also hear interview summaries from four great and diverse women in agile: 

     Lyssa Adkins, Esther Derby, Ellen Grove, and Kat Conner

  • Liked Fadi Stephan
    keyboard_arrow_down

    Fadi Stephan - Fostering Self-organizing Teams

    45 mins
    Workshop
    Intermediate

    One of the 12 principles of the Agile manifesto states that “The best architecture, requirements, and designs emerge from self-organizing teams.” Why is that? and what exactly are self-organizing teams? How does a team become self-organizing? Teams that have always been used to command and control cannot suddenly become self-organizing overnight. Come to this session to learn what self-organizing really means. Understand the attributes of a self-organizing team and some of the challenges you face in getting your team there. Understand how to find the right balance between team learning and team empowerment vs. control? Leave with techniques to help you build and foster high performing self-organizing teams.

  • Liked Scott Blacker
    keyboard_arrow_down

    Scott Blacker - Help! My Teams are Agile but my Execs are Waterfall!

    45 mins
    Talk
    Beginner

    Organizations in the midst of a bottoms-up agile transformation can find themselves in a quandary. Even though some (or even all) teams may have adopted agile at the developer / program level, PMOs are often still required to plan, resource, and report on progress with almost no consideration given to the methodologies of the underlying work. 

  • Liked Mindy Bohannon
    keyboard_arrow_down

    Mindy Bohannon - Winning at Remote Project Teams, Pajamas and Productivity

    Mindy Bohannon
    Mindy Bohannon
    Agile Business Analyst
    Excella
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    80% of communication is face-to-face non-verbal cues. In today’s remote working environment this dynamic is dumped on its head and written emails have taken over. Skype would be ideal but any company I’ve ever worked for doesn’t give video bandwidth as an option. Communication and trust are the key for success in any project. The more remote the team, the more important communication in all forms and modes becomes. Different personalities and cultures require a variety of communication methods and collaboration tools. This requires a variety of approaches by project managers and team members when requesting input on questions, raising issues in a safe environment and setting expectations of each other. When do you pick up the phone versus send a text versus send an email? What tone are you sending? What example are you setting for openness and collaboration?

  • Liked Mathias Eifert
    keyboard_arrow_down

    Mathias Eifert - Impact Mapping – How to Have your Goals Drive your Features

    45 mins
    Workshop
    Beginner

    Wouldn’t it be nice if there was a way to combine design thinking, visual facilitation, cause-and-effect analysis, quantified business goals, surfacing of value assumptions and direct traceability from goals to features in a single approach?

    There is! Gojko Adzic’s Impact Maps are both a tool and a method that helps multiple stakeholders gain consensus on which features or actions will most likely help us achieve an organizational goal. In the process, we can decide which user groups or personas to target first, derive epics/user stories, identify the underlying assumptions that need to be validated using testable hypotheses, and determine leading indicators to get early feedback whether we are moving in the right direction.

    In this workshop, we will look at how to build an Impact Map with a group of stakeholders and how to get the most value out of it. Best of all, you will go create your own sample map so you will walk away with hands-on experience!

  • 45 mins
    Talk
    Intermediate

    While there are many examples of Agile  methodologies being used in government, the number of agencies realizing success from it is much lower. A recent survey of Federal CIOs shows that while over 90 percent of respondents reported some form of Agile adoption, 50 percent believe they are ineffective at implementing Agile.

    So why the gap? If agencies can stand it up, why are they stumbling to realize the promises of Agile?

    Understanding this gap and the reasons causing agencies to stumble will help you to recognize similar issues impeding Agile adoption, understand ways to address those challenges, and reflect on your own journey transitioning to Agile. 

    This presentation will address these questions by telling the story of ongoing Agile adoption within the IRS around a large-scale IT modernization project. It will describe the organizational characteristics that challenged Agile adoption and integration, and share lessons learned through our Agile journey to date.

  • Liked Rupesh Kumar
    keyboard_arrow_down

    Rupesh Kumar - Don't fall victim to "if it ain't broke, don't fix it" - Be the change

    Rupesh Kumar
    Rupesh Kumar
    Agile Solution Director
    Citizant
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Have you ever imagined how our ancestors built Stonehenge, the Great Wall of China and the Pyramids without the tools and technology that are available to us today? Now imagine today’s world without the internet, smart phones and technology. What do you see? I see that there have been generations before us and there will be generations after us which will develop ways to survive, excel, and perish. One thing that is constant is change. Most of the organizations today acknowledge that change is good and have discussed it in great detail; however, but fall short in realizing the change.

    Change is an absolute truth. No one can agree with this more than organizations in today’s cut-throat competition, where constant change is the norm for their survival. Organizations which are slow to respond to change or resist change are on the verge of being obsolete. They need to change for various reasons such as external competition, market pressure, performance issues, changing workplace demographics, globalization etc. Organizations which invest in proactively responding to change are more likely to not only survive or but also emerge as leaders, creating new markets which never existed before. When organizations are successful, they become complacent and continue to do what worked, but in doing so you keep getting what you were getting; where is the growth in that? The main reason for organizations to resist change is in their mindset; change is perceived as negative or with skepticism. How many times have we heard the phrase “if it ain't broke, don't fix it.” Many organizations have fallen victim to this mindset and have become extinct.

  • Liked Rupesh Kumar
    keyboard_arrow_down

    Rupesh Kumar - How Scientific Method complements Business Value? - Lets take a look

    Rupesh Kumar
    Rupesh Kumar
    Agile Solution Director
    Citizant
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Product owner provide requirements and its business value to IT which in turn works on building a solution. Usually the focus is geared towards building the correct solution based on customer’s requirements. But can we guarantee if the requirement and the business value provided by the customer is right? Does the product owner really know if their requirement adds value? We propose a shift in how the requirements should be processed. Instead of accepting requirements based on business value and customer’s need, we suggest a scientific method of evaluating a requirement to see if it really does add any value prior to adding it to the backlog. Most of us in our early school years might have studied in science the scientific method for asking and solving a scientific question.

  • Liked Rupesh Kumar
    keyboard_arrow_down

    Rupesh Kumar - The other side of Agile - What can we learn from it?

    Rupesh Kumar
    Rupesh Kumar
    Agile Solution Director
    Citizant
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    We all know how paramount collaboration and communication is among members for success in the Agile world. People, Process and Tools are the three pillars of any organization. This session will focus on the people aspect of Agile. Teams are made of people who come together to work on a project from their diverse backgrounds - each of whom bring with them their respective personalities which has developed and evolved over time. According to the Myers-Briggs indicator, there are 16 personality types and each personality type has its own pros and cons. An organization’s success is largely dependent on its team’s personality which in turn is driven by the personality of each and every team member. In this session we will explore questions like – What has personalities to do with Agile? Why do we care? What is the impact of personalities on an organization’s success? Which type of personalities promotes team members to thrive? Which personalities create bully behavior in the team and toxicity in the organization? Can personalities evolve over time?