#1 REASON Why Developers HATE SCRUM (not what you think)

00:07:32
https://www.youtube.com/watch?v=5Fd7U4sQ1Ao

Ringkasan

TLDRIn this video, the speaker discusses why developers often dislike the Scrum framework. Initially, the speaker embraced Scrum during an agile transformation, becoming a Scrum Master certified with PSM1. However, they noticed that many developers are not fond of Scrum. The theoretical benefits include self-management, a flat hierarchy, and sustainable pacing, promoting adaptability to change and self-direction. Despite these advantages, the reality is often different. Many companies don't implement Scrum as intended, leading to issues like unrealistic planning and estimation commitments. Developers often face pressure to meet unattainable deadlines, resulting in compromised quality and increased technical debt. This causes a disconnect between the ideal values of Scrum and the actual practices in companies, leading to developer frustration.

Takeaways

  • 📘 Developers often have a negative perception of Scrum.
  • 💼 Scrum is supposed to support self-management and adaptability.
  • 📉 In practice, Scrum is often implemented poorly in companies.
  • ⏳ Unrealistic project timelines frustrate developers.
  • ⛔ Commitments to high-level estimations lead to quality issues.
  • 🤔 Scrum ceremonies feel pointless in rigid environments.
  • 🛠️ Originally, Scrum aims to empower development teams.
  • ⌛ Pressure from management can negate Scrum's benefits.
  • 🚧 Technical debt and reduced quality are common outcomes.
  • 🔄 True self-management is rarely achieved in large companies.

Garis waktu

  • 00:00:00 - 00:07:32

    The speaker introduces the video topic - why developers dislike the Scrum framework. He shares his own story of transitioning from a developer to a Scrum Master, expecting developers to love Scrum as he did. Initially, he was surprised to find out that developers disliked it despite its perceived benefits such as self-management, flat hierarchies, Scrum values, sustainable pace, and adaptability to change.

Peta Pikiran

Video Tanya Jawab

  • Why do developers dislike the Scrum framework?

    Developers often dislike Scrum due to poor implementation, unrealistic planning, and pressure to meet unattainable deadlines, leading to quality issues and technical debt.

  • What are the theoretical benefits of Scrum?

    The theoretical benefits of Scrum include self-management, a flat hierarchy, sustainable pacing, and adaptability to change.

  • How is Scrum often implemented in companies?

    It's often implemented with unrealistic planning, forcing developers to commit to high-level estimations, resulting in pressure and reduced quality.

  • What issues arise from poor Scrum implementation?

    Poor implementation can lead to compromised quality, increased technical debt, and developer dissatisfaction.

  • How do Scrum ceremonies feel in poorly managed environments?

    Scrum ceremonies often feel pointless when teams are under pressure from management and cannot truly self-manage.

  • What is the main reason developers hate Scrum?

    The main reason is being forced to commit to high-level estimations and timelines, causing a host of other problems.

Lihat lebih banyak ringkasan video

