en-us https://www.intensedebate.com/users/793849 Comments by Geir Berset http://aptoma.com/select.star/2010/10/31/3-more-industry-problems/#IDComment107554310 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. Wed, 3 Nov 2010 09:25:47 +0000 http://aptoma.com/select.star/2010/10/31/3-more-industry-problems/#IDComment107554310 http://aptoma.com/select.star/2010/10/31/3-more-industry-problems/#IDComment107351545 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? Tue, 2 Nov 2010 13:49:09 +0000 http://aptoma.com/select.star/2010/10/31/3-more-industry-problems/#IDComment107351545 http://aptoma.com/select.star/2010/02/22/a-first-look-at-javascript-frameworks/#IDComment69809791 Thanks for the tip, we'll check it out. Thu, 22 Apr 2010 20:30:02 +0000 http://aptoma.com/select.star/2010/02/22/a-first-look-at-javascript-frameworks/#IDComment69809791 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment69804580 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. Thu, 22 Apr 2010 19:47:59 +0000 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment69804580 http://blogg.abrenna.com/hva-er-gravemaskinen/#IDComment59716274 Stå på. Lykke til videre i prosjektet ditt. Thu, 4 Mar 2010 10:06:46 +0000 http://blogg.abrenna.com/hva-er-gravemaskinen/#IDComment59716274 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58623476 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. Thu, 25 Feb 2010 09:17:51 +0000 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58623476 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58622903 Vi kjørte 30 i starten, men for det meste kjørte vi 14 dager. Thu, 25 Feb 2010 09:10:12 +0000 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58622903 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58622830 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. Thu, 25 Feb 2010 09:09:09 +0000 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58622830 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58622605 Thanks, it's nice to hear that you draw some inspiration from our experience. Thu, 25 Feb 2010 09:06:18 +0000 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58622605 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58622578 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. Thu, 25 Feb 2010 09:05:56 +0000 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58622578 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58622489 Thanks. We'll keep you posted on our progress with continuous deployment. Thu, 25 Feb 2010 09:04:59 +0000 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58622489 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58622404 We have one team which is co-located in a shared office environment (no walls between each of us) and we have one person in another city (Gothenburg, Sweden) We use IRC for a lot of the day to day communication, even between the co-located individuals, as it is less disruptive for the receiver (i.e. you can finish what you are doing before checking messages), and for the group as a whole. Also using IRC will include the person in Sweden so he is up to date on the osmotic micro-communication. Thu, 25 Feb 2010 09:03:30 +0000 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58622404 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58622111 Thanks for your feedback. I have only a small correction -- we did not use 2 days for planning. We time-boxed it to 4 hours -- still it was too much at once, and not enough ongoing planning as we had already discussed the details during our 4 hour session. Thu, 25 Feb 2010 08:59:22 +0000 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58622111 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58620389 Yes, I shall admit to being a student of kanban and other lean practices which has also influenced how we work. I have not read the book you are referring to, however. Thu, 25 Feb 2010 08:34:46 +0000 http://aptoma.com/select.star/2010/02/11/no-scrum-no-more/#IDComment58620389