Thoughts, learnings, comments, discussions, reflections and speculations on anything Agile and Lean.
If you enjoy these videos, please consider becoming a Patreon and support me creating free educational content for RU-vid.
If you’re an agile coach or teacher and are showing my videos as part of workshops or trainings, I would be super grateful for “Super Thanks” contributions.
would be interesting to see what all the currently existing tests look like along with some kind of explanation of what each is testing for merely out of curiosity.
Just came here from EightSidedSquare, this stuff is really interesting! As a beginner game dev, I could see things like this coming really in handy when you have lots of big systems that interact with each other.
Principle #3 I do not think understanding more empirically in a just in time manner is incompatible for experiment and learning I feel your title is misleading
Based on the material presented, "Aglie" looks to me at most like a copy or a new marketing name for the basics of the queueing theory. The basics of queuing theory concern finding an optimization between the cost of idle times in resource utilization and the cost of queuing/flow time. There are ready-made mathematical formulas that enable the calculation of the response time to emerging variability.Theories from over 100 years ago. Regards
I would have added in the video that one of the most powerfull metric in Kanban with Scrum is to follow Item Aging Work In Progress during Daily Scrum. For me, it's a game changer to quickly identify item which is not going to respect the SLE. It helps the team to focus on and to find solution to get this item out of the system the best way possible. My team starts every single daily scrum with this chart. I would have added too that using Kanban and its flow metrics really help a Scrum team to be more predictable. You can follow your throughput, your cycle / lead time, define an SLE by using percentiles, running monte carlo simulation etc. Great video though. It's really hard to cover everything in 30 minutes or so.
Hi ! I don't totally agree on the "Changes to priorities" (around 20:16 ) regarding Scrum when you write that "sprint is fixed" : you should inspect the sprint backlog during the sprint and adapt it to reach the goal. It's the sprint goal that should not change, not the sprint backlog. So, if the new prioritary topic is related to the sprint goal, there is no problem to add it immediatly.
Love your videos. thanks so much for sharing and creating. Question in the Kanban example - Is it best to take from the top of the backlog as the highest priority item. In your case you chose a feature that appealed to you. Where does the priority of items come in?
In Kanban, the rules are set by the team. These aren't shown explicitly in the example. (Perhaps these are the top 5 items, all equally valuable, choosen from a much bigger set of ideas and requests.) But I would say yes, it makes total sense to order the top 5 so that you pull from the top :-)
This is really cool, the exact video I need right now. Super into minecraft and programming. I am even developing my own modpack right now. I also just read Uncle Bob's Clean Code and now I starting to figure out how to implement TDD in my own work. Overall, I really really enjoyed the video!
This had some great ideas about autonomy. One thing though... you don't seem to understand *anarchy*. Anarchy is not chaos. Anarchy means "*without rulers*". All the ideas about ownership, boundaries, expectations apply to true anarchy where people learn to interact with each other without coercion or violence.
Every PM should see this video! This is about putting focus on installing proper infrastructure and facilitating knowledge sharing and education to enable delivery, instead of focusing on delivering. A metaphor: if you build the bridge and roads, the commerce will take care of itself.
What if the bottle neck is caused by a bad manager, how does one go about fixing anything if the issue is caused by the ones in charge of fixing the bottle neck?
It would have been interesting Jimmy to clarify agile maturity as a wrong labeling but inspecting continuous improvement for team Effectiveness can be possible .. I.e how early do we ship ,are we delivering what users need , is our deliverable stable and quality free ,how early can react or pivot if hypothesis is not validated ,is our team in goood dynamic and safety ? Other stuff can also be measured etc.. Bjr I felt that this topic is easily misinterpret into thinking maturity (don’t really like this label and model ) = do we do agile stuff .. Anyways always a pleasure watching your channel
I agree AC is not well defined, hence different interesting points of view. However, I strongly disagree the view of the SM being a "junior AC" or "team-only-partner". Helping the whole organization to effectively use Scrum and improve is the core accountabilities of the SM. The Scrum Team is a open-system to its stakeholders, not a closed system disconnected from the stakeholders. The SM is ideally placed to help change the system from the inside-out.
This video series is WONDERFUL, thank you so much Jimmy, I'm trying to learn how to better engage my team, especially during the pandemic when everyone is so burnt out and the boundaries between work and home are really starting to blur (lots of work from home). I'll probably watch many of your videos today, thank you!
As an agile coach I agree Martins explanation the most. Scrum Masters are supposed to be scrum implementers, whereas, Agile coaches we have the greater Agile methodology in our toolbox and can help create new solutions and processes.
Thank you Ajeet 😀🙏 I paid for the intro animation. Some are made in the editing (primarily scene transitions and some animation). The majority of the animations are however done in PowerPoint 🙈 Don't tell anyone.
