Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
If ATC were business systems, to which Agile is often employed, the requirements would change from "Aircraft must never be allowed crash under any circumstances" to "Crashing is mandatory where this is seen to improve the bottom line".
I never heard of anyone needing a design to test before.
I was under the impression you needed to know WHAT something is supposed to do in order to test it, not HOW it is designed, so yes, what's the design got to do with testing?
Being older than you lads, I was doing agile before it was called agile (approx 2001 AD). It was then called RAD.
I built RAD systems for eg BP and Shell. There was never any 'design'. If you'd asked me about such a thing then, we'd have had to go down the pub to mull over the consequences of such a new and fangled concept.
The Business told you what they wanted to achieve and you built them a system.
When I go out shopping on a Saturday I don't have a plan. Or a design document.
You young people are so bureaucratic I just can't get over it.
"Don't part with your illusions; when they are gone you may still exist, but you have ceased to live" Mark Twain
Being older than you lads, I was doing agile before it was called agile (approx 2001 AD). It was then called RAD.
Being even older, I've seen these fads come and go, given different names for the same bollocks, I've learnt to ignore them all and it doesn't seem to have hurt
“Brexit is having a wee in the middle of the room at a house party because nobody is talking to you, and then complaining about the smell.”
Comment