test please delete

[Diver]

\/

Without sneaking a peek using quote

[BrowneIssue]

... we (yeah, like it was my idea) thought that if we used a cycle of just a couple of weeks, then if we went off the rails we could afford to write off the work.

[Diver]

Where is everyone tonight ?

[BrowneIssue]

However, writing off work has a bad effect on programmer morale. Hence the idea of prototyping: producing 'fake' programs that 'pretended' to accept real input but in fact were just a series of screens. The input was ignored.

[BrowneIssue]

We wrote a script to go with the screens and this drove the fortnightly (ish) prototype meetings.

We showed what we intended to develop during the next cycle and got their feedback before writing anything in anger.

So, the prototype WAS the program spec! Outrageous!

[Diver]

You will not be distracted will you ?

[BrowneIssue]

So writing off a prototype was no big deal - a few hours work so no negative programmer morale issues. Win + Win!

[BrowneIssue]

You will not be distracted will you ?

No.

[BrowneIssue]

So there we were, 15 years ago, using a development methodology with these attributes:

- loads of user communication;
- prototyping;
- tight development cycles of only a few weeks;
- light documentation.

[BrowneIssue]

Was it Agile programming?