SCRUM: Twice the Work, Half the Time 

Over a month I'm looking for agile, scrum videos. They appear only in IT context. Your video strongly convinced me thats totally useful for any project!

Its because a lot of people who make the deadlines don't have a clue, or they want to put 'false' pressure on people. I never worked in a scrum environment, but to me it is common sense on how to come up with time estimates. Whenever my boss asks me how long a project would take to complete -- if it was a project I never worked on before so I didn't have a frame of reference. I would tell my boss that I will need to start working on the project for a few hours and then give an overall estimate to complete by the end of the business day, and I would also indicate any potential items that may delay the project, so the boss is aware. I would also update a % complete in the workflow project management tools at least once a day. But even then you can run into delays with system outages, people being out sick,a new project coming in with a higher priority, etc.

This video is by far the best introduction to Srum you can find ! Clear and very Informative. Thanks for the upload

I've kind of been using this method for the feature film I'm making but I'll definitely take it to the next level using this.

Very well done, keep up the great work!

Thank you so much @Productivity Game for explaining Scrum in the most basic way. I am making this channel one of my favourite after watching "The Power of Full Engagement" today, and yet I bought the book yesterday. The universe indeed brought me here. Stories to answer what? why? when? can provoke thinking and lead to completion of projects. THANKS AGAIN

Very nicely summarized! Thank you!

Very Well Done.. !! Thanks Productivity Game for this Productive Tool

You are the best savior in the world. I read the book, but your summary is super sophisticated. Thanks man.

Wow! You should write a book on how to summarize a book. I've been using Scrum for close to 20 years, and you nailed it.

What an explanation, hats off & superb 👍

Great summary. I 've been using SCRUM in the EPC industry for last three years. it has limitation but the overall framework works best that traditional waterfall Project Management. Thanks for sharing...

Scrum doesn't advocate for stories (03:28). It calls for an ever-evolving product backlog with product backlog items, which get refined into something the team can work from (backlog refinement). User stories are a common way of doing it, but not one defined by the Scrum Guide (or, from memory, in Jeff's book).

Excellent work. Please do more videos on similar content.

It only works with good and technically literate management. Usually the management without technical background wants to show immediately something to the client, reserving less time to important infrastructure features. Later this makes the development more and more difficult.

Really, Appreciate your explanation and you made it so simple for the users. Looking for more videos. (y)

Best Scrum summary in 10 minutes.

Amazing video.

Great explanation!

Good summary 👍🏻

very nicely explained

"You can hand off the story to anyone and they can do it". The modern version of the Mythical Man-Month.

Great Efforts

What are the best ways to prevent overuse, or watering down of agile method e.g., using it for planning office lunches and general meetings? When does agile ever stop being agile? (e.g., what project perimeters or team make-up [two or less] lead to more work rather than less) I think agile is awesome and have been doing business this way for years.

2:24 many companies screw up the Scrum process because they try to use the word 'Agile' like magic pixie dust to magic away bad management and bad project management.

What I like the most is the first sprint is completed and a product is declared and shipped. The next sprint starts and history repeats itself. Where is the time identified for adding the current sprint's code into the previous sprint? Seems like lots of code rewrite, code integration, redundant testing, changing tests and writing automated test plans and having to test the automated test plans.

Very good! by the way, What tool did you use to make this video?!

Great Content, Keep up a good job, Rewards will come soon.

In the world of Chemical Engineering projects, we use the Front End Loading (FEL) based system for refinery or chemicals projects. It is very effective with stage gates and reviews at each gate. I am not sure this new approach can replace it as much as maybe get incorporated into work processes within the stage-gates. This Scrum approach may suit software development projects better. Thoughts?

Amazing video 👌🏻🙂

Excellent

We'll explained. Thank you

Thank you

8:28 Only if I can write perfect font vertically like this, I would be qualified to become scrum master.

Hi. Great video. Any chance we can get the copy of the whiteboard? Ie where you made all the drawings? Thnx

Excellent. Please can I have the checklist?

IMPACT productivity Thanks

Clear. Well done! Thank you.

