I was asked to speak at Software Passion Summit after a friend and colleague of mine, Portia Tung, was unable to make it. This was my first time speaking at a conference 🙂
When: 19th March 2012, 2 days
Where: Göteborg, Sweden.
Description
Software Passion Summit is a developer conference with a passion for software development. The Software Passion Summit is going to be held the 19-20th of march 2012 at the Clarion Hotel Post in Göteborg, Sweden. The Software Passion Summit is a gathering of software professionals from every part of Scandinavia and the world. As software has become more pervasive and important as well as more complex and challenging, there is a growing need for software professionals to come together, meet, and exchange ideas. This conference will provide attendees with valuable opportunities to learn new skills and techniques, discover the latest innovations in software tools and technologies, share best practices, and network and build new relationships with other highly motivated software professionals.
We have created this technologically open conference to support the developer community in Scandinavia to develop their skills and create new innovations. This conference will cover multiple topics in software development such as: software platforms, development techniques, new languages, frameworks, and future directions. Specific topics include: cloud computing, Mobile and Web development, testing, and security. The conference will cover platforms from Java and .NET to IBMi and many others.
While the technology forms the core of the conference, we do more than just work at the Software Passion Summit. The evening before the conference there will be a welcome dinner and the evening of the first day we will have a cocktail reception for all attendees where we can exchange ideas and discuss challenges that we face in an informal setting. This is a conference designed to support your passion for software.
(Source)
My talk was on using an economic framework for prioritization, using cost of delay.
Commentary and Feedback
Zsolt Fabok wrote a nice overview of the conference. In particular, his conclusion about the focus of the conference was spot on:
I was really happy to see that speakers talked about the product and value and not about methodologies and techniques. Nobody – at least nobody I was listening to – wanted to sell Scrum or Kanban, because these don’t matter. The goal is to deliver usable product and not to implement a methodology.
Björn Tikkanen also blogged a nice summary of my talk:
Introducing an economic framework to prioritization – Özlem Yüce
The last session of the day felt like a fresh wind, with a lot of focus on numbers and money. Real things and less emotions than many of the other topics, or atleast it felt like this. Özlem talked about how Maersk uses a process for prioritization that is built on risk, time to market and reward.
“We want to fill the development pipeline with the most profitable ideas”. Don’t just do things, do the things that leads to some value for the company. This means “putting a pricetag on time : cost of delay”.
The different benefits to look at are :
Increase Revenue; Protect Revenue; Reduce Costs; and, Avoid Costs.
I feel myself that we don’t look at all these four very much.
Ozlem also talked about the method of CD3, Cost of Delay Divided by Duration as a measure for what to do next.
A good way to keep it agile is to “split the benefits, release continuously and look at the dollars”. A nice side effect of their work with these methods is that they “went from yelling and screaming to looking at pure data (dollars) in their prioritisation meetings”.
There were also a few comments made on Twitter:
Now for us #agile nerds: an economic framework for prioritization, presented by Ozlem Yuce.
— Software Passion (@SoftwarePassion) March 19, 2012
She comes from Maersk. Software intense logistics. Since 3 years they have adopted agile. They were inspired by lean ideas. #spse2012
— Software Passion (@SoftwarePassion) March 19, 2012
At Maersk they say: fill the ships with the most valuable cargo. Now they say: fill development with most valuable requirements. #spse2012
— Software Passion (@SoftwarePassion) March 19, 2012
They needed a method to prioritize, against manager's feelings. They put a price tag on time: Cost of Delay for each requirement. #spse2012
— Software Passion (@SoftwarePassion) March 19, 2012
Different products have different costs associated with being late to market. That cost structure defines the Cost of Delay. #spse2012
— Software Passion (@SoftwarePassion) March 19, 2012
Do root cause analysis on the requirement to identify the benefits. Then quantify the benefit in money. #spse2012
— Software Passion (@SoftwarePassion) March 19, 2012
The method shows very convincingly how expensive it is delaying releases. Release early, release often, and earn money! #spse2012
— Software Passion (@SoftwarePassion) March 19, 2012
Prioritize depending on cost of delays. #spse2012
— Software Passion (@SoftwarePassion) March 20, 2012
Now Tom Gilb about driving software projects using quantified value. Like Ozlem Yuce’s talk yesterday? She is here listenining. #spse2012
— Software Passion (@SoftwarePassion) March 20, 2012
@portiatung Bad thing: we missed you. Good thing: the replacement you hinted about was brilliant and thought provoking. — Software Passion (@SoftwarePassion) March 21, 2012
And the first day of #spse2012 from my point of view http://t.co/rgAJwGxN @OzzieYuce #janbosch @ZsoltFabok @stack72 @SoftwarePassion — Björn Tikkanen (@BjornTikkanen) April 3, 2012