After reading the Scrum Guide for 2020 for almost a dozen times now, I've got to say that this script is pretty much well crafted in terms of the application, theory, and for that organizational argument about Scrum adoption. Jared is such an inspiration to be a Scrum Master.
That Scrum Board is nowhere near the Scrum Guide 2020. I mean sure it's okay for teams to adjust and have their own specific custom Scrum Board, but let's not make it sounds like the Scrum Guide requires it to be that complicated. One of Scrum's principles is Focus, so it's important to use just what's absolutely necessary
So you actually admit to reading the scrum guide almost a dozen times? As a long suffering scrum victim I can only quote Guilfoyle: "why don't you choke on my balls?"
Dassix 1 exactly! waterfall works very well in defined, very obvious contexts wherein no real unanswered questions lie. Scrum on the other hand is very handy for kind of complex contexts in which we don’t know the full scope of the problem we’re tackling. Peace
I remember screaming 'I HAD ALMOST THE SAME SCRUM EXPLANATION GIVEN TO ME' when I saw this first air on HBO... it's a scary funny feeling to know how well they captured people's feelings when introducing SCRUM to a dev or product team. I just wished they also lambasted JIRA in the same scene...
Problem with scrum IS managers. Using it as micromanaging tool, using estimates as deadlines and converting process that is pretty much experimental and error prone to publicly humiliating risk averse process. Not to mention you have to literally spend days every sprint on doing this side work.
Scrum is hard to do right. But, you should complete all the work in the sprint that you committed to delivering. If you don’t, you have to adjust how many points get put into the sprint. If you’re gaming the system... well the manager will fire you. I’m sorry you had a bad experience. The managers should be doing most of the planning, not the entire team, so that you’re not holding the entire team up for days, just for the sprint planning, estimations, and retro, so about 2-3 hours every sprint.
@@elliemay1748 Wow... that sounds like heaven. I've seen this done correctly. I've seen it done badly more often, but usually because of bad training. I kid you not, my team had a 1-hour stand up, where we all went to the high-rise cafeteria and talked for an hour. If a "blocker" was brought up, the manager would say, "keep trying."
This is unbelievably accurate. I'm an IT developer and we have 30 minute scrum meetings every single day, except our board is about twice this size with 20 shades of fucking postit notes.
It's fine except for the condescendingly insider vernacular. Is they had just made it functionally descriptive engineers wouldn't regard it with disdain
30 minute scrum meetings, how tf did people let that happen. It's supposed to be 15 minutes at maximum, preferably like half that. That's why it's called a "standup"... you're literally supposed to stand up through the whole meeting so that people keep it moving.
Well, 95% (some even say 99%) of startups failed within their 1st year, and this show has followed Pied Piper to its 6th year. That's much longer than most would consider the appropriate age of a startup
"This just became a job describes" how I feel about waterfall, agile, scrum and six sigma seperately and together lol I swear Gilfoyle is my inner voice during every meeting I have ever been my life.
And the new coworker I just got that inspired me to come rewatch this, he's an instructor/master in ALL of those, from the Marine Corps. So great, my job just became more of a job lol.
A decade as a product manager and I can't believe people can actually study this and get a degree in it. I feel like me saying this is the equivalent of saying "in my day we had to walk through the snow uphill both ways!"
When Gilfoyle said "This just became a job", I burst into laughter. This is literally what we do 😂 Even the same fcking explanation is spot on. What I hate most in scrum is our manager. Instead of using it as a tool for efficiency, he's using it to micromanage us.
I liked the whole run, but I think losing TJ Miller was a noticeable hole that made the show a tad bit weaker for the last 2 seasons. They tried to fill his absence with more Jian-Yang, and it was decent, but it just wasn't the same.
"Psych 101 mind control MBA bullshit" - best definition of SCRUM ever. Things like kanban boards are perfectly fine tools, but the whole 'scrum culture' and the admin nonsense that pops up around it is just.... cringe.
kaban is an useful tool, scrum is a set of rules to use this tool made by people who usually don't do the work but try to have full control over it. Scrum outcomes relies so much on "who" is the person who tries to control it and that can end up in a smooth process or a blocking nightmare, in my experience, in most cases, it's the second one.
SCRUM Master certification that needs to be renewed regularly? Check. "If your project fails you didn't follow the process rigorously enough"? Check. Nonsensical nomenclatures? Check. Scrum is a religion. And don't get me started on the whole "Storypoints are complexity not time" thing. They are time. You goddamn map it to time. It's time.
@@NatureFreak1127 I am no Scrum guru, but if you calculate velocity, then story points/velocity=time. It's more akin to distance. Better coder still can´t work 26 hours a day. That what is meant by that story points is a measure of complexity. But in my team, we just call those man-hours, assign 5 a day to a coder and call it a day. Who can accurately predict these anyway? The complexity of this process must not be such that it actually slows development or is a hurdle as of itself.
Our company gave up and just said 1 point = 1 day of work. Doing scrum / agile by the book is just asking for trouble. Also I am convinced that scrum master certification is a pyramid scheme of some sort
New coworker who's a Marine Corps trained SCRUM master, and he was pretty impressed with what I knew until I showed him this clip as where I learned it all.
Gilfoil was corrrect. Those are not stories! They are tasks. A story is a large requirement consisting of multiple tasks. You only estimate tasks. If they are in a story, the estimate for the story is the sum of the tasks.
+FromTheFlame29 correct, at least in Jira. The writers correctly highlight that a story is a glorified synonym for a task and that epic is a buzzword describing a collection of tasks.
"A story is a large requirement consisting of multiple tasks." OK, but the more pressing issue is whether "choke on my balls" is, as Gilfoyle suggests, a story rather than a task.
7 ปีที่แล้ว +9
A story is a requirement written from the perspective of the user/client. It is broken down or combined with other stories into a task or multiple tasks. An epic contains multiple stories.
I dont think Gilfoyle is a legit programmer. Look at his hands when he types! No real computer guy could last long typing like that! He is begging for RSI!
I think Gilfoyle has mastered a revolutionary way to ignore RSI in a healthy manner. He just refuses to tell everyone why it doesn't apply to him because it would leave a shitload of people out of jobs when sales and treatments go down, so he's chosen not to be an asshole and keeps his technique to himself. That, plus he also hopes that Dinesh gets it.
same thing with gender studies. The entire reason people study gender studies is to teach the next generate of people studying gender studies, its like a circle of uselessnes
Developers love to complain about non-technical positions but put them in a room of non-developers and they wouldn't be able to sell the cure for cancer. I'll agree that a lot of companies would benefit from listening to their devs more, but it's not like every other position is useless
@@sugandesenuds6663you sound like a stem major who'd have a stroke trying to comprehend the idea that life and society is more complex than 1s and 0s. Not to mention you've probably had your fair share of sexual harassment complaints you've had to deal with.
Rob R it’s kind of a combo of both, because they estimated the back log (I don’t know why they called it “ice box” here because that’s something different) so they kind of did scrum because they had a sprint planning meeting, and they didn’t prioritize the back log which is necessary for kanban, and the manager assigned tickets to the devs so, again that’s scrum... it’s really more scrum than kanban but it’s also not really either of them.
Kanban and Scrum can be used together because Scrum focuses on time boxes and Kanban is about tracking story status. We used a similar hybrid at my last job.
I first saw this episode about 4-5 years ago, and about 3 years ago, I asked my boss to implement Scrum. She said she had no idea what that was, and like 3 other managers agreed with her. Now I'm in school for CS and I'm watching this to help me in my Software Engineering class. My, how things come full circle!
"I've got a story, why don't you choke on my balls" @1:41 has to to be the epitome of inner thoughts that engineers want to say to their PMs every friggin sprint planning. This show perfectly captures the hilarity of Silicon Valley work culture. Engineers saying fuck you I do this because I like it and I'm good at it so don't tell me what to do, and PMs being like yeah that's cool, but we need to run a business so we can keep paying you outrageous salaries so shut up and do your job. And engineer CEOs who also hate process but begrudgingly admit that its needed cause velocity is a shit show. This dynamic is beautifully illustrated lol
I don't understand the hate with scrum. What's wrong with dividing up a project into smaller tasks and tackling them one at a time? That's what you're suppose to do as a programmer.
Kyle Netherwood lol it's turns out to be a race between teammates and time becomes factor and fear of deadline that ends up with short cuts to achieve tasks ... Yeahhhhh you completed but wait until it comes back with double load on your head..
It's about autonomy. Reality is, many programmers are arrogant, although the culture of "PC, non-toxic" that's popular right now in the world (and by extension/more importantly, HR) curbs most of this in large companies. I don't know how other fields react to an ignorant outside force, but if a non-engineer/programmer tells devs what to do, a percentage of them will be irked that some PM that graduated from Fuckville University with a BA in polisci and an MBA in marketing is telling them what and how to do things. Especially if said PM is bad at his job (let's implement blockchain on our website!), which'll double the workload with scrum with 0 gain. Then at that point, fuck it, maybe even autonomous waterfall is better than a dictatorial scrum. But yes. Done correctly, scrum is a way of getting software out quicker.
I was far more productive before I had waste time with scrum, nearly as big of a time sink as emails. As for estimating times, it always felt like I was being asked how long it would take to drive from one side of a city to the other without being told which city.
I remember having to delve into various project methodologies for a course...I remember thinking how intro and tutorials came off as very....."Cultish"
I need to give a talk on TDD in front of all the devs in my company on monday, but instead of finishing my presentation I rewatch Silicon Valley clips for the 100th time, because they are 'relevant' to the topic x(
As much as I hate bending under the gaze of any management technique, communication errors are quite literally why I drink. So many wasted hours, trying to accomplish something without success. I could have spent my nights loving life, rather than pondering death.
I've been in this field 20 years now. It's amazing how many devs hate scrum but love kanban when scrum is just kanban where you only plan every two weeks. Now I know you will say kanban is flow etc. but in well functioning teams scrum stories all get broken down into mostly the same size and you basically should end up in flow. The sprint intervals in scrum exists to provide some rigidity so that, in larger groups, you don't constantly get bombarded with change requests, hot tickets, etc. You can just say "that's nice, unless it's really urgent I'll see you in two weeks" and get some work done. To be clear I'm commenting on this video because I came back to watch it because I love this scene. It's hilarious. My comments above are in response to the comments.
I found scrum to work with larger teams, especially dispersed teams. Kanban worked for a product that was well established and more product-led. But I like to be a rebel and mix all the methodologies together to come up with a flow that works for my team. It's never been the same, and it's always changing. As long as we're all in alignment, my devs aren't being bombarded with "hey can you do this real quick?" bullshit, and we can track and measure success, I'm open to anything.
Don't worry too much about it. They never actually implement it as it takes away too much control from management. They'll use some form of bastardized hybrid system.
Scrum puts the development team on constant high alert with numerous iterations of the software on various progress levels (dev, sys test, integration, acceptance, etc). It's supposed to make things very efficient, but all it really shows is that your development team is very replaceable to the lowest bidder.
I just rewatched this and muttered "this is kanban, not SCRUM" and then remembered I used to be cool but now I am Jared. I have so many mixed emotions. Product Managers are a special type of human.
1. Scrum does NOT require you to estimate. If you want to do that, story points or t-shirt sizing is better idea than saying how many hours it’ll take. 2. If you read the Scrum Guide there’s not a single word about User Stories - it’s just a way of writing down requirements. There are other ways of doing that. Nobody said you have to use epics and stories - you can use tasks only if you want. You know why people hate Scrum so often? Because there are Product Owners and Scrum Masters that suck. PO acting like Project Managers (they just use Scrum because it’s popular) it’s the worse thing that can happen.
Yep, totally true. I've worked for only one company that implemented scrum to the fullest, they had dedicated scrum masters managing 2-3 teams. Scrum worked great, productivity was high, and we could get marketing and other useless meetings off our backs. We mostly had technical sessions where we discussed architecture and planned out implementation with the team (usually 2 hours a week). All the other 4 companies I've worked for claimed they worked in scrum or agile. All of them looked like this: they randomly selected a few scrum processes (mostly the ones that were 0 effort to implement) and forced the team to use it. Then when productivity tanked due to the poorly implemented nonsensical new rules they concluded that scrum didn't work. But of course we kept using the half-baked new scrum rules because reasons. Most of my fellow engineers hated scrum, because of experiences like this. But if it's implemented correctly it makes life so much easier. Engineers don't seem to grasp the finer social details (scrum helps to manage teams with team members who have a bit of a difficult personality) and they tend to freak out when we talk about stuff that's a bit less tangible (like story points). Don't get me wrong I'm also an engineer but some of my colleagues who've advocated against scrum also talked hours about how we should let old and sick people die to covid and just be done with it.
Jared said to measure story effort by time and not Fibonacci numbers or T-shirt sizes. Hopefully they just missed the scene where the product owner wrote those stories and added them to the backlog followed by the team refining them. For that, he is fired.
Have a CS interview today and the application says must have a good understanding of Scrum framework... came here to brush up of my knowledge
How'd it go?
completly bad when he told him ”why dont u cholk on ma balls”
this is kanban tho
@@greywolf187 that's correct. Or scrumban
@@jorgeriveramx 6 week sprint maybe? It's excessive
"This just became a job."
exactly...
Firebrand Heard it as I scrolled down to see this.
*angry face*
Gilfoyle gets all the best lines
Yeah, who would ever want to do something worthwhile *on purpose*?
the best course ever about scrum i think
and it's about kanban, unfortunate
Funny is that I was looking for a video that would explain it so I can implement it at work
Konstantine Shengelia Kanban, saFe, JIRA all part of our daily lives now
Major issue is difficulty of stories shouldn't be assessed by time to complete
Scrum is easy to understand, but hard to master
Jared was the glue to this company
Indeed.
@@saisubhash8907 No, Pied Piper
and useless
@@shohruhjurakulov1079 Useless? He literally saved this company on multiple occasions. Especially at the start. What show have you been watching?
@@theascendunt9960 still useless
After reading the Scrum Guide for 2020 for almost a dozen times now, I've got to say that this script is pretty much well crafted in terms of the application, theory, and for that organizational argument about Scrum adoption. Jared is such an inspiration to be a Scrum Master.
That Scrum Board is nowhere near the Scrum Guide 2020. I mean sure it's okay for teams to adjust and have their own specific custom Scrum Board, but let's not make it sounds like the Scrum Guide requires it to be that complicated. One of Scrum's principles is Focus, so it's important to use just what's absolutely necessary
From my academic experience, this is kanban/scrumban instead of an actual scrum. They are all agile so….. they are still right.
So you actually admit to reading the scrum guide almost a dozen times? As a long suffering scrum victim I can only quote Guilfoyle: "why don't you choke on my balls?"
This is kanban, not scrum. There is no sprint and no scrum rituals. Kanban can exist within scrum and usually does, but this is just pure kanban.
You guys need a life.
That's exactly what I thought when I was introduced to scrum: "THIS JUST BECAME A JOB"
bapluda wait is scrum a real thing
We use scrum at work but our workboard is on a website instead of an actual board.
Dassix 1 exactly! waterfall works very well in defined, very obvious contexts wherein no real unanswered questions lie. Scrum on the other hand is very handy for kind of complex contexts in which we don’t know the full scope of the problem we’re tackling. Peace
@@rice83101 incompetent people believe in just one method for all tasks... you can combine the two for developement within release cycles
phil jml it used to be a creative outlet but with all the scrum bullshit it's no longer about passion. Hence it just became a job.
Is there anyone else here who's just watched a video about scrum and came back here to see Jered's explanation?
Watch Silicon Valley online here => twitter.com/fa91d03149e3e4e2d/status/824453837792567296
@@magicgame8735 thats a tweet
Currently studying for my Scrum exam, came back to get more of an understanding haha
When no one updates the Trello.
And you use the faded card function so you open up your Trello one day and every card looks like an old-ass pirate treasure map.
I only have access to the online version so...
I thought it was a voluntary thing
Trello is evil.
Notion ain't it fam
I remember screaming 'I HAD ALMOST THE SAME SCRUM EXPLANATION GIVEN TO ME' when I saw this first air on HBO... it's a scary funny feeling to know how well they captured people's feelings when introducing SCRUM to a dev or product team. I just wished they also lambasted JIRA in the same scene...
Fucking JIRA….
Is that bad? I am waiting to get access to it. 😅
@@Mone7Hero77 once you get in, there is no way out...
I love Jira
@@Mone7Hero77 Jira sucks. SCRUM sucks more. Its managements excuse to load crap tons of red time instead of actually getting things done.
Problem with scrum IS managers. Using it as micromanaging tool, using estimates as deadlines and converting process that is pretty much experimental and error prone to publicly humiliating risk averse process. Not to mention you have to literally spend days every sprint on doing this side work.
perfeclty summed up
At my job we have the problem that devs refuse to cooperante to estimate, so they always play around until two days before the deadline
Scrum is hard to do right. But, you should complete all the work in the sprint that you committed to delivering. If you don’t, you have to adjust how many points get put into the sprint. If you’re gaming the system... well the manager will fire you. I’m sorry you had a bad experience. The managers should be doing most of the planning, not the entire team, so that you’re not holding the entire team up for days, just for the sprint planning, estimations, and retro, so about 2-3 hours every sprint.
@@elliemay1748 Wow... that sounds like heaven. I've seen this done correctly. I've seen it done badly more often, but usually because of bad training. I kid you not, my team had a 1-hour stand up, where we all went to the high-rise cafeteria and talked for an hour. If a "blocker" was brought up, the manager would say, "keep trying."
So true
All my cards seem to end up in the emergency column....
All your *stories
This is unbelievably accurate. I'm an IT developer and we have 30 minute scrum meetings every single day, except our board is about twice this size with 20 shades of fucking postit notes.
It's fine except for the condescendingly insider vernacular. Is they had just made it functionally descriptive engineers wouldn't regard it with disdain
30 minute scrum meetings, how tf did people let that happen. It's supposed to be 15 minutes at maximum, preferably like half that. That's why it's called a "standup"... you're literally supposed to stand up through the whole meeting so that people keep it moving.
30 minutes? those are rookie numbers. Try 60
"IT Developer"
@akshaynatu1084everybody needs to be managed.
"Maybe my leisurely pace is just a little faster than yours." love this show
Why 20 seasons for Grey's anatomy, and this masterpiece is already at the end....?
The power of female viewers
Exactly :-/
Sometimes less is more.
@@r3furbish3dbrain12 I mean, they had one of the best series finales of all time, so I would say they ended exactly at the right time
Well, 95% (some even say 99%) of startups failed within their 1st year, and this show has followed Pied Piper to its 6th year. That's much longer than most would consider the appropriate age of a startup
Guilfoyle's line delivery at 1:42 is A+
Deserves an Oscar
Edmund Huang yeah I love this movie
He was still speaking fast then 😅
A++
"This just became a job describes" how I feel about waterfall, agile, scrum and six sigma seperately and together lol I swear Gilfoyle is my inner voice during every meeting I have ever been my life.
And the new coworker I just got that inspired me to come rewatch this, he's an instructor/master in ALL of those, from the Marine Corps. So great, my job just became more of a job lol.
Damn, I love that board.
I already don't like you
@@HelloThere-xs8ss Found a lazy-ass.
Those guys need to #Pivot
longhorn2615 like Ross said: PIVOT...PIVOT...PIVOT!!! xD
Pivot
Pivot
PIVOT
shut up
shut up
SHUT UP
At work, whenever the “scrum master” talks, my eyes glaze over and my brain turns off.
Learning in 3 minutes what took me 3 weeks in university 😆
They tend to over explain simple things
A decade as a product manager and I can't believe people can actually study this and get a degree in it. I feel like me saying this is the equivalent of saying "in my day we had to walk through the snow uphill both ways!"
I already miss this show :(
1:48 Gilfoyle and Jared balance is comedy gold. It's like Cartman x Butters.
Yeah... Sort of...
But Jared fucks
@@gersoncruz91 So does Butters, but only Canadian chicks.
When Gilfoyle said "This just became a job", I burst into laughter. This is literally what we do 😂 Even the same fcking explanation is spot on. What I hate most in scrum is our manager. Instead of using it as a tool for efficiency, he's using it to micromanage us.
Man, I binged 6 seasons in 2 weeks. The semi-disappointing finale almost made me forget what a gem this was for the first few seasons
I liked the whole run, but I think losing TJ Miller was a noticeable hole that made the show a tad bit weaker for the last 2 seasons. They tried to fill his absence with more Jian-Yang, and it was decent, but it just wasn't the same.
@@roy4922 People love Jian-Yang but I could never stand the guy. I missed Ehrlich.
"guess he didn't had enough elvis dust on him"
"Psych 101 mind control MBA bullshit" - best definition of SCRUM ever. Things like kanban boards are perfectly fine tools, but the whole 'scrum culture' and the admin nonsense that pops up around it is just.... cringe.
it has some "cult" vibes...
Scrum is basically just a modified form of kanban where you only replan at the end of the sprint.
kaban is an useful tool, scrum is a set of rules to use this tool made by people who usually don't do the work but try to have full control over it. Scrum outcomes relies so much on "who" is the person who tries to control it and that can end up in a smooth process or a blocking nightmare, in my experience, in most cases, it's the second one.
Got a job interview in an hour, coming back here for a quick refresher on SCRUM
🤣
Jesus Christ this is the HARDEST I've ever related to content in my life.
Can't believe after watching tons of videos on how scrum operate in real life, this video made it all clear for me!
"Fuck off, we're working" ..Danesh has the most unexpected replies.
Scrum works perfectly when people hate each other
Alternatively, scrum can MAKE people hate eachother, at which point it will start working perfectly.
I laughed my ass off in class when my Software Systems and Analysis teacher mention Scrum just because of this scene.
SCRUM Master certification that needs to be renewed regularly? Check.
"If your project fails you didn't follow the process rigorously enough"? Check.
Nonsensical nomenclatures? Check.
Scrum is a religion. And don't get me started on the whole "Storypoints are complexity not time" thing. They are time. You goddamn map it to time. It's time.
It's impossible for the process to fail, so any failures are on you.
absolutely. It fucking IS time. I am tired of explaining this to my manager.
Omg, thank you! I thought I was dumb, when I couldn't understand how storypoints aren't measure of time.
@@NatureFreak1127 I am no Scrum guru, but if you calculate velocity, then story points/velocity=time. It's more akin to distance. Better coder still can´t work 26 hours a day. That what is meant by that story points is a measure of complexity. But in my team, we just call those man-hours, assign 5 a day to a coder and call it a day. Who can accurately predict these anyway? The complexity of this process must not be such that it actually slows development or is a hurdle as of itself.
Our company gave up and just said 1 point = 1 day of work. Doing scrum / agile by the book is just asking for trouble. Also I am convinced that scrum master certification is a pyramid scheme of some sort
"This just became a job..." hahahah love it! :D
I use this for my school work to this day thank you Jared
I studied scrum method just 2 weeks back in my curriculum..I totally get what jared said..🤣 go scrum team..
thank you, i was loooking at this reference while at scrumstudy, now i get it even more, it's great.!
the way he says "booyah" is just so funny
New coworker who's a Marine Corps trained SCRUM master, and he was pretty impressed with what I knew until I showed him this clip as where I learned it all.
Was going to send this to my coworkers until 1:42 hahahaha
1:42 was the only reason I sent this to my co-workers :D
I could watch Dinesh & Gilfoyle arguing with each other for 24 hours straight.
The company i work for brought in a complete MBA moron to implement SCRUM in our company too. All the Technical guys despised it.
.. it still worked
master piece of a show. I miss it so much
Gilfoil was corrrect. Those are not stories! They are tasks.
A story is a large requirement consisting of multiple tasks.
You only estimate tasks. If they are in a story, the estimate for the story is the sum of the tasks.
gilfoil
like they said, it maybe four hours or maybe a year for that task
+FromTheFlame29 correct, at least in Jira. The writers correctly highlight that a story is a glorified synonym for a task and that epic is a buzzword describing a collection of tasks.
"A story is a large requirement consisting of multiple tasks."
OK, but the more pressing issue is whether "choke on my balls" is, as Gilfoyle suggests, a story rather than a task.
A story is a requirement written from the perspective of the user/client. It is broken down or combined with other stories into a task or multiple tasks. An epic contains multiple stories.
tis kanban actually =o
I dont think Gilfoyle is a legit programmer. Look at his hands when he types! No real computer guy could last long typing like that! He is begging for RSI!
Exactly, he is sitting on some awkward desk.
I think Gilfoyle has mastered a revolutionary way to ignore RSI in a healthy manner. He just refuses to tell everyone why it doesn't apply to him because it would leave a shitload of people out of jobs when sales and treatments go down, so he's chosen not to be an asshole and keeps his technique to himself. That, plus he also hopes that Dinesh gets it.
what is RSI?
Repetitive strain injury
Ozxmin O'malley c
The world seems to be filled with managing, sales, HR, and marketing people desperately trying to justify their salary.
Correct.
I have a couple of projects going where I have to wear all those hats at once.
Now all my alter egos hate each other.
same thing with gender studies. The entire reason people study gender studies is to teach the next generate of people studying gender studies, its like a circle of uselessnes
Developers love to complain about non-technical positions but put them in a room of non-developers and they wouldn't be able to sell the cure for cancer. I'll agree that a lot of companies would benefit from listening to their devs more, but it's not like every other position is useless
@@sugandesenuds6663you sound like a stem major who'd have a stroke trying to comprehend the idea that life and society is more complex than 1s and 0s. Not to mention you've probably had your fair share of sexual harassment complaints you've had to deal with.
I used this on my team on last day of our sprint and it worked like a charm. People were so happy to move their cards to complete
10 years ago?! 😮
This is more kanban than scrum. But still a funny scene.
yuck...
Rob R it’s kind of a combo of both, because they estimated the back log (I don’t know why they called it “ice box” here because that’s something different) so they kind of did scrum because they had a sprint planning meeting, and they didn’t prioritize the back log which is necessary for kanban, and the manager assigned tickets to the devs so, again that’s scrum... it’s really more scrum than kanban but it’s also not really either of them.
Kanban and Scrum can be used together because Scrum focuses on time boxes and Kanban is about tracking story status. We used a similar hybrid at my last job.
I first saw this episode about 4-5 years ago, and about 3 years ago, I asked my boss to implement Scrum. She said she had no idea what that was, and like 3 other managers agreed with her. Now I'm in school for CS and I'm watching this to help me in my Software Engineering class. My, how things come full circle!
Imagine being such a fucking tool that you ASK YOUR BOSS TO IMPLEMENT SCRUM.
But your circle needs to go back to backlog.
"Not tasks, storys" LOL
0:31 That face is just "why tf am i hearing this"
I've haven't watched Silicon Valley but I'm taking the Scrum Master certificate and this clip was recommended by the trainer. Now I'm intrigued 😛
one of the best series of all time things are accurate
Dammit, what was out front?
This very inappropriate logo had been painted on their garage door. i.imgur.com/vutPkwF.jpg (It makes sense in context.)
alxg833 we need a video with the garage and the weed
"I've got a story, why don't you choke on my balls" @1:41 has to to be the epitome of inner thoughts that engineers want to say to their PMs every friggin sprint planning. This show perfectly captures the hilarity of Silicon Valley work culture. Engineers saying fuck you I do this because I like it and I'm good at it so don't tell me what to do, and PMs being like yeah that's cool, but we need to run a business so we can keep paying you outrageous salaries so shut up and do your job. And engineer CEOs who also hate process but begrudgingly admit that its needed cause velocity is a shit show. This dynamic is beautifully illustrated lol
It's Kanban not scrum
I'm currently studying Scrum and it's pretty good when software looks all messy.
I don't understand the hate with scrum. What's wrong with dividing up a project into smaller tasks and tackling them one at a time? That's what you're suppose to do as a programmer.
BrainDeadZombies what they hate is the time to the milestone set by a pm with no programming experience
They split it into smaller tasks anyway; scrum is just the method of communicating who is doing what.
Kyle Netherwood lol it's turns out to be a race between teammates and time becomes factor and fear of deadline that ends up with short cuts to achieve tasks ... Yeahhhhh you completed but wait until it comes back with double load on your head..
It's about autonomy. Reality is, many programmers are arrogant, although the culture of "PC, non-toxic" that's popular right now in the world (and by extension/more importantly, HR) curbs most of this in large companies. I don't know how other fields react to an ignorant outside force, but if a non-engineer/programmer tells devs what to do, a percentage of them will be irked that some PM that graduated from Fuckville University with a BA in polisci and an MBA in marketing is telling them what and how to do things. Especially if said PM is bad at his job (let's implement blockchain on our website!), which'll double the workload with scrum with 0 gain. Then at that point, fuck it, maybe even autonomous waterfall is better than a dictatorial scrum. But yes. Done correctly, scrum is a way of getting software out quicker.
I was far more productive before I had waste time with scrum, nearly as big of a time sink as emails. As for estimating times, it always felt like I was being asked how long it would take to drive from one side of a city to the other without being told which city.
I love how they think there are way too smart for this but end up caught in it in a matter of seconds !
“Maybe my leisurely pace is just a little bit faster than yours” 😂
looks like a great show
182 scrum "masters" disliked this video ! 😂
I remember having to delve into various project methodologies for a course...I remember thinking how intro and tutorials came off as very....."Cultish"
That's it. That's all I needed to know. I'm applying for the Certified Scrum Master certification.
I need to give a talk on TDD in front of all the devs in my company on monday, but instead of finishing my presentation I rewatch Silicon Valley clips for the 100th time, because they are 'relevant' to the topic x(
their chair is so uncomfortable, how they sit on it all day long?
It's a TV show
and gilfoly seating position also uncomfortable
1:20 does anyone recognize what software shows up on this screen?
One of the Jetbrains IDEs?
As much as I hate bending under the gaze of any management technique, communication errors are quite literally why I drink. So many wasted hours, trying to accomplish something without success. I could have spent my nights loving life, rather than pondering death.
I've been in this field 20 years now. It's amazing how many devs hate scrum but love kanban when scrum is just kanban where you only plan every two weeks. Now I know you will say kanban is flow etc. but in well functioning teams scrum stories all get broken down into mostly the same size and you basically should end up in flow. The sprint intervals in scrum exists to provide some rigidity so that, in larger groups, you don't constantly get bombarded with change requests, hot tickets, etc. You can just say "that's nice, unless it's really urgent I'll see you in two weeks" and get some work done.
To be clear I'm commenting on this video because I came back to watch it because I love this scene. It's hilarious. My comments above are in response to the comments.
I found scrum to work with larger teams, especially dispersed teams. Kanban worked for a product that was well established and more product-led. But I like to be a rebel and mix all the methodologies together to come up with a flow that works for my team. It's never been the same, and it's always changing. As long as we're all in alignment, my devs aren't being bombarded with "hey can you do this real quick?" bullshit, and we can track and measure success, I'm open to anything.
"Fine, then don't compete, at whatever speed you like..."
I remember when they were telling people in school about this scrum bullshit. I'm surprised it was still relevant in 2014
Heard about Scrum on this when I first saw it, now learning about it
Don't worry too much about it. They never actually implement it as it takes away too much control from management. They'll use some form of bastardized hybrid system.
Scrum puts the development team on constant high alert with numerous iterations of the software on various progress levels (dev, sys test, integration, acceptance, etc).
It's supposed to make things very efficient, but all it really shows is that your development team is very replaceable to the lowest bidder.
i am dealing with this.... daily... 😆 😆 😆
I really don't understand how a house full of developers, didn't knew about scrum...
Because there are many other methodologies. Real, developed methodologies that allows to analyze, have requirements, design and estimate.
what best tool for using scrum method?
Such a great show
Why is Maya open on the computers behind the code editor ?
I just rewatched this and muttered "this is kanban, not SCRUM" and then remembered I used to be cool but now I am Jared. I have so many mixed emotions. Product Managers are a special type of human.
I wish I knew scrum when I was in school, damn! still graduated, but damn!
"I've got a story..."
isn't that kanban
lol after working my way through Project Management for WGU this scene makes more sense.
"Psych101-MBA-MindControl-Bullshit"
1. Scrum does NOT require you to estimate. If you want to do that, story points or t-shirt sizing is better idea than saying how many hours it’ll take.
2. If you read the Scrum Guide there’s not a single word about User Stories - it’s just a way of writing down requirements. There are other ways of doing that. Nobody said you have to use epics and stories - you can use tasks only if you want.
You know why people hate Scrum so often? Because there are Product Owners and Scrum Masters that suck. PO acting like Project Managers (they just use Scrum because it’s popular) it’s the worse thing that can happen.
Yep, totally true. I've worked for only one company that implemented scrum to the fullest, they had dedicated scrum masters managing 2-3 teams. Scrum worked great, productivity was high, and we could get marketing and other useless meetings off our backs. We mostly had technical sessions where we discussed architecture and planned out implementation with the team (usually 2 hours a week).
All the other 4 companies I've worked for claimed they worked in scrum or agile. All of them looked like this: they randomly selected a few scrum processes (mostly the ones that were 0 effort to implement) and forced the team to use it. Then when productivity tanked due to the poorly implemented nonsensical new rules they concluded that scrum didn't work. But of course we kept using the half-baked new scrum rules because reasons.
Most of my fellow engineers hated scrum, because of experiences like this. But if it's implemented correctly it makes life so much easier.
Engineers don't seem to grasp the finer social details (scrum helps to manage teams with team members who have a bit of a difficult personality) and they tend to freak out when we talk about stuff that's a bit less tangible (like story points). Don't get me wrong I'm also an engineer but some of my colleagues who've advocated against scrum also talked hours about how we should let old and sick people die to covid and just be done with it.
lmao did gabe got fired from sabre and joined a startup?
...aaaand they still doing it till season 5 hahaha
Jared was the best character.
i write software -- and happy to have no idea what scrum or agile or any of that bullshit is all about.
Jared said to measure story effort by time and not Fibonacci numbers or T-shirt sizes. Hopefully they just missed the scene where the product owner wrote those stories and added them to the backlog followed by the team refining them. For that, he is fired.
Today was my exam on software software engineering and question about scrum came i could only think of this scene😂😂
1:42 or 1:43 or 1:44 which ones better?
The genius of this show and Scrum is that they went from "why don't you chortle my balls" to "fuck off, we're working" in less than a minute.
This was more useful than my university.
This is literally my job. I’m the Jared 😭
the good old days, without system masters… i mean scrum masterss
What kind of code editors are they using by the way ? can anyone tell the name ? its clearly not sublime text.
vim
They're building a compression algorithm, not working with html,css or js - so I doubt they'd use Sublime
Shashwat singh The fullscreen app on the computer at 1:19 is Microsoft Blend. Don't know what's in the foreground.
+Shashwat singh It's an ".idea" / "intellij" editor of some kind.
+BenRangel Sublime Text is considered hard-core these days and not suitable for HTML/CSS and other BS.
Ken Schwaber cried watching this
This is Trello!
"Everything thas has to do with errors sounds like your whole vibe" hahahha fucking Gilfoyle