Agile Methodology, an analysis to its title

Agile Methodology:

  • an approach to project management
  • it works at iterative, incremental way
  • its also known as ‘inspect-and-adapt’ approach with ‘analysis-paralysis’ way.

Agile Software Development is a group of software development method including most used popular SCRUM with the tool ScrumWorks Pro.

The main concept behind it:

Agile methods break tasks into small increments with minimal planning and do not directly involve long-term planning. Iterations are short time frames (timeboxes) that typically last from one to four weeks. Each iteration involves a cross functional team working in all functions: planning, requirements analysis, design, coding, unit testing, and acceptance testing. At the end of the iteration a working product is demonstrated to stakeholders. This minimizes overall risk and allows the project to adapt to changes quickly. An iteration might not add enough functionality to warrant a market release, but the goal is to have an available release (with minimal bugs) at the end of each iteration.  Multiple iterations might be required to release a product or new features.

Team size is typically small (5-9 people) to simplify team communication and team collaboration.No matter what development disciplines are required, each agile team will contain a customer representative. This person is appointed by stakeholders to act on their behalf

And the meeting for these teams, sometimes referred as daily stand-ups or daily scrum meetings, are held in at the same place and same time every day and should last no more than 15 minutes. Standing up usually enforces that rule.”

There is a common debate between old Waterfall and Agile method. Now the question is why agile and why not waterfall?

Waterfall method tell us for a sequential workflow. like making requirements, design, coding, testing and so on, that is one by one.
But the problem here is : at the end of a project, a team might have built the software it was asked to build, but, in the time it took to create, business realities have changed so dramatically that the product is irrelevant. In that scenario, a company has spent time and money to create software that no one wants. Couldn’t it have been possible to ensure the end product would still be relevant before it was actually finished?

Yes, it can be done by agile way, an iterative, incremental system where a group of teams finish their assigned work by their team meeting, collaborating with client within a short time frame and finally done with a successful software which make sense.

Well-known agile software development methods include:

Today, up to this, happy agiling, be right back with SCRUM soon 🙂