How the agile methodology really works

preview_player
Показать описание
Follow InfoWorld to satisfy your tech business needs!
------------------------------­----
Рекомендации по теме
Комментарии
Автор

This is the easiest explanation of Agile I've come across. Thank you:)

ayodelebamgbose
Автор

Only works when there is one dev team with one cook. When there are multiple restaurants and multiple interdependent teams you need waterfall like processes to organize the teams so they deliver in unison. That’s why everyone says agile is chaos and you never see any agile videos talking about multiple teams organizing on a delivery.

patjohn
Автор

You just explained it all so simply and so well! Thanks so much!

aryank
Автор

This kind of explanation is really what I'm looking for thanks

mreast
Автор

Very helpful... Simplicity is KEY! Great Job😊👍🏾

temisalami
Автор

The metaphor u use were incredibly amazing. It is clear and appropriate for the title

rqhtoot
Автор

This was explained very well. Thank you.

journeyskinnyville
Автор

@1:40 "In Agile Development, these groups are called Sprints" - You're thinking of Scrum development, which many would argue is the exact thing you said in the beginning of people thinking they are doing Agile development, but are falling short. You mention Scrum again at the @2:00 mark. Again, "The Scrum Process" is not Agile. Any OG Scrum Master will tell you that Scrumming is a transitional template used to help companies learn Agile while moving away from Waterfall, and if you "Do Scrum Right" then you'll eventually not be doing Scrum, because you were supposed to grow/evolve INTO an Agile process, and out of Scrum. Every company would land somewhere else, though something very Kanban-esque.

Similarly, you brought up that Agile is iterative. Iterations are surely helpful for organization. But Waterfall was iterative. It's iterations were 6-months (give or take a few months). A short Waterfall could be a month. Breaking that down into 2-week iterations doesn't make it Agile. It makes it "Even Shorter Waterfall." That doesn't mean don't consider an iterative approach, but that iterations over delivering a whole meal is Waterfall. Whereas, iterations over delivering minimally viable pieces (The water, the appetizer, refills/drinks, entree, refills, desert) is a better view. People conflate the use of the word "iterations" in that way.

I love that you brought up the tight feedback loop around @2:20, and bringing up CICD around @3:50. But I have to point out that there is an impedance mismatch between your talking about Scrum/Sprinting, and saying that CD "let's you deliver code within". CD doesn't LET you, it absolutely 100% automatically delivers code upon each commit to the trunk. Any process (Scrum, GitFlow, etc) that splits those things out to "let you" choose when to deliver is Anti-CD, and Anti-Agile.

Your overall talk is very good. But this video isn't how agile "Really Works". This is a very high level view for beginners which has a few misleading things. Much like Scrum, this is a good video as a transition from Waterfall-esque approaches. But this isn't "Really" Agile.

JinnGuild
Автор

Thanks for your detailed explanations. I enjoyed the restaurant analogy. It reminds me of few places that need to fire their Agile team. :)

faraandrusky
Автор

Great explanation, great graphics, easy to understand and to the point. Thank you very much for this excellent video.

inhsgfu
Автор

Perfect composition! really like it.Good job.

mhn-desg
Автор

May I remind if I'm correct
Agile methodology
When the client give a document for the QA and execute the system and test case may I ask if the client can give another document for another specification?

atataviang
Автор

Where does the design team fall into the sprint?

thepilot
Автор

Yes, nice parallels... except there was nothing wrong with that 5th burger, it was exactly like the others.

michaelkeller
Автор

It was really helpful. Thank you so much.

josnajose
Автор

may I ask what video software is used to make this video?

jninlove
Автор

Agile, Scrum, Kanban. That are different things. I think you need an explanation too

sevdalink
Автор

Moore Elizabeth Martinez Matthew Lewis Richard

MarionWilliams-mx
Автор

now I know what is Kanban in Japanese, but wait, what is Agile process and how it's different from others?

dgfromy
Автор

I get so irritated with software engineering production methods. It just feels like it's so complicated to implement these things that it makes the creation of these apps harder than otherwise!!

halobullseye