3 ms·
During some crunch times, I've told our business analysts that it's not a bug if they have to write a requirement for it (the bug) :) And, in an ideal world, r
by wallflower 19y ago
During some crunch times, I've told our business analysts that it's not a bug if they have to write a requirement for it (the bug) :)
And, in an ideal world, requirements would be stable before coding starts. We make the best of what we can work with. Cost, quality, functionality - the classic triangle - you can't impact/maximize one of those three without affecting the others
- edw519 19y ago"in an ideal world, requirements would be stable before coding starts" It is and they are. I think the common misconception is that requirements change during the project. My experience is that this is a rarity What really happens is that OUR VIEW of the requirements changes during the project. The business rules didn't just suddenly change because we are building something. We NEVER NAILED THEM DOWN in the first place. This isn't hard to comprehend; analysis is a lost art and probably the most fragile link in the SDLC chain. "What do you mean, when we file the record, a traveler should print out next to the supervisor's desk? Who told you that?" "Joe did." "What did Mary say?" "I don't know. I didn't ask her." "Ask her. Once you get her answer, change the specs." (A silly little example, but is I had a nickel for every time that happened...)
- dhimes 19y agoIn my experience, this depends a lot on the project. Often, with new ideas, new uses will come up once the 'opinion leaders' get their hands on something real. Then, the requirements, in fact, do change (if you're smart).
- edw519 19y agoWow, wallflower, you got me to reply twice to the same post. Good job! "you can't impact/maximize one of those three without affecting the others" As soon as someone finishes saying "can't", I start looking for the business opportunity.
- dgabriel 19y agoIf you think you can solve the classic "Good/Fast/Cheap - pick two" conundrum in a way that is ethical and sustainable, then go for it. That's the grail in more fields than just software.
- edw519 19y agoI think the startup mindset is to find a way to get all 3 for your customer. The example I always like to use (dated, but classic): In 1950, travel from NY to LA: - most comfortable: train - cheapest: car - fastest: plane In 2000, travel from NY to LA: - most comfortable, fastest, and cheapest: plane Thank you, technology. How can we do the same thing today with bits and bytes?
- dgabriel 19y agoI totally see what you mean, and technology has brought the formerly impossible into the reach of millions. Technically, however, the absolute cheapest way to get there is to borrow a bike and some camping gear and start pedaling, and the absolute fastest way is to hop into your own private jet waiting in your backyard. The first is waaaay too time-consuming for most people to consider reasonable, and the latter is too expensive for most people to attain. Commercial air travel is the best compromise between the two. The problem with most clients is that they want a private jet at borrowed bicycle prices.
- edw519 19y ago"The problem with most clients is that they want a private jet at borrowed bicycle prices." Not my clients. At least not for long. You bring up extreme outlying cases that are beyond the scope of my example. (How's that for hand waving?) OTOH, what if you could find a way to satisfy those "unreasonable" customer demands? How much further ahead of your competition would you be?