A Brief Overview of th e Scrum Framework This brief video clip offers a testimonial of the Scrum Framework. Scrum is specified by its designers in the Scrum Guide which is the body of understanding of Scrum.

24 thoughts on “A Brief Overview of the Scrum Framework This brief video cli…

  1. Hi Team. As per the latest Scrum Guide..Scrum Master is not a one who ensures that Scrum is understood and enacted.. but the Scrum Master is responsible for promoting and supporting Scrum.

  2. Is this Kristen DiMercurio? We were watching this in a business management lecture, and I practically fell out of my seat!

  3. Why do we need SCRUM after all? Many big and successfull projects including software development projects were done in the past without using SCRUM, SCRUM masters or any other new and exotic methods. SCRUM seems to be another buzz word meant to create jobs for people especially females that cannot write a simple program but feel entitled to give us, hardworking programmers, orders on how to do our job and how to behave.
    SCRUM is nothing else but a supervision and control tool meant to tell programmers that they need to be bossed around by a person who often is unqualified to lead a software development team. This makes SCRUM look alot like politics where people are given ministerial positions without having any background or experience in the particular area whatsoever.

    1. @M North I can only assume the video is meant to explain (parts of) it. If the viewers that don’t already understand it don’t get the concept after watching, the video failed its goal.
      commenting “if you dont know it, I can’t explain it to you” is not only pointless but shortsighted as well.

    2. @Scrum.org I’m wondering what you’re copy-pasting. As Bel Diman said, there was no mention whatsoever of male/female. Why was that statement relevant?
      Stating “In 1995, less than 20% of all software projects were successful” is similarly pointless without comparing it to other figures. Did the figures improve? Was there any correlation proven between the projects and scrum being developed?
      I will agree that any methodology, however succesful, will fail if it is implemented wrongly.
      Still, none of the reply even tríes to answer the question asked, but instead focuses on trivialising the objections the poster has. Further reinforcing their belief that scrum is primarly buzzwords and misdirection.

    3. @OmikronWeapon Bel wrote this statement that we were responding to: “SCRUM seems to be another buzz word meant to create jobs for people especially females that cannot write a simple program but feel entitled to give us, hardworking programmers, orders on how to do our job and how to behave”

      If you want to read about improvements by Agile, read the Chaos Reports https://vitalitychicago.com/blog/agile-projects-are-more-successful-traditional-projects/ and lots of other research on why agile projects are more successful. Agile and Scrum are about 1 thing if nothing else, not thinking you know everything from the start, learning as you go and improving your knowledge over time to delver greater value.

    4. Try Scrum in 1 or 2 projects and validate properly if it was designed properly to better deliver projects. Compare it properly to Traditional waterfall approach.

  4. Scrum is very complicated. I read the guide 3 times & attended 2 sessions, however, still I didn’t understand anything.

  5. Scrum is responsible for some of the worst developed software in ages. It belongs no where in or around software development. You can see that in the very first stupid shit line of this video discounting efficiency. CPU cores are going to get tremendously faster. Even if we add more cores there is a limited gain in performance and the code has to be written to make use of the multiple cores. Look up Amdahl’s law. You will learn something. That means efficiency is going to be number one going forward. When you are going to be running more and more on a system you are going to need that efficiency to make the best use of that hardware. SCRUM all it has done is attract a bunch of individuals that don’t know or properly understand programming into the industry with a bunch of bullshit certificates of knowing nothing. SCRUM has been an absolute plague to the programming industry I say that with 35 years experience at every level. If someone walks into my business with a scrum cert and I find out about it I will literally throw them out the door.

  6. Told me basically nothing. Talks half the video about why scrum is needed without really saying why. The second part is just saying “sprint” 300 times without ever having defined the term. Interspersed are some tech/trend words like “iteratively” and “empirically”.
    End up with eye catching slogans like “better results!” “better values!” and the video is done.
    At least the visual give sóme insight in the proces/framework in that it probably involves sticky notes or something or other on a progress board.
    If I wasn’t already familiar with those, I would have had no clue what the video was trying to explain.

  7. From the website:
    “Scrum is simple. It is the opposite of a big collection of interwoven mandatory components. Scrum is not a methodology. Scrum implements the scientific method of empiricism. Scrum replaces a programmed algorithmic approach with a heuristic one, with respect for people and self-organization to deal with unpredictability and solving complex problems. … ”

    Scrum might be simple, but this explanation ísn’t.
    Firstly, you’d have to visualise whatever “a big collection of interwoven mandatory components” means, then imagine the exact ópposite. The second sentence only says what scrum ísn’t. As does the fourth.
    “respect for people” is mostly PR bullshit, let’s be honest with eachother. We’re left with: “Scrum is empherical and deals with complex situations”

    If the “Hóme of scrum” isn’t able to make its concept clear, something isn’t going quite right, in my opinion.

  8. Is this for real? I mean how fucking dumb can you be not to know that you have to work and have meeitngs with your team in order to develop something. Is there a way which illuminates ppl, to know that THEY HAVE TO FUCKING WORK to get the job done? Unless you train ppl to the specific proffesion and give them the neccesary theory in order to work like masters of the field, you will not have results due to lack of work. Because ppl will not work. They will generally just study in order to be able to work. Other than that, why is there a need to document the need to work in order to have something done? If is beyond mind boggling how stupid this is. And how stupid it is for companies to even consider a said “miraculous process” that helps them solve a problem. Yes there is a process and it is not miraculous. It is called WORK. And it is not an abbreviation of anything.

  9. Around 1:30 the video starts repeatedly using the term “the increment” which seems like something important but its meaning is never actually defined…

  10. Nice artistic decision giving the Scrum Master a Hitler haircut and the stakeholders a Monopoly Man Hat. Was great laugh, but learned nothing about Scrum though.

Comments are closed.