Reasons You Don't Need WinA&D

Next time your software manager mentions time-to-market, defining requirements, software design, quality or customer expectations, here are reasons you can use to convince him that WinA&D isn't needed on your project.

  • I'm too busy rewriting code to waste time on software design.
  • They'll be plenty of time after the code is written to sort out the requirements.
  • If we document requirements, product testers will report too many bugs.
  • Unstructured code is great for job security.
  • The original developers will always be here to explain how it works.
  • I prefer creation from scratch rather than reuse of tested, field-proven code.
  • Our applications are not important enough to require actual design.
  • I'd rather type thousands of code lines then click a generate code button.
  • Programming time is cheap, why be concerned with efficiency.
  • New hires can be productive without understanding legacy code.
  • Our customers don't expect software that satisfies their requirements.
  • I never use a map on a cross country road-trip.
  • Less than 60% of software projects fail, why can't you be more of an optimist.

Goto Excel Software Home Page