Thoughts on Software Development, .Net, OOP, Design Patterns and all things cool
I was chatting with a buddy last week and he told me that during a recent meeting, one of the consultants he was working made this statement. 'We need to hurry up and get to QA so we can get the requirements for this release'. If that one sentence does not speak volumes, I don't know what does.
When you get requirements during the 'QA cycle' (this shop is standard waterfall) does that make the QA cycle the elaboration phase? or the QA phase?
I still have a smile on my face 2 days after hearing this one. :)
About Derik Whittaker
Derik is a .Net Developer/Architect specializing in WinForms working out the northern suburbs of Chicago. He is also believer and advocate for Agile development including SCRUM, TDD, CI, etc.
When Derik is not writing code he can be found spending time with his wife and young son, climbing on his bouldering wall, watching sports (mostly baseball), and generally vegging out.