Whether you have fixed or negotiable scope contracts should have no effect on how you develop the software. Clearly, negotiable scope acknowledges the ...
I would agree it wouldn't matter if people acted like it doesn't matter. Unfortunately, the client and supplier on fixed-scope contracts are both selfishly...
I was involved in a fixed price contract in which we had an excellent customer-vendor relationship and a very agile approach. Unfortunately, to get the...
MessageI've delivered exact scope, but only on very short projects. Normally my customers never get exactly what's in the specification. But they're happy,...
I agree, but XP Planning still yields the optimal results in those bad scenarios. In a binary sense, yes, fixed:bad, negotiable:good. But that, of course,...
Sticky wicket indeed. That does not to me sound like a fixed/negotiable problem. It sounds like multiple-stakeholder problem. One of the Customer Team...
The fact that there were multiple stakeholders was not one which could be changed on this project, or on projects in general - if there are multiple ...
Recently I came across an article - actually a keynote address to the 16ht annual IPM world congress - by Martin Barnes. It contains a very interesting view...
I'm wondering about the "Do it right the first time" rule as stated at http://www.poppendieck.com/lean.htm. Is it accurate to say that "Do it right the first...
Hi Jason, I regret now the application of "Do It Right the First Time" from manufacturing to programming. I generally use the phrase "Test First" or "Build...
I think a better term is "Keep options open - avoid rework". If you look at Toyota's approach to design they use anticipatory techniques based on experience...
David - Programmer tests drive the loose architectural coupling you rightly advocate. It is very difficult to have every feature testable at the level TDD...
Today in an article in our newspaper Dale Dauten wrote an interesting piece which started out: "Here, in four words, is the unspoken assumption of bad...
Great points, Mary. Once when I was just starting a really risky project that would make or break the company I had a boss who was fantastic. I didn't learn...
Hmmm. I really see two points being made here. One is about the problems of IT scope on internal projects getting too big. The other is about products getting ...
... Hmmm- I've got a couple random reponses to this: 1) Over any given short time scale, (In particular, over the length of a given scrum) the scope has to be...
Hi all, I'm trying to understand the difference between Timeboxing and the iteration as used with the lean approaches. I'm in the middle of a discussion on...
While the notion of no fence around scope seems radical, it makes the point that we can't know what we could be providing at the outset of a project. Teams...
David, Are you sure that the Standish report on the ratio of unused features refers to software products? I was under the impression that it referred to...
Hi Clarke, I'd say that time boxing as it is currently used means that you decide for any iteration exactly what features you are going to develop within some ...
You may have a point here. I automatically recalled a similar presentation I had seen before specifically in relation to bloatware. If the same is also true of...
A couple of XP clarifications. * I always start with 1-week time boxes now, and 1-day timeboxes for a few weeks. * The amount of solid conceptual design we use...
Thanks Mary. Your answer has helped a lot. But it also raises an interesting point. A bit more of the theory behind why lean can be so successful. From what...
Hi Kent, Thanks for your comments. Apologies, but I didn't understand your first point. Can I ask you to clarify/expand. Do you start with 1 week time boxes...
Excellent point, Clarke. I like to list the seven wastes of software development, similar to the seven wastes of lean manufacturing. One of the seven wastes...
Sorry to be unclear. We start with 1-day timeboxes for the first 2-3 weeks, so people get a lot of practice estimating, writing stories, integrating, planning,...
Hi Pete, I agree with you, it is often very difficult to get a customer to set priorities. Sometimes I think it because it is a lot of work and they don't ...
I had a programmer tell me just the other day, "I don't trust product management not to screw up the business." What can you say? In this case product...
Hi, I'm new to this group, but I think that I have been using an interesting technique to help developers (myself included) to trust that managers are making...