Dapatkan akses instan ke ringkasan video YouTube gratis yang didukung oleh AI!
Teks
en
Gulir Otomatis:
  • 00:00:00
    in this video I will share the top
  • 00:00:01
    reasons why developers hate the scrum
  • 00:00:04
    framework so much but before that let me
  • 00:00:07
    share a quick story many many many years
  • 00:00:11
    ago I was a developer and the
  • 00:00:13
    organization the company I was working
  • 00:00:15
    for was going through an agile
  • 00:00:18
    transformation I quickly did my
  • 00:00:20
    professional scrum Master bsm1
  • 00:00:23
    certification applied for a job and got
  • 00:00:25
    it I was now a scrum master so remember
  • 00:00:28
    we were not using agility
  • 00:00:30
    scum Gan waterful model pure waterful
  • 00:00:34
    and we went through this angro
  • 00:00:35
    transformation and I was a SC Master
  • 00:00:37
    doing it while going through the scrum
  • 00:00:39
    guide Pio Manifesto taking my psm1 I was
  • 00:00:42
    convinced that developers would love the
  • 00:00:45
    scrum framework and funny enough when I
  • 00:00:48
    started implementing it when my
  • 00:00:49
    colleagues over scrum Masters
  • 00:00:51
    Consultants F came here agile coaches to
  • 00:00:54
    the company started applying agility
  • 00:00:57
    framework gban I was surprised to notice
  • 00:01:00
    that developers hated it I went online
  • 00:01:03
    and the same thing there seems to be
  • 00:01:05
    this perception that developers hate the
  • 00:01:07
    scrum framework but before going into
  • 00:01:09
    the reasons why let's quickly talk about
  • 00:01:12
    all the benefits of a scrum framework
  • 00:01:15
    for developers first scrum is all about
  • 00:01:18
    self organization self management ver
  • 00:01:21
    scrum team ver scrum Master product
  • 00:01:24
    owners developers are all
  • 00:01:27
    self-managed they decide what to build
  • 00:01:30
    how to build it who builds it and by
  • 00:01:32
    when to build it who wouldn't love that
  • 00:01:36
    put yourself in the shoes of a developer
  • 00:01:38
    you are full control on how to do
  • 00:01:41
    something and by when you need to
  • 00:01:44
    deliver this thing obviously you would
  • 00:01:46
    like it right second hierarchies flat
  • 00:01:49
    structure no hierarchies if you read the
  • 00:01:52
    scrum guide the latest version the
  • 00:01:54
    product owner is not the CEO of a team
  • 00:01:56
    the manager of the team the scrum Master
  • 00:01:58
    is not here to tell developers what to
  • 00:02:00
    do everyone in the team has a specific
  • 00:02:02
    role or accountability but we are all at
  • 00:02:05
    the same level the five scrum values
  • 00:02:08
    courage commitment openness focus and
  • 00:02:11
    respect who wouldn't love these values
  • 00:02:13
    obviously if implemented but we'll talk
  • 00:02:16
    about that more later sustainable Pace
  • 00:02:19
    one of the agile principles and also one
  • 00:02:22
    of the key components of a scrum
  • 00:02:23
    framework we are dedering value to the
  • 00:02:26
    customers every two weeks remember when
  • 00:02:29
    we were working on waterful prior to the
  • 00:02:31
    release you're working like that and
  • 00:02:33
    gradually increasing the amount of work
  • 00:02:35
    the amount of hours that you spend at
  • 00:02:37
    the office until the release date and
  • 00:02:39
    you're here and then it crashes down
  • 00:02:41
    afterwards after the maintainance period
  • 00:02:44
    maybe but every single release we
  • 00:02:47
    already know that we needed to do a lot
  • 00:02:49
    of overtime because we were late we were
  • 00:02:51
    constantly late but with angel with
  • 00:02:54
    scrub we releasing every two weeks the
  • 00:02:56
    base should be sustainable one of the
  • 00:02:58
    key components of angel of of scrum is
  • 00:03:01
    reacting to change being adaptable to
  • 00:03:04
    change our goal here is to provide value
  • 00:03:07
    customers and we are always
  • 00:03:09
    experimenting every two weeks we're
  • 00:03:11
    releasing something to the market we are
  • 00:03:13
    experimenting and experimenting means
  • 00:03:15
    that we can fail learn from our failures
  • 00:03:18
    and that's okay two weeks later we can
  • 00:03:20
    release something better to the market
  • 00:03:22
    we can't plan for one year we can't plan
  • 00:03:24
    for multiple quarters in a row because
  • 00:03:26
    we are releasing every two weeks that's
  • 00:03:28
    how you provide value to customers
  • 00:03:31
    responding to change instead of
  • 00:03:33
    following a plan and what about managers
  • 00:03:35
    directors other management stakeholders
  • 00:03:38
    interacting with a SC framework we are
  • 00:03:40
    not here to tell us what to do because
  • 00:03:42
    we are self-managed we have full control
  • 00:03:44
    on what to build who builds it by when
  • 00:03:46
    to build it and how to build it the
  • 00:03:49
    stakeholders for managers of management
  • 00:03:51
    for directors are here to help us help
  • 00:03:54
    us resolve impediments remove these
  • 00:03:56
    blockers give us feedback on the product
  • 00:03:59
    give us feedback on the team you're not
  • 00:04:01
    here to tell us what to do we here as
  • 00:04:03
    servant leaders that's the textbook
  • 00:04:06
    version of scrum how to do it and the
  • 00:04:08
    benefits that's how aile coaches scrum
  • 00:04:11
    Masters Consulting companies tell you to
  • 00:04:13
    implement scrum to the benefits of scrum
  • 00:04:17
    but in reality I've worked with many
  • 00:04:19
    companies with many scrum Masters
  • 00:04:21
    hundreds of agile coaches and scrum
  • 00:04:23
    Masters in different companies and it's
  • 00:04:25
    always the same thing I've never a
  • 00:04:29
    single time met someone in a large
  • 00:04:31
    company who is applying scrum as per the
  • 00:04:34
    scrum framework and getting the benefits
  • 00:04:36
    of scrum never seen that what I've seen
  • 00:04:39
    though are behaviors that make
  • 00:04:41
    developers hate scrum and for me it all
  • 00:04:45
    starts with pi planning long-term
  • 00:04:47
    planning road map no matter what you
  • 00:04:49
    call it planning that is more than a
  • 00:04:51
    Sprint planning you're planning for
  • 00:04:53
    multiple quarters you're planning for
  • 00:04:54
    one year you're even planning for one
  • 00:04:56
    quarter that's three months you need to
  • 00:04:58
    know three months in advance they ask
  • 00:05:00
    you for a high level plan high level
  • 00:05:02
    estimations and what do they do they
  • 00:05:04
    make you commit on these estimation on
  • 00:05:06
    these dates and too often or not you
  • 00:05:09
    underestimated how much time it would
  • 00:05:11
    take to develop the thing I know many
  • 00:05:13
    managers who tell developers but why not
  • 00:05:15
    add buffers why are you always
  • 00:05:17
    constantly underestimating and then
  • 00:05:19
    rushing to meet the dates first it was a
  • 00:05:21
    high level it was a guess you never said
  • 00:05:23
    we would need to commit on that second
  • 00:05:25
    when I had buffers you challenge my
  • 00:05:27
    estimation and you tell me to reduce it
  • 00:05:29
    so what are you talking about fix your
  • 00:05:31
    problem first and stop making me commit
  • 00:05:34
    on things that are unrealistic but I
  • 00:05:37
    didn't commit on fast for core problem
  • 00:05:40
    which causes a lot of problems down the
  • 00:05:42
    line because when teams are rushed to
  • 00:05:44
    meet deadlines that they never committed
  • 00:05:47
    on they start cutting Corners quality
  • 00:05:50
    decreases we don't have time to fix
  • 00:05:52
    production issues technical debt
  • 00:05:55
    increases customer value we don't care
  • 00:05:58
    about customer value now we just care
  • 00:06:00
    about meeting this date we are late
  • 00:06:02
    we're getting pressure we're working
  • 00:06:04
    overtime and to make matters worse we
  • 00:06:07
    need to do all these scrum ceremonies
  • 00:06:09
    daily stand up daily scrum SP planning
  • 00:06:12
    retrospective why do we need to do all
  • 00:06:14
    these things we are not in an
  • 00:06:15
    environment where we can experiment
  • 00:06:17
    where we can learn where we can fail
  • 00:06:20
    where we can be self-managed no someone
  • 00:06:22
    already decided that we needed to to
  • 00:06:23
    release that by this date why are we
  • 00:06:25
    faking it why are we doing the daily
  • 00:06:27
    stand up the daily scrum spr planning
  • 00:06:29
    planning one what are we planning in the
  • 00:06:30
    Sprint why do you need to plan when you
  • 00:06:32
    already know that you need to meet this
  • 00:06:34
    date no matter what because someone in
  • 00:06:35
    top management pressured you to meet
  • 00:06:37
    this state why are we even doing
  • 00:06:39
    planning the complete system breaks down
  • 00:06:42
    crumbles when you prevent the team from
  • 00:06:44
    being self managed and make them believe
  • 00:06:47
    that they are s managed obviously they
  • 00:06:49
    will hate scrum and some people tell you
  • 00:06:51
    know that's only some companies using
  • 00:06:53
    the scrum framework live but no every
  • 00:06:55
    single one every single company I've
  • 00:06:57
    worked with all I know scrum Masters man
  • 00:06:59
    or coaches working in different
  • 00:07:01
    companies no one it's always the same
  • 00:07:04
    thing the focus is projects the focus is
  • 00:07:08
    timeline road map deadlines that's the
  • 00:07:11
    main reason why I believe developers
  • 00:07:13
    hate the scrum framework so much it's
  • 00:07:16
    because of a single thing being as high
  • 00:07:19
    level estimations and then they force
  • 00:07:20
    you to commit on that it causes so many
  • 00:07:22
    other a problems down the line people
  • 00:07:25
    don't see and if you want to know how to
  • 00:07:27
    fix that watch this video right here and
  • 00:07:29
    I'll see you in a few seconds
Tags
  • Scrum framework
  • developers
  • agile transformation
  • self-management
  • planning issues
  • estimation commitments
  • technical debt
  • Scrum ceremonies
  • developer frustration