I'm Brazilian (don't know speak English), but I understand some things. Congratulations for your video, you explaned so good and simple, thank you very much.
Switching to Scrumban can be a great idea. I took over a scrum team one year ago. They never met a sprint goal, the burndown chart was quite flat. The basic scrum workflow that was recommended did not fit to the team process. The reason was, that the team was not cross functional. There were specialized FE and BE developers, experts for test automization and manual testers. So we kept the working artifacts, but switched to a complex workflow in a Kanban board which includes a swimlane for emergency issues. I think we are on a good way now.
Wow... I never enjoyed listening to someone like I'm doing right now, it seems learning this knowledge is a breeze with you. If you ever get to wander on the other side of the world, I'm more than willing to be your guide and bodyguard. :)
Looks like kanban is not your biggest strength :) Other videos were amazing. This one has a lot of assumptions and some advice which might not be always a good choice or true. Anyway, I think you are doing a great job. Keep on doing a great job. Subscribed! :)
Thanks for feedback! I think I know what you mean and this is a long conversation ;-) Long story short, I simplified it because I struggled with it when I started with Agile. And back then I would’ve appreciated a little simplification to grab the basic concept. Nonetheless, I emphasise that the best way to find a good fit is through experimentation. I’d love to talk about it more, you can reach out to me via LinkedIn www.linkedin.com/in/mariachec/
I'm Brazilian (don't know speak English), but I understand some things. Congratulations for your video, you explaned so good and simple, thank you very much.
Thank you so much! :)
Switching to Scrumban can be a great idea. I took over a scrum team one year ago. They never met a sprint goal, the burndown chart was quite flat. The basic scrum workflow that was recommended did not fit to the team process. The reason was, that the team was not cross functional. There were specialized FE and BE developers, experts for test automization and manual testers. So we kept the working artifacts, but switched to a complex workflow in a Kanban board which includes a swimlane for emergency issues. I think we are on a good way now.
Hey Markus, thanks for sharing your experiences with switching or better yet, adjusting frameworks to the teams needs. Great stuff!
Continue the good work 👏
Love this video!
Gracias, un buen resumen y criticas interesantes!
Wow... I never enjoyed listening to someone like I'm doing right now, it seems learning this knowledge is a breeze with you. If you ever get to wander on the other side of the world, I'm more than willing to be your guide and bodyguard. :)
Thank you, John! You made my day! Which part of the world is that exactly? :)
@@AgileStateofMind I'm from Philippines, the land of smiles.
@@bienbaterna that sounds lovely! 😊
Chrystal clear! Thanks
Great video!
Looks like kanban is not your biggest strength :) Other videos were amazing. This one has a lot of assumptions and some advice which might not be always a good choice or true. Anyway, I think you are doing a great job. Keep on doing a great job. Subscribed! :)
Thanks for feedback! I think I know what you mean and this is a long conversation ;-) Long story short, I simplified it because I struggled with it when I started with Agile. And back then I would’ve appreciated a little simplification to grab the basic concept. Nonetheless, I emphasise that the best way to find a good fit is through experimentation. I’d love to talk about it more, you can reach out to me via LinkedIn www.linkedin.com/in/mariachec/