Here you will find everything related to Agile, Scrum, Kanban, Eduscrum and every other Agile approach i write about. Actually anything that i use in my day to day work to make things work better with the team i function in. Everything that keeps me busy and i want to share knowledge about is to be found here. I am also very interested in topics and subject about Flow. It is a word that is easy said but hard to find within teams that work together. Real Flow makes you thrive as a team.
Master hotfixes in Kubernetes with Docker. Learn to rapidly deploy critical fixes in a CI/CD pipeline focusing on streamlined branching. Perfect for tackling urgent issues without disrupting flow. Dive in now.
Exploring CI/CD with Docker & Git. Mastering deploying Docker artifacts via Git branching. Dive into strategies for DEV, STAGING, PROD environments. Perfect your pipeline!
I first learned about Scrum way before the 2020 manifesto update was in place. So when we went to a Scrum master training after this 2020 release we had a nice little discussion about the change that has had the most impact with me since this update to the Scrum guide.
Changing a word like "Sprint" wont mean anything if you dont foster an environment in which the words rush and haste aren't words that describe the work ethics. A sprint is just about an x week development cycle everyone understands, it shouldn't be at all related to haste and rush.
I am already for a while intrigued by transforming a business into a DAO (Decentralized autonomous organisation). Thinking of my role as a Product Owner i thought of a way that can work very well when transforming a part of our business into a DAO
Without a "good" SME (Subject Matter Expert) stance within SCRUM, every product is a lesser product then it can be. That's why this is one the most interesting misunderstood stances of a Product Owner to me.
In this post, I will share the experiments we conducted during the last three sprints with our physical Scrum board. The focus was about creating a better understandable visual representation of our sprint progress. Sprints are two weeks increments for us at this moment.
In this post I share our current journey of implementing Scrum and Kanban principles with my team, this is mainly about emphasizing the importance of real collaborative work and instilling a product vision which helps us to achieve FLOW which translates to high value Scrum for us.
This post explains how we as a team manage our current Board on which we keep our sprints. This board is leading over Jira we love working analog next to our digital work.
