Tag Archives: #AgileMyth

Agile Myths: User Stories – a mandatory format for Scrum Teams?!?

The User Story format is often used by Scrum teams to document requirements. It’s a short syntax that sounds totally simple, but when we sit down and try to fill this syntax with life, we quickly realize that it’s not that easy. Some of you may have stumbled across user stories that somehow sound “artificial”. So what is it about this little sentence? Why do so many people use it? And do Scrum Teams have to document requirements in the user story format? Don’t they otherwise make a “real” Scrum? Continue reading Agile Myths: User Stories – a mandatory format for Scrum Teams?!?

Agile Myths: Agile Solves all my Problems

 Agility – the solution to all problems: We no longer run over project time and budget, our clients are always satisfied with the results of our work and we work fulfilled and motivated. Agile methods are often seen as a way to achieve such results. But does such a miracle cure even exist? One thing is for sure, there is a market for this demand as well.

Agile Culture

Agility provides one thing above all, a culture with values and principles that can change a company from the ground up if you get involved in it.

Continue reading Agile Myths: Agile Solves all my Problems

Agile myth: Writing user stories is Product Owner work

Again and again I am confronted with the statement that only the product owner writes and prioritizes user stories. The Product Owner is the person who prioritizes the Product Backlog. But for reasons I don’t understand, many people seem to be convinced that it is a core task of the product owner to sit down at his desk and write a user story until it is ready for a sprint. Is that really what the Scrum Guide says? Continue reading Agile myth: Writing user stories is Product Owner work