Hey guys, this video is FAN-TA-STIC! I'd love to use as "Scrum in a nutshell" for my students and Clients. I must say it's pretty complete, but I can suggest 3 adjustments, that require very few time. 1. In timestamp 7:15 (Step #5) you use "Scrum Leader". Sorry, but it's incorrect. Terminology is important in Scrum like everywhere else in Agile. The facilitator of the Daily Scrum (15' Stand up meeting) is the Scrum Master. Scrum framework accounts nobody as "the Leader", as responsibility and success is shared by ALL members of the Scrum Team (Product Owner, Scrum Master and the members of the Development Team). 2. Step #7 This meeting (ops, "ceremony") is a very important one, indeed has a name: it's the "Sprint Retrospective"; it's also the best opportunity to learn from mistakes, celebrate the success and plan better ways for the Team to deliver better quality and great value in the very next sprint. 3. In timestamp 8:41 you write "TYPICAL PROJECT": I suggest "WATERFALL PROJECT" or "TRADITIONAL PROJECT" as "TYPICAL" doesn't define specifically any area or boundary. Hope it might help. ;) Great job, keep on improving and Scrum on! Cheers, Michael (Certified Scrum Master & Agile Coach)

^_^Is this along the lines of (Energy Management)? I do consulting and coaching and have found by eliminating (Time Management) and focusing on (Energy Management) I get MORE DONE in less time or so it seems, the reason being is (from a technical stand point) the time is taken out of the equation? This sounds like that? Thank you.

Great video! Although I think there is an issue with the link to the 1 page pdf checklist..

Well done

Best animation by far.. keep it rolling. One question, which program do you use for the animations. Adobe After Effects ??

Back to school. The Time table way!

Very Well Done (y)

Some stuff sounds extremely dumb, like the interpretation of the 20-80 rule, but if this is how it is presented in the book that's not the videomaker's fault. Overall probably a fair intro to the scrum book. As a developer already scarred by badly run scrum projects, I am terrified to see so many people feeling inspired by this short intro. It should be mandatory to watch Allen Holubs talks "#No Estimates" and the "Death of Agile" in the context of every scrum video :D. Seriously, for anyone out there planning to adopt scrum in some way for their projects, watch his stuff first.

Listening to this in double speed 😁

I've been using SCRUM since 2009. I highly recommend it! It gives the best visibility and agility.

I can imagine you spend all day developing your plan and then one of the managers says hey I've got something else for you to do as well as your project

As a company president and (thus) the BIG project manager, I'm ambivalent. Let's say we have something to develop, a complete product. Something more complex than a dog whistle. Let's also say that the success of this product/project is measured by more than just "does it satisfy the user stories". We have investors, a board, marketers, a distribution channel, long-lead items, risky aspects, a limited budget, and worst of all, an impending due date (say, Christmas). The notion that we don't/shouldn't/can't do an initial top level whole-project estimate is to live in a fantasy world. Scrum in a vacuum ignores a vast array of real-world needs. Like it or not for actual product development we need a blended or "hybrid" approach, one that incorporates input from and satisfies a broad community of players and milestones. The notions that we can "plan along the way" and "we can't/shouldn't do initial whole-project estimates" leaves me cold.

What software is used to create a video like this?

Scrum i s not a game for kids (junior designer) but for heavy skilled and committed people. Methodology is the key and lots of scrum masters and scrum enthusiasts are only allergic to hierarchy and procedures since they want to diverge from classic methods for personnal reasons. Scrum is not an another avatar of chaos.

Thanks

I can't believe but I came to the end of the channel. I watched all the videos. Now what? 😢

Good content. Nice video. Keep up the good job! ( Though slightly out of context here but - I Liked the fact that you showed the team with diverse nationalities, and a colleague with a wheelchair. )

All this money spent on MBA’s then businesses make the same mistakes they always have. This and channels like it are far more educational for RL than anything you’ll pay for.

You know what this sounds like? Cracking the whip.... or slave driving. Maybe the only other thing I am hearing is: set a short deadline so you just focus on delivering the MVP. That seems really it.

I didnt't get the estimate part...the numbers mean what? hours, minutes... Like, If I say an item is 13 but at the end of the sprint I couldnt quite finish it, I change ito qhat number? Please, sorry my stupidity, I'm just studying this now

how is this different than Demming qc?

Why we need debit card details to get free audio book

how do we get the one pager? What's the email?

Starts at 3:14

If the sprint is estimated by points instead of by time, how do we know whether a sprint should/can be done in 1 week/2 weeks/1 month? Also, by improving 10% of successive sprint points, do you mean the team should aim at cutting the total sprint points down to 90% for the future print baselines? How is it practical if most of the sprints end up taking more points than previously estimated? In this case, what can we do to make the improvement? What tools can we use?

Nice typo on the board from Jeff Sutherland - "accelerates" is shown as "accerates". Nice job in translating a quote from his book. Starts at 2:30 of the video.

the link to the check list did not work.

Where is link for email?

The person estimating wrong in a regular project management will likely estimate wrong in scrum methodology...

Why didn't this video take half the time with the same content?

I'm still thinking What is a scrum? And What is a Fibonacci?

Hello, I am urdu speaking. I want to creat a channel like you. Can you help me out?? I have no idea of apps and softwares which are useful

Absolutely the best methodology until rival management gurus invent another bullshit methodology in five years time. Loved the Fibonacci, not at all pretentious and pretty much a guarantee of project success. The exponential improvement function impressed me as well.

Can SCRUM work for individual persons or is it only for groups or organizations?

I'm a construction project manager.

Ok the fibonacci sequence inclusion is just hilarious.

Nice. But estimate in points is not a pratice of Scrum. Please, start to crack the histories in tasks. Then, count the time between the start and the finish of each task. Make a dispersion graphic. Done: without know the complexity of the tasks, you can know the media of delivery of your team. Without lost time playing poker in work time.

this sounds like days of meetings about who what why when blah blah..and little to no actual doing of work, refining and then fixing. OODA loop idea cleaner faster get it done

This format of the writing hand with generic upbeat music is so over-used and so unnecessary. It also makes the content provider over-estimate how much they actually have to say. This could have been said in 3min. In fact, it lost my attention in min 3 anyways. Did we need all those testimonies? Did we need all company names and non-sense diagrams? All it's saying is, do the work with less pre-planning and do it in small chunks with more room for improving plan as we go. Doesnt apply to all sorts of projects nor does it work in every setting but it really works sometimes

why even estimate in the first place? Estimates are so often way off. Why not just work on the top prio items until you feel they’re done or taking too long. For short term consultant projects of course you need to present the client with estimates to land the job. But many companies don’t need that, they just use scrum ”because”, and force themselves to make and break estimates for no reason

Google doesn’t use scrum

not one dislike

Yeah and forget change management. Who needs it?

”The fibonacci sequence is very common in nature so humans are used to it” what a load of BS. A pattern existing in nature doesnt mean the numbers are intuitive

There's so much wrong with this it's difficult to even know where to begin. Scrum is for specific use-cases, claiming it's better than all other project management techniques is empirically incorrect, which is ironic, given that Scrum claims to be an empirical process. (I'm a developer who has used various agile processes since 2007).

Sounds like he had a really hard time reading his script today.

Nice animation and overall good content. Wrong concepts of MVP and several other issues. Please don’t use this video as a source of truth for the details of scrum. You are not going to get a job offer if you do so.

This video is a downward death project.

Once I heard that "Scrum is a project management system" and "oftentimes" I realized the guy does not even know what he is talking about, and grammar is not his friend either. Thus watching this video further would be a waste of time, and waste is to be eliminated (greetings from Lean :)).

This seems like over-engineering a coproduction setting. Sounds like guidelines for communication with autistic coworkers.

Thanks for the video but Scrum is NOT a project management system.

according ot this when apple was making laptops and workstations and steve jobs started focusing on phones since that wasnt a big part of immediate revenue then apple should have ignored it and focused on making more /cheaper/faster laptops and forgotten all about that dumb fone i dea that 1/6 people on the planet now use. ...this shows the folly and relative uselessness of this concept .

Stressed Constantly Revising Unrealistic Milestones

bollocks

Really bad title for the book. We don’t want to do twice the work. We want to create more and better outcomes with less work. See the agile principle on simplicity.

Thank you

Thanks