@johnelliott9823
During start of lockdown Agile coach insisted we physically stand at home when saying our piece during standups "in the spirit of agile" Two years on not sure where he went..
@MrLordZenki
I worked in a company where they decided to adopt Agile and Scrum and literally the first thing they did was set how many hours are in a story point.
@drybiscuits
The awkward moment when everyone's standing up and looking at one another knowing someone's about to lie
@diegoleao
So accurate ๐ Scrum is just a template for organizing your development, nothing more. But the agile coach will $ell you that if you "do it right" it will solve a billion problems. You did it, and the problems are still there? Well, you didn't do it right.
@this-cris
Test driven development! or a regular manual QA tester. We are hungry for more!
@lunaticberserker5869
"I'm a horrible developer" looks at the camera confidently
@doresearchstopwhining
"I help them make waterfall look like scrum." pure gold....
@h3um
we deserve cloud architect next.
@Sarubotai
"We solved the problem we didnt even know we had" I just got coffee all over my desk - this is gold ๐
@wouterschols3345
Got an actual add for an agile coach before this video
@zanepearton
Absolutely brilliant ๐๐
@kencharles7048
I love these videos so much. I laugh my head off every time.
@PeepingOtter
"I was a horrible developer"- every scrum master I've dealt with that was a developer. Looking at you Kristie
@์กฐ๋ฐ์ด๋ -r6r
i've been waiting for you from korea
@blueice1364
Would love to see your iteration of an Android or iOS developer. XD
@glthegamemaster4197
"I don't remember what I did yesterday, but I'll keep doing it" I feel attacked lmao
@golubevslife
Waiting for video about DevOps :)
@zxul2340
"AI didn't work because you didn't do it right"
@Zeero3846
When agile requires conformity to a process, you know it's being done wrong. I think of agile as whatever process helps to achieve these goals: - Regular correspondence with stakeholders - Tasks are clear, verifiable, and short - Developers are not stuck on something for a long time - High priority items do not dominate the majority of sprints Things I've found to help achieve these goals are: - The use of sprints to prevent long cycles of no communication between the developers and the stakeholders. There should be the freedom to adjust sprint size or the amount of ceremonial overhead; otherwise, you're losing productivity. - Points are not treated as estimates or measures of competency, but measures of vagueness. Developers will tend to underestimate work for a variety of reasons, but it really doesn't help if the manager is constantly making the team wary of deadlines, but if points aren't an indication of deadlines being met as much as the potential for uncertainty, then he can at least force a conversation about mitigating the risk associated with that uncertainty, which developers otherwise tend to hide for fear of looking incompetent. - Team members actually do some work together. This at least helps mitigate the problem with certain developers being a single point of failure, and it helps with rapport, unless there's a personality clash. - Junior developers have a scheduled meeting with a senior developer to go over technical details. This is another way to force communication that might otherwise never happen until a lot of time has been wasted. Everything else that's usually associated with agile, I find it to be either extraneous or ends up getting done organically without having to lay it down as standard practice. Agile is just a guideline, not a framework of rules and ceremonies, and many of its practices are just to demonstrate that certain high level goals are actually possible, but the team needs the freedom to revise those practices to find out how best to get there with what they already have. They can't be dictated from on high with very strict standards of uniformity. Maybe the goals to align with can be that way, but the practice needs to vary where it needs to.
@JohnVance