Thanks for all the support on this video. As one of my first videos on this channel, I know there are heaps of ways it could of been improved, and thanks for all the feedback which I am taking note of!

@AssepMapanta

2 ай бұрын

Thank you I have learned a lot from this video

Great video, but you wrote "spring" like a hundred times.

@username00009

2 ай бұрын

He also spelled “artifact” incorrectly and spelled “sprint” correctly at least a few times. I’m guessing he’s dyslexic, but does it really matter if you understood the video?

Generally an ok video, but there are a lot of mistakes in here, not just spelling errors. Just a couple examples from the first couple of minutes: the burndown chart is a tool but it is not a scrum artifact, the 3rd artifact is the increment, or working iteration of software. Additionally, the scrum guide outlines 5 events: the sprint, sprint planning, daily scrum, sprint review, and sprint retro. This video gives a decent baseline, but watchers should be aware that there are inaccuracies throughout.

@Nox-gu9cj

2 күн бұрын

Thanks !

Much better than the 9 hour lecture we had in uni

Let me start by saying, I'm NOT hating the video just pointing out a few anti-patterns. User stories is not part of SCRUM, a user story is one method of defining the work that need to be done - there are many others. In addition, it's Sprint Planning apposed to Spring Planning. There are many other terms (Project backlog vs Product Backlog, Burn down charts) and concepts here that are components of Jira and not Scrum. Scrum does not prescribe which tools to use and Jira is not Scrum, you can use Jira for Scrum but the choice is yours which tools you want to use. My suggestion is to anyone wanting to write the exam, stick to the Scrum terms and concepts in the Scrum Guide. This video does have some good guidance as far as method is concerned.

@inouk_hay

Ай бұрын

100% agree, thank you for pointing out those details Riccardo.

This spring will be awesome :D

@MkFilipe2

27 күн бұрын

1-2 weeks seems like an unusually quick spring D:

Very useful. I love especially the practical part where you show it by example and not just theory.

@bubnov

Жыл бұрын

completely agree

As someone who has learnt enough to start building larger projects, this is very useful. I'd like to get a job in web dev at some point, but most of my projects in the past have started out with me immediately typing out some code and moving on from there. People talk about the importance of planning, but no one has laid it out quite as well as this video. I'm just about to start a new project, so I'll see if I can put this into action.

Well made video, with real examples. As a web development student learning scrum work, this is best what I found in youtube. Thank you very much.

I really liked that you included a real world example to solidify the concept. Thanks for the great content.

It was very confusing when it showed 'Spring' instead of 'Sprint' on the visuals.

@tjane_izme

4 ай бұрын

I thought it was just me, waiting for him to correct it.. 😅

just started with Scrum training today and this video really defines the how-to's and what visually effectively. thanks for this

Please don't spread misinformation. Scrum is not an acronym and doesn't stand for what you seemingly made up to be. I would love to see the source where you got that from. It actually comes from the term Scrum that's used in rugby. The team comes together in what they call a scrum to work together to move the ball forward. In this context, Scrum is where the team comes together to move the product forward.

@landsknecht_voran

8 ай бұрын

Noone cares

@seektruth5750

7 ай бұрын

@@landsknecht_voranwe care

@Soccer_funny_AFG

7 ай бұрын

Correct

@zaradmaster

6 ай бұрын

Pls Shit It.

@hanar7765

6 ай бұрын

Please i want to understand the difference between scrum and agile

Good example, easy to catch up what the basic knowledge of SCRUM. Thank you!

Thank you so much for such great a explanation of SCRUM. You really help me a lot.

Thanks for the video! It's simple and very understandable

Thank you for this amazing video! Very helpful for my exam in Agile Project Management. :)

Very useful video descriped a whole stuff in a simple method 🎉

Great pace and details - thanks very much!!!! Excellent presentation

SHARED to TechApart! This was an EXCELLENT tutorial. Thank you.

The three artifacts are Product Backlog , Sprint backlog and Increment. I highly doubt that Burn-Down Chart is an artifact. I would say it is definitely a tool for measurements, not an artifact

I love this content, it helps for my capstone, thank you sir.

wow! this video is not appreciated enough. This is GOLD! Thanks a lot

Very useful Scrum! Love this!

