agilescrumsdlc
For small size projects, is it worth following the SDLC? is SCRUM/agile development a better approach?
Edit: The project I have in mind is a small change but it will affect multiple layers/parts of the application, so there will be 2 or 3 developers involved each from a different team, then the code will be integrated at a later step.
Thanks.
I believe if you're using Agile development as an excuse for cowboy-style programming, then you're not really following Agile development. Cowboys will always be cowboys, no matter what process you give them.
It's not possible to have effective scrum with such a big group. Even with twenty-something you begin to struggle. You have to divide these 100 people into much smaller task groups, which each group having their scrum. Then you can have scrum of team leaders/representatives. This is known as the scrum of scrums.
Best Answer
SDLC stands for "software development life cycle" or sometimes "system development life cycle," and it refers to the process that you follow for developing your product. There's no single SDLC process that everyone follows -- you're free to define your own, and to change it as the project (or your organization) grows. The point is to have a defined process, preferably one that's written down, that you follow for the work related to development and maintenance of your project. The alternative is to work by the seat of your pants, making things up as you go along.
So, if you want to use Scrum or some other "agile" methodology in your process, that's perfectly fine. Just write it into your SDLC and you're good to go.