Having wrote several blogs about what an SDLC is, what’s it benefits are and the different types of SDLCs, it is important to consider whether or not it is worth it for a business?
Is a systems development life cycle a waste of time and resources?
According to one IT specialist, he has worked on several IS projects and finds more often than not that strictly following SDLC procedures can often double, triple, or more the length of time spent on a project. SDLC often takes longer than the coding and testing itself! Does that make sense? Or is it just something to keep project managers and analysts going?
I would agree that it takes time but often taking a little more time in the beginning will save a lot of time in the long run. It ensure that the delivered system conforms to the requirements and hence this saves time in the future on altering the system. It produces a much higher quality product, measured in defects as variations from specifications. It should also mean that maintenance work is much easier.
One of the problems with SDLC as it is practised in many companies is that there is little technical involvement at the beginning and not much flexibility. Often requirements are passed to the technical project team before the team can actually work on it and improve it. Technical decisions are made too early on.
Possible solutions? Having some people who are both functional/business and technical. Experts that can both submit in to the requirements and design process and also be part of the development team. This will also save time as info does not need to be constantly passed between functional and technical teams. Hence the project becomes more efficient for the business.
Therefore I would argue that having an SDLC is not a waste of time or resources. It is simply a way to plan the project so that it has a higher chance of succeeding and satisfying the users needs. It may take longer but at least there’s a high chance of getting it right the first time!