Agile
When I write non-agile environment I do not necessarily mean an environment that does not use an agile methodologies like scrum or kanban. What I mean is an environment that is not agile. I made the following observations when I worked in such an environment. * there are a lot of
Agile
I wrote about our retrospectives already in an earlier article. In this one, I would like to write about my personal experiences of changes that your partner suggests to the meetings. I started using the way of holding retrospectives mentioned in the referenced article. I chose the structure as a
Agile
I experienced the pretty fast growth of a company I worked for, in which scrum is used as the development process. When companies grow, teams get bigger or new teams form. In my particular case the company used to have one scrum master - let's call him Jim
Agile
In one of my past articles I briefly mentioned the roles in a scrum team. One of them is the scrum master who guides the team to be successful applying scrum. But why do you need this role? Asking from a different perspective: what happens if you remove the scrum
Agile
A key point in scrum is transparency. To create transparency of the work of a team the board plays an integral part. A discussion point in multiple scrum teams I worked in was if the board should be digital or analog. I asked myself the same question when we started
Agile
When I started introducing agile methodologies in private life and in my family I thought I have to do it the right way. For me this included story estimation. It turned out that for me this is not the right way of organizing my free-time and projects in our family.
Agile
“Fail fast, fail often”. You read and hear this sentence a lot in the agile world. It is supposed to be a good practice. But why exactly is this a good practice - not only in agile? First of all, failing feels bad, right? You usually invest time and energy.
Agile
Nowadays kanban is considered to be an agile software development methodology. In fact, it is also a synonym for a token that is running through a kanban system. Kanban has its roots in physical manufacturing at Toyota. That was in the 1940s. At that time the basic idea was to
Agile
I already gave a short overview of retrospectives in the context of software engineering teams. There are several books for this available and I won't go into detail about this. What I would like to focus on in this article is how we in our family do weekly
Agile
I already presented my actual priority backlog in a former article. When I started using it I asked myself how I will be able to really work on the priorities I wrote down. The key of learning First things first: if you really want to learn something the key is
Agile
A sprint is an iteration and at its end user value should have been created. It includes the sprint planning at the beginning and at its end the sprint review and retrospective. The sprint includes short daily sync meetings called daily scrum or stand-up. The software engineering perspective The sprint
Agile
When a scrum team is founded one of the first things to do is to set up a working agreement. A working agreement is a contract between the members of a team. All members should adhere to the contract at any point in time. A working agreement in scrum usually