Author Archives: trond
As you probably know, I’m an agile guy – as a practitioner, enthusiast and project manager. I’m also a certified PMP (Project Management Professional) – or a “real project manager”, as one of my agile friends jokingly remarked. I’ve been … Continue reading
As you may know, I left Steria and joined Statkraft June 1st this year. One of the things that I looked forward to in Statkraft, was the opportunity to work long-term with the same team. How good can we become? … Continue reading
In part 2 we looked at how an improved value process can rectify the shortcomings of a Product Backlog / User Story oriented standard agile approach. The main component was introducing two levels of quantified goals; Stakeholder Goals and Product … Continue reading
So, let’s summarize where we are so far. The value process in agile software development projects is flawed, and the Product Backlog is at the center of it. It normally goes something like this: Flawed Value Process The customer has … Continue reading
(I did a lightning talk with this title at XP2010 in Trondheim, Norway, and thought I’d do a write-up of it as well. This is part 1.) Ok, we all want to create value with your software projects. Using agile methodologies is … Continue reading
So, today is my last day at Steria Norway. It’s been a great three-and-a-half years here, and Steria is without competition the best place I’ve worked so far – even considering the one year or so when I was self-employed … Continue reading
Today something clicked for me. I’m working on my lightning talk for XP 2010, entitled The Product Backlog Hinders Value Creation. I typically do from six to twelve “real” presentations a year, and I want to be good at presenting. … Continue reading
The agile manifesto (www.agilemanifesto.org) was created by a group of very bright and experienced people. However, these people all came from the supplier side of software development, something that’s evident already in the third of the four value statements: Customer … Continue reading
In Part 1 of this series, I showed how frequent releases and prioritizing features increased the value of a project. In this Part 2 we’ll see what happens when things don’t go exactly according to plan.
You may have heard or read that frequent releases can improve project economics and ROI (return on investment). Here’s the math.