The Agile Manifesto was first established by a group of 17 developers in February 2001 during a meeting on lightweight software development methods that took place in Utah. The Agile manifesto consists of 12 principles that deals with the communication, collaboration, team work, open mindedness for software upgrades and work efficacy. Agile methodology runs by a set of principles and they are as follows:
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
- Deliver working software frequently, from a couple of weeks to a couple of months, with preference to the shorter timescale.
- Business people and developers must work together daily throughout the project.
- Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
- The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
- Working software is the primary measure of progress.
- Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
- Continuous attention to technical excellence and good design enhances agility.
- Simplicity — the art of maximizing the amount of work not done — is essential.
- The best architectures, requirements, and designs emerge from self-organizing teams.
- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.
Scrum methodology is a fork of the Agile manifesto and functions under the principles of Agile umbrella. Most development companies around the world and the developing teams opt to Scrum due to it’s efficient working principles and flexibility in making changes. It introduced the most famous empirical process control approach rather than working based on predictions and forecasts.
- Operates under three roles : The Product owner, team of developers & the Scrum master.
- Tasks are detailed after an in-depth team discussion with the product owner and the group of developers. The scrum master is always present during all the discussions.
- Runs by the sprint schedules by which each task completed during a sprint is submitted for review by the product owner.
- A Sprint usually takes about 1 ~ 3 weeks as per the project complication.
- Discussed tasks are grouped into a list as a backlog and submitted for development during the launch of the first sprint.
- Completed tasks are submitted for review by the product owner at the end of a sprint.
- Flexibility to make changes after each sprint based on the finished work.
- Project expense is substantially reduced since the tasks are directed based on the empirical control approach.
- The ability to accept changes on the course of development during each schedule of a new sprint.
- Backlog refining process which allows all the team members and the product owner to share their thoughts and recommendations for a more efficient workflow.
- Sprint retrospective meeting is held which allows the whole team, the scrum master and the product owner to discuss about the previous issues they had faced in the previous sprints and move ahead in a more productive way.
- Scrum master holds regular meetings with the development team on the advice of the product owner and discusses all kinds of changes needed for a project.
- New features and upgradations are gladly done on the course of the sprint completions with open-mindedness.
Waterfall is a simple linear approach to any incoming project and is one of the famous forks of Agile Manifesto. This is a simple and effective methodology used for less complicated projects which doesn’t require too many upgradations or feature upgrades after the initial launch. This method of approach has been the popular version of Systems Development Life Cycle (SDLC) followed by the software experts around the world for manufacturing, construction and many other projects whose final results are always pre-determined. Every project undergoes a certain evaluation and is considered to be taken with a Waterfall approach that falls linear with every other steps that follows each other.
- Suitable for construction, manufacturing and factories.
- Linear approach methodology that goes step by step.
- Any completed step is usually complicated to be re-done and incurs huge cost.
- All projects are clearly discussed and the results are always pre-determined.
- Changes can’t be implemented during the course of the development.
- Competitive analysis and requisites are discussed with the stake holders before project initiative.
- Gantt Chart planning which involves a bar chart with start and stop of a task schedule.
- Eight effective pre-planned stages until project launch.