18 September 2011
OlafLewitz
What is Feature Injection? And how and why should that be applied to service delivery?
Recently, I worked with a service delivery team in a company that is currently changing into an agile product development organisation. The company develops and runs one of Germany's biggest websites. Let's call them Awesome Online. After introducing Scrum and Kanban to all development teams over the past two years, executive and product management have started to introduce agile and lean thinking into the organisational structure and culture.
Motivation
A main motivational factor for the development teams was the definition of product visions for all products, and the application of Feature Injection as introduced by Liz Keogh to ...
19 May 2011
OlafLewitz
Why does your project need a product backlog? Or, does it actually need one, and why? A discussion on Twitter led me to these ponderings... As always, I'm very interested in your thoughts!
Olaf Lewitz
agile42 Coach.
Visiting Business Influencer and Linchpin.
My motto is that of NannyMcPhee: "When you need me, but do not want me, I must stay. When you want me, but no longer need me, then I have to go."
- On
- 19 May 2011
- In
-
Scrum
- Tags
-
backlog,
bdd,
lean,
pull,
waste
Is A Backlog Waste? Yes. A backlog is inventory and inventory is waste. Simple question.
Does that Help?
No. Depending on your system, some amount of waste will be necessary to be able to keep the flow. Where would you pull stories from if there is no backlog? Directly out of the product owner's mind?
Context
If you need a backlog and how much of it depends mainly on two factors:
- the experience of your team and the product's stakeholders (including the level of trust between them), a.k.a. the maturity of your system, and
- the context ...
7 July 2008
andreat
One of the "assumption" that is often made, when starting to adopt Scrum, is that there will be a Product Owner and there will also be a Product Backlog. Well, it happens that the Product Backlog quality is one of the major responsible for the outcome of what the team will produce in terms of software, and is absolutely one of the most difficult things to work out. There are many problems related to having a right Backlog in place, and as you may guess there is no "one recipe" for the right Backlog, only some important ingredients to mix up in the right way ;-)
Product Backlog: Requirements or User Stories?
Hi there, spending some extra time at the airport (thanks to lovely pilot strikes) gives me the chance to write a bit about Scrum and the Product Backlog. A Product Backlog is a stack of "features" prioritized by Business Value, which means that on top of the stack there is always the most valuable item for the customer/client.
The owner of the Product Backlog is the Product Owner and as such should be the one and only authorized to make changes to the Product Backlog, given also the fact that the main responsibility ...
