Are you really delivering value, or are just making sure people work hard?
Marcus Ahnve
Short talk - in English
So now that everyone and their dog is agile, what really changed? Are we really „delivering more value in less time“ as many agile methodologies promise. What do we even mean by value? How do we know when we’ve delivered value? When we’re "done" according to our "Definition of Done", or when we can validate that a feature is being used by our customers?
Most organizations that implement agile methodologies mistakenly believe that implementing the process according to spec is the goal. In reality it doesn’t matter how many certifications you have if the product you are building does not meet end users expectations.
I will talk about:
- Why every organization tries to be a factory, and why it is a bad model for software development.
- Why projects are a mostly bad way to organize software development.
- Why counting features is not really measuring value, and what to do instead.
- It doesn’t matter if you’re "done"