IntenseDebate - Geir Berset

13 years ago @ select * - 3 More Industry Problems · 0 replies · +1 points

One more thing.

Just-in-time planning of details frees a lot of time of prematurely fooling around with too many details. This freed time should be spent analyzing the 'big picture'. Bby understanding long-term strategy for the project, this insight will translate into well-informed design decisions early on -- such as creating a loosely coupled architecture at the right places which again will lend itself nicely to refactoring into future needs. All of this without significantly impacting us today with a lot of assumption-based development.

It becomes the best of both worlds. We are able to make small (but significant) investments for the long haul, while not losing focus on the imminent challenges.

13 years ago @ select * - 3 More Industry Problems · 1 reply · +1 points

Thanks for the comment.

If I understand your use of "dynamic story card development" correctly, I agree with you. Keep planning on a strictly business value/strategic level. Break into details when it gets in line for implementation, just in time. Thus, details should only exist on ongoing work, not future work. This removes a lot of the need for extensive tools and backlogs. I really believe in going all-in (Tom Gilb-style) on ongoing work -- specifying and measuring everything -- but never on future work. Specs will be good only when we have as much knowledge as possible while writing them. We do not have future knowledge now, so we must wait until the last responsible moment.

I think this is what you mean by dynamic story card development?

14 years ago @ select * - A first look at JavaSc... · 0 replies · +1 points

Thanks for the tip, we'll check it out.

14 years ago @ select * - No Scrum, No More · 0 replies · +1 points

Agreed. We sometimes work where not only solution is unknown, but also customer need is unknown. Also, uncertainty varies during a project, which makes us lean toward flexible length sprint planning most of the time.

14 years ago @ Anders Brenna - Hva er Gravemaskinen? · 1 reply · +1 points

Stå på. Lykke til videre i prosjektet ditt.

14 years ago @ select * - No Scrum, No More · 0 replies · +1 points

As much as I love a good round of unbiased total immersion to experience both the upsides and the flaws of something, I do not believe it is always necessary. Scrum was our first formal experience with an agile methodology, and thus we decided to go all in. Scrum turned out to be less agile than we had more intuitively worked before, but the experiences were very useful, and we are still very inspired by it, although with the aforementioned adjustments.

I guess my answer is plainly: I don't know.

We will definitely not go all in on the next agile methodology that shows its face, but we will surely draw inspiration from it.

I know that did not answer your question, but I hope it provided a little insight anyway.

14 years ago @ select * - No Scrum, No More · 0 replies · +1 points

Vi kjørte 30 i starten, men for det meste kjørte vi 14 dager.

14 years ago @ select * - No Scrum, No More · 0 replies · +1 points

Thanks for the tip. We are working on automating everything about deployment and testing, but we have yet to use a framework for it, we are rolling our own. Automation is key to low cost, frequent deployments, of course.

14 years ago @ select * - No Scrum, No More · 0 replies · +1 points

Thanks, it's nice to hear that you draw some inspiration from our experience.

14 years ago @ select * - No Scrum, No More · 0 replies · +1 points

We just switched to Intensedebate, and I seem to have missed the point completely. My reply is further down the page for this one. ;) Thanks for the comment.

IntenseDebate Comment System

Connect with Geir Berset

People I'm following

Geir Berset