dustinleblanc
You can accomplish this with agile development:
1. People meet at the beginning of the project and say "heres what we think our washing machine needs"
2. They create a backlog based on those features
3. They start working and implement some features.
4. They find out they don't actually need the washing machine to wink and smile and say its done in a fancy british accent. It was a silly idea marketing came up with that adds no value. They drop that feature from the backlog.
5. They find out making the machine text you when your laundry is done is a desirable feature, they add it to the backlog.
6. Management says the competitor is launching a month earlier than us so we need to accelerate the time table. Engineering gives them the hard news that they need to sacrifice some features. They look at what they have left to do and prioritize the important items and drop the feature for the washer tie-dying your clothes if you want from the backlog.
6. Project enters qa, all tests are passing but testers found a bug. They write a test to confirm and reproduce the bug, they squash it and update the build.
7. Software is working, launch happens, everyone celebrates.
Nothing here says the software has to change anymore; its done, its shipped, its good to go, and done using scrum/agile.
There are plenty of agile/scrum teams who run continuous integration that won't allow code that breaks a build to even be in production. They write integration tests and acceptance tests and all of it is done with sprints and iteration.
Agile does no encouraging of adding features. It simply gives you the freedom to choose which ones get implemented based on the current knowledge rather than be forced to make those decisions based on 18 months ago knowledge.
"hey here's a feature we're pretty sure we need:
As a foo, I need to bar, So that baz
okay, write the test, make the test pass, refactor"
What about that isn't possible in agile?
Who ever said you don't plan in agile and scrum? Where does the magical backlog you start the project with come from?
The point is not to pretend you know things that you don't. You have a severly flawed interpretation of what agile means.
Perhaps an alternative would be some declaration that says "Hey render me this way if you feel like it, but use these all powerful browser supplied styles if I become unreadable"
Some browser's have implemented that reading mode (safari?) and it seems like a cool idea, but I think it only works if you provide really good HTML5 markup.