Best content i've seen on SCRUM. Simplified, yet detailed. Thanks

@obumnemeadubasim4880

8 күн бұрын

U haven’t seen anything bro.

I get the odd typo but how can you ‘spring’ over this whole presentation and still upload it? I think you need to review your QA process. Perhaps your spring review needs some adjustment.

⭐⭐⭐⭐⭐ corto, claro y conciso 10/10 , thank you

Well narrated but the spullung arrors ere innoing and make me wonder if you just slapped this together on the fly? That seems crucial to maintaining credibility, by just being able to spot and correct: sprint/spring or artifact (not artificats).. project/product.. That did detracted from it.. & was 100% distracting to say the least. ..Otherwise I did learn from it and appreciated the video!

@CodexCommunity

7 ай бұрын

Yea this was done on the fly since I was learning scrum, I'll try to update when I do my next 2023 Scrum video!

Great informative video!

What I have learn in this videos is What is SCRUM, How we can use that method for Our projects and This Man is bad at Spellings(Jokes apart), By the way very good video and very helpful.

Wow, such a great content. I love it. Thank you

You are the only person making videos on this without putting annoying music in the background

Great video and gives me some insight as to what scrum is. However, there are a few typos that made things confusing for a newcomer i.e. shouldn't it be sprint not spring? I found it very distracting to the point I had to search if spring is a term used in project management that I missed. My suggestion would be to fix this error as well as the other screen/audio differences, especially for newcomers such as myself. It might be worthwhile slowing down the narration; in parts I found it difficult to keep up with what you were saying and what was happening on the screen.

Traditional, Traditioanl. Artifact, Artificat. These kinds of mistakes make me question other information in your presentation. Are you using spring and sprint interchangeably or are they 2 different things?

What a fantastic video and a great effort in presenting! Thank you for sharing the Figma diagram, you are a legend.

Good overall explanation, but the errors are very confusing and are a huge distraction when trying to watch the video. Is it possible for you to remake this video without any errors to make every thing as clear as possible?

@alexp7274

Жыл бұрын

Agree. Having the word "Spring" instead of "Sprint" throughout the video multiple times (even after many cut-and-pastes) without catching the error made it look like a legitimate scrum term. No offense but it's a bit sloppy when the video generally had good content otherwise.

@user-zf1pl6wj4n

9 ай бұрын

I think he stole the video from someone else 😂

This whips through Scrum with alot of assumptions that the person viewing it will have any sort of inkling what you are doing and/or talking about

Its very informative thank you!

thanks! it was a complete intro video in a short time!

Great stuff. Good overview and refresher.

You did an excellent job here.

This was the video that made me understand. Thank you! :)

Absolutely fascinating

Thanx, god bless you for sharing

00:00 Scrum is a project management method for startups and software development. 02:19 Scrum methodology involves three roles, three artifacts, and three ceremonies. 04:48 Scrum methodology is a more efficient way of creating a project compared to traditional waterfall development. 07:27 Understanding user stories and sprint planning 10:15 Scrum methodology for software development 12:44 Create pricing calculators using scrum methodology 15:08 Creating a project backlog with three main features for pricing calculations. 17:37 Creating a sprint using a Trello list Crafted by Merlin AI.

For start-ups, the most effective agile Scrum tool that is also affordable would depend on various factors such as team size, specific project needs, and preferred features. However, tools like Trello, Asana, and Vabro are often considered effective choices for start-ups due to their user-friendly interfaces, customizable workflows, and reasonable pricing plans. These tools offer essential Scrum features such as backlog management, sprint planning, task tracking, and collaboration functionalities, making them suitable options for start-ups looking to implement agile methodologies without breaking the bank.

Very informative. Thanks for sharing. Have a great day. 👍

Best Spring explanation

Hi, I have a question, according to your video the third artifact is a burn down but according to the scrum guide it is an increment. Can you explain please?

Awesome explanation. Thanks for sharing.

You made this so simple we're my teacher was dragging it out and confusing me

well explained, Thank you.

Fantastic video. Commenting for the algorithm.

awesome explanation. Thanks Codex.

I appreciate you making this but I was looking for something exactly in line with the Scrum Guide and this deviated a bit.

I enjoyed this a lot and for a waterfall PM, this gave me a high level walkthrough. Very useful. Question. How would you use this workflow for an enterprise project with 400 stories? How would you include EPICS into this workflow?

Cool! Thanks

I still don't understand where the much vaunted "customer feedback" comes in. Once the sprint is done, the user story is done and goes into the burndown chart. Achievement checkmarks are put in checkboxes. Onto the next sprint. If a customer doesn't like it, it will happen weeks (?) later. Then you have the problem of "how many user complaints do we need to care?" So, an additional backlog item is generated. The backlog grows. Which messes up the velocity calculations. Eric Ries talks about a Build-Measure-Learn cycle that leads to validated learning. It is not done, until it is done, and the learning is achieved. The Scrum system is working in failure mode when there is actual customer feedback. Mangement will get all riled up. This seems like a poor method.

@DonGivani

4 ай бұрын

You begin with a MVP as lean as possible. For Example Citibank creating a mobile app for customers. The Customer Service discuss the customer feedback with the product owner. The product owner makes a product backlog for the scrum team to improve customer experience. And this keeps on repeating. After a few years the Citibank is a full fledged app with added investment, insurance possibilities

Although the burndown (or burnup) chart is not an official scrum artifact, many teams use it to communicate and track progress toward the sprint goal during the sprint

@iantho

Жыл бұрын

That's right - formally speaking, the third Scrum artifact is the "increment", not the burndown. The material in this video is a bit misleading.

A thousand likes!!! 👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽 this video should be the best scrum video explanation in the entire KZread !!!

Thanks I was a bit stuck on explaining this

Scrum is product development which was initially created for software development.

This is well explained, thanks! As I understand it, "scrum" is just a term carried over from rugby. It's not an initialization for anything ... funny how language changes though popularity and recognition-the zeitgeist! It reminds me of how Python was taken from Monty, not a snake! OK fine, so long as one knows when to shed the skin, lol.

Great video! Thank you. It's funny though how many times you typed "Spring" instead of "Sprint". Haha

Excellent Explanation !!.....Have subscribed to the channel...

Not clear on something -- in a regular project management scenario, you have the product, but you also have things that come before and after the development: requirements gathering, configuration, implementation, training, beta testing, regression testing, and so forth. Would these all be separate SCRUMs or do you include these phases in the SCRUM planning for the product. If they're all separate, then I don't understand how this method saves a company any time.

Did you confuse spring with sprint repeatedly on purpose or what?

Nice explanation ❤

love this, very helpful :)

thanks mate!

great great video, congratulations

Burndown chart is not one of the artifacts. Product increment is one of artifacts.

Thank you.

I love the explanation and illustration, thanks man

Great video!!

I wish there was consistency in term usage and proper attention given to presentation because the spelling errors make it unprofessional and confusing.

Nice way explained

Could you provide new figma links? The above are not valid anymore (?) I got an error message

you're the Goat

well explanied

How many times can you write spring instead of sprint?!

PLEASE 🙏 ! make another video just like this one but for “SAFe 6.0 Safe Scrum Master” SSM. I would really appreciate 😬

Nice knowledge

How do you deal with large task that couldn't fit inside a sprint but also cannot be divided into smaller items (say a difficult backend support needed for a feature)?

I thought scrum is framework and scrum mindset is product delivery not project delivery

thanks buddy

Good day how can I be trained as a scrum master? great so far!

Excuse me, the burn down chart is not an artefacts in scrum, its only a complementary tool for managing work in a team. The last artefact un scrum is the increment.

Spring, instead of Sprint ;-)

So, what is the difference between spring and sprint? I noticed you pronounce spring as "sprint", even though you wrote it as spring. Why is that?

do you now application lovevol for scrum?

owesome video

Can you send that Scrum Layout you did in the Video?

Hi I have been looking to move IT sector from mechanical manufacturing at the age of 36 is that possible to changover ? If possible can I survive IT sector ?

First time in my life I actually slow down a video 😅

3rd is Product increments

usefull thanks :)

Hey nice Video. But why didn't you create all the Figma Paper and just point to it while you are talking about it. It's very confusing to just see all the arrows and boxes you create while trying to understand Scrum. Apart from that, it was a good and educational video.

Hi can i check if Figma board free?

Artifact is misspelt in your video