Of course not! As with all things, there are several ways to do the same thing. A small business method could not follow the SDLC (Software Development Life Cycle) at all, but upon closer examination it might have traces of the SDLC process and they do not even know they are using it regardless of their belief.
When your home computer is broken and/or you want to upgrade it, you take it to your favorite computer store or you do it yourself. This meets the definition of a project.
Does a simple repair or upgrade require an elaborate SDLC? ...for the most part no. It is reasonable and manageable to do it without SDLC.
The scale usage of SDLC:
- BIG: Use SDLC in all it's glory for big business and big projects, but not as company LAW.
- MEDIUM: Use a scaled down version(s) of SDLC for medium size business and projects.
- SMALL: Use a checklist type format and/or quick evals without all the massive detail of a formal SDLC.
- REALLY SMALL: For really small projects and small business hardly any SDLC at all is needed.
Ok, lets scale this a little more. Lets say you have 35 computers to upgrade. Would you need a SDLC. ...yes and no. I would highly recommend that you come up with an action plan and costs before taking on such a project both for your sake and the customers.
Finally let really scale this up. Lets say you now have 10,000 computers to upgrade. Would you need a SDLC. Absolutely yes There are too many devices and too many variables that not having a SDLC could result is a huge disaster and be very costly. Then everything that is being taught in the lecture and text are applicable to a very high degree, and yes you had better have your CYA component in place.