TAG | SCRUM
Yesterday I went to a pub with friends. One friend arrived late after the rest of us had already eaten. She ordered something to eat anyway and about 40 minutes later she asked for it again only to find out that the waiter forgot her order. So he was send to the kitchen and within just under 10 minutes her food arrived.
I instantly had to think of the company I work for.
I was talking to a friend the other day who told me about a scrum team he recently met. He said he was irritated by the amount of rules and rituals they employed. Everything was done by the book.
And it felt wrong.
While the product owner (me) was away on holidays the scrum team launched the renewed website of the Financial Times Deutschland.
And did a great job! (more…)
Just into the fifth sprint of my Scrum project I can sum up what I think about my life as a product owner. The experience has largely been a positive one with only few negatives.
However being a product owner doesn’t cut it for me.
Many of you will adore the idea of Scrum and might have had a good experience with it so far. However I think it highly depends on your working environment if Scrum can actually be of help.
When needing fixed deadlines for example.
Any web project, well any project really, should be done by a team that includes developers and project managers or product owners alike and they should act like a team.
As it often turns out this will not be the case when problems occur.
Currently entering the fourth sprint I thought it would be a good time to give an update on being a product owner. Part-time that is as I can spend only some percent of my time to this project while I’m involved in many others at the same time.
However I learned that Scrum actually nicely allows myself not paying attention.
As a product owner I want to follow a process that adapts to my current working situation so I can take on my responsibilities within the project as well as with the rest of my work. One sprint ago I stopped writing user stories alone and instead do it with the team.
Now one sprint later I tell you how it turned out.
There are three things to consider to any given IT project: scope, time and quality. You can only fix two of them and the third one need to be able to scale to allow for the others. You can run out of scope, out of time or end up with dirty code. Your choice. That’s why we want to use agile methodologies like Scrum.
Most of the time quality will be the loser..
Following yesterdays post I had a little discussion with a colleague of mine who is a scrum master and working in a Scrum project himself. In the end we argued about whether it’s ok to change the Scrum process to fit your working situation or whether it should be the other way around.
Needless to say I prefer to bend the process.