Happy Birthday. Thank you for your ability to take complex applied theory and allow everyone to embrace knowledge and get it. That's an incredible gift that has made a difference in my life.
Hi Gary. Wanted to say thanks for your many teaching videos that have helped me pass my PMI PMP exam today. I know you are Agile focussed, but it has all brought me a greater insight to project management generally, but particularly Agile, scrum , and kanban. Thanks my friend....it felt like you travelled the road with me! Keep up the good work. 👍
Love the video Gary :). One common thing that can be done and which is no secret to anyone and is part of the kanban principles and /or practices is to define explicit quality policies and criteria from one Column to another, kinda like a mini dod per column. i.e: What needs to happen in order for that element to go from column A to B?
Devs should go with scrum master to the playroom for foosball match. You would be surprised how quickly tests are done then... Seriously, great episode! Mr Pink beats even Mr Who. 😂
Thanks for the answer. Hygger has the sub-statuses (in progress / done) in the stages, but unfortunately the limit only applies to the "in progress" sub-status.
Hello Gary. Thanks for another good class. Is it possible to add a column between DOING and DONE for those items that needs some external help or answer?. For example for some devellopment that needs to be consulted with some expert... It could have a limit to just 1 item.. Thanks!
We've used a mix of traditional, Agile, Scrum, and Kanban in our PM approach towards software/video game projects. The worse thing that comes up are egos and the term "Feature Creep." When you only have 5 months per project, feature creep is detrimental to your time and quality mgmt.
i have a problem with in solving with the flow but the organizayipn has limited the access of employees to do specific job only how can we do kanban in this situation
Not sure where you are on this journey, but my first question would be "why" is such a restriction in place? What happened in the past which caused them to start the restriction?
As always, great work. Just one wrinkle. what if something fails testing and needs Development work but you're grid-locked by all the previous columns waiting for testing to open a slot? Or is failing in the test phase not an option?
In a dev-ops environment, how would you blend shiny new features and boring maintenance tasks? Our stakeholders just don't want to know about the latter and it's irritating!
It is irritating, not least because the same stakeholders will be the first to shout when something breaks. This is one thing (among several!) that Scrum gets right: it's down to the Scrum Team - only - to decide what to select from the Product Backlog. The team is considered to be best-placed to pick the right mix of "shiny" and "boring".
@@Developmentthatpays Absolutely, I call it "getting it in the neck both ways!". Must look at trying to borrow this from Scrum. Obviously, we've also got a bit of imbalance between the dog and its tail that we need to address. Thanks for coming back, this is useful!
Great video! :) Does anyone has a Kanban for Marketing Agencies? We do some kind of Scrumban, and our board’s columns has each member of the team... which I think is not the best. I think we should use row as departments/members, and then create columns of doing, etc. Does anyone has other ideas to share? Thanks!
There are lots of non-software companies applying Agile methods - including Marketing Agencies. I agree that a work-centric board - rather than a people-centric board - is the way to go. Would love to hear how this works out for you.
Putting your head down and "doing your job" can break the system that you're in. Remember to look at the context in which your system is working and adjust accordingly.
Devs should not do testing. They know the inner workings of the system too well and will most likely test the happy path. Consultans and users will use the application in ways a dev would have never thought of.
Depends on the team. In my experience, it's easier for Dev to complete automated testing which allows Testers to complete the manual testing thus putting their efforts towards finding more complex breakage.
I disagree...devs can and should be part of testing upfront or side by side with testers as the team progresses which in turn clarifies feedback, granted it’s time to do that work the skills these Dev often benefits peer review or mentoring or learning hands on the go you know...
Hugues Peccatte no you misunderstood me...everyone as developers along side with testers can develop the work and their test scenarios...the goal is test automation so the results are testable being repeatable each time and gives both developers and testers assurance that all is good as their go along about their work knowing the outcome has been tested and their assumptions/goals/business rules are validated....perhaps as an analogy Doctor Who isn’t a specialist the Barista is however the Barista could tell the Doctor how to make standard coffee to his quality of making it (that’s up to him of course) while he is out for whatever reason and return later that Doctor can continue the business a bit longer on regular coffee.
We're back with the third and final part of the Coffee Shop Trilogy.
Watch out for a "special effect" that I've never used before!
Succinct language, crystal clear presentation - What more to ask for. All of the videos set a benchmark for understanding Agile concepts!
Absolutely love the tuber presentation/edit style, effective and lively!
So nice of you to say so. Thank you!
Just discovered this channel. Where have I been for so long? It's so wholesome.
big thanks for that series of videos. I realize now that I am doing kanban since ages then. 🙂
Excellent news!
Happy Birthday. Thank you for your ability to take complex applied theory and allow everyone to embrace knowledge and get it. That's an incredible gift that has made a difference in my life.
Perfect example. Clear, understandable and concise.
Thank you - much apprecaited.
Amazing work, explanations. Simply excellent, well done. Thank you
Thank you! Very nice of you to say so 👍
I really appreciate your humour! Thanks for the explanations :)
I think I learned more from these three videos than I have from all the in-office training my company has provided. Very good series.
That's really nice of you to say so. Glad you found the videos useful.
AMAZING! Love it.
Very useful Kanban videos! Thank you so much for your contribution and btw I liked your shirt on this video!
Stay safe and have a good one
This is so simple and well explain 👏
Hi Gary. Wanted to say thanks for your many teaching videos that have helped me pass my PMI PMP exam today. I know you are Agile focussed, but it has all brought me a greater insight to project management generally, but particularly Agile, scrum , and kanban. Thanks my friend....it felt like you travelled the road with me! Keep up the good work. 👍
Many congratulations. Great news!
Brilliant Gary! Thanks!
You're most welcome!
Nice compilation 👌👌👌
Thank you!
This is so helpful
Excellent, very useful! Thanks for this, I'm going to pin those principles on my board.
Glad you liked it. Pinning the principles to the board in a great idea!
excellent series:)
Thank you very much!
Hi Gary, thank you for the valuable content again. Can you please show how to create better "Pull system"? How to encourage people for "pull"?
Just remember this is free. Thank you 🙏
You're most welcome!
I simply love Gary
Awwww.
Nice explanation. I like it.
Glad you liked it
Great production quality yet again Gary!
Loved the Tardis effect, gave me a good chuckle :)
Ah ha! You spotted it!
Brilliant!
Love the video Gary :). One common thing that can be done and which is no secret to anyone and is part of the kanban principles and /or practices is to define explicit quality policies and criteria from one Column to another, kinda like a mini dod per column. i.e: What needs to happen in order for that element to go from column A to B?
Well done. One "other thing they can do" is invest in operational improvement to increase speed and capability. Tool development, for example.
Yes, agree 100%.
It seems I can use the Kanban concept can be used in business operations
Definitely!
Devs should go with scrum master to the playroom for foosball match. You would be surprised how quickly tests are done then... Seriously, great episode! Mr Pink beats even Mr Who. 😂
Ha! You're so right!
Gary, do you know any virtual tool that would implement the rules you gave (WIP limits on stage, stages split in doing/done, …) please? Thank you.
Jira has WIP limits. Trello also has WIP limits (via a power-up). But I'm not sure either support shared WIP limits.
I wonder if anyone else knows?
Thanks for the answer.
Hygger has the sub-statuses (in progress / done) in the stages, but unfortunately the limit only applies to the "in progress" sub-status.
Hello Gary. Thanks for another good class.
Is it possible to add a column between DOING and DONE for those items that needs some external help or answer?. For example for some devellopment that needs to be consulted with some expert... It could have a limit to just 1 item.. Thanks!
Yes, absolutely. (It's quite common to have a User Acceptance Test (UAT) column.)
We've used a mix of traditional, Agile, Scrum, and Kanban in our PM approach towards software/video game projects. The worse thing that comes up are egos and the term "Feature Creep." When you only have 5 months per project, feature creep is detrimental to your time and quality mgmt.
Feature creep is a killer.
Nice!
Thank you!
i have a problem with in solving with the flow but the organizayipn has limited the access of employees to do specific job only
how can we do kanban in this situation
Not sure where you are on this journey, but my first question would be "why" is such a restriction in place? What happened in the past which caused them to start the restriction?
Could you clarify what you mean? Does everyone in the team "do everything"?
As always, great work. Just one wrinkle. what if something fails testing and needs Development work but you're grid-locked by all the previous columns waiting for testing to open a slot? Or is failing in the test phase not an option?
In a dev-ops environment, how would you blend shiny new features and boring maintenance tasks? Our stakeholders just don't want to know about the latter and it's irritating!
It is irritating, not least because the same stakeholders will be the first to shout when something breaks.
This is one thing (among several!) that Scrum gets right: it's down to the Scrum Team - only - to decide what to select from the Product Backlog. The team is considered to be best-placed to pick the right mix of "shiny" and "boring".
@@Developmentthatpays Absolutely, I call it "getting it in the neck both ways!". Must look at trying to borrow this from Scrum. Obviously, we've also got a bit of imbalance between the dog and its tail that we need to address. Thanks for coming back, this is useful!
Great video! :)
Does anyone has a Kanban for Marketing Agencies?
We do some kind of Scrumban, and our board’s columns has each member of the team... which I think is not the best. I think we should use row as departments/members, and then create columns of doing, etc.
Does anyone has other ideas to share?
Thanks!
There are lots of non-software companies applying Agile methods - including Marketing Agencies.
I agree that a work-centric board - rather than a people-centric board - is the way to go. Would love to hear how this works out for you.
Putting your head down and "doing your job" can break the system that you're in. Remember to look at the context in which your system is working and adjust accordingly.
Genial
Youre fucking hilarious man love this shit.
Thank you!
Devs should not do testing. They know the inner workings of the system too well and will most likely test the happy path. Consultans and users will use the application in ways a dev would have never thought of.
Devs should be able to write tests until there are only happy paths left.
Depends on the team. In my experience, it's easier for Dev to complete automated testing which allows Testers to complete the manual testing thus putting their efforts towards finding more complex breakage.
I disagree...devs can and should be part of testing upfront or side by side with testers as the team progresses which in turn clarifies feedback, granted it’s time to do that work the skills these Dev often benefits peer review or mentoring or learning hands on the go you know...
Does it mean that if a developer tests something, noone else can test it? Damned!
"Guys, stop everything! Things can be tested only once!"
Hugues Peccatte no you misunderstood me...everyone as developers along side with testers can develop the work and their test scenarios...the goal is test automation so the results are testable being repeatable each time and gives both developers and testers assurance that all is good as their go along about their work knowing the outcome has been tested and their assumptions/goals/business rules are validated....perhaps as an analogy Doctor Who isn’t a specialist the Barista is however the Barista could tell the Doctor how to make standard coffee to his quality of making it (that’s up to him of course) while he is out for whatever reason and return later that Doctor can continue the business a bit longer on regular coffee.