SDLC approach: SCRUM & Agile

You may know something about SDLC when you heard about "Waterfall" and "Agile".

People talking about Agile or Agile-like development might also talk about Scrum. Here's a bit digests from the specifications I came through:

For the term "Agile" as people normally say:

The Agile Movement (www.agilemethodology.org) notes that Agile is not in itself a methodology, but rather an alternative to traditional project management to try and help teams respond to unpredictability through incremental, iterative work cadences and empirical feedback. Agile methods are therefore alternatives to waterfall, or traditional sequential development. 

So, how about Scrum?

Scrum is described as the most popular way of using Agile and Agile-like methods and has based its assumptions around that approach. The use of the term Agile and/or Agile-like is intended to imply that Customer may be more interested in the principles of Agile as tailored to the project, rather than in strict adherence to any particular form of Agile.

Scrum is an iterative and incremental agile software development framework for managing product development.

In simple words, Agile is a mindset and Scrum is a method.

To get scrum fully implemented and make the software development truly agile, companies might need to adopt the necessary changes in management style, organisation culture, running processes and way of executing projects.

A bit of Agile Software Development

As the developers are always asked which methodology would be adopted in their software development life cycle. Most of the time they would say, "In a Agile way!" So, how actually should Agile development look like in real life?

Consider doing software development in Agile way, there are 12 principles which I can easily forget.

Now, let's forget them one-by-one:

The Agile Manifesto is based on 12 principles:

1. Customer satisfaction - Make it QUICK and CLEAN in terms of software delivery.
2. Welcome changing requirements - Be YES-MAN to your client, as always.
3. Frequent software delivery - Release it by weeks/days, of course, with QA tests done.
4. Close, daily cooperation - Love your business and talk to the client everyday.
5. Projects built around motivated & trusted individuals - Yes, we trust them so we work with them.
6. Face-to-face conversation - It means you should be there in front of your parties for TALKING
7. Principal measure of progress - It basically means NO Progress if software is NOT YET WORKING. So try your best.
8. Sustainable development - Keep your dev work RUNNING in constant pace.
9. Continuous attention to technical excellence and good design - We loves good things like STATE-OF-THE-ART/BLEEDING-EDGE technology.
10. Simplicity - LEAVE traces to ongoing work as much as you can, i.e., We don't have time for sure. Just keep it simple & get the work done.
11. Self-organizing teams - CONTROL YOURSELF.
12. Regular adaptation to changing circumstances - BE ALERT to the changes around you, and the project.