Explore agile development practices
Traditional software development practices involve:
- Determining a problem.
- Analyzing the requirements.
- Building and testing the required code.
- The delivery outcome to users.
Usually, all refer to as a waterfall approach.
The waterfall model follows a sequential order. A project development team only moves to the next development phase or testing if the previous step is completed successfully.
It's what an engineer would do when building a bridge or a building. So, it might seem appropriate for software projects as well.
However, the waterfall methodology has some drawbacks. One relates to the customer requirements.
For example, It doesn't matter if the customer requirements are defined accurately at the start of a project.
Usually, the project takes a long time, and the outcome may no longer match the customer's needs.
There's a real challenge with gathering customer requirements in the first place.
Taking a long time to deliver something would often be different from what the customer needs, even if you built exactly what the customer asked.
Customers often don't know what they want until they see it or can't explain what they need.
By comparison, Agile methodology constantly emphasizes adaptive planning and early delivery with continual improvement.
Rather than restricting development to rigid specifications, it encourages rapid and flexible responses to changes as they occur.
In 2001, highly regarded developers published a manifesto for Agile software development.
They said that:
- Development needs to favor individuals and interactions over processes and tools.
- Working software over comprehensive documentation.
- Customer collaboration over contract negotiation.
- Respond to changes over following a plan.
Agile software development methods are based on releases and iterations:
- One release might consist of several iterations.
- Each iteration is like a small independent project.
- After being estimated and prioritization:
- Features, bug fixes, enhancements, and refactoring width are assigned to a release.
- And then assigned again to a specific iteration within the release, generally on a priority basis.
- At the end of each iteration, there should be tested working code.
- In each iteration, the team must focus on the outcomes of the previous iteration and learn from them.
Having teams focused on shorter-term outcomes is that teams are also less likely to waste time over-engineering features. Or allowing unnecessary scope creep to occur.
Agile software development helps teams keep focused on business outcomes.
Comparison of the waterfall and agile methodologies
|Divided into distinct phases.||Separates the project development lifecycle into sprints.|
|It can be rigid.||Known for flexibility.|
|All project development phases, such as design, development, and test, are completed once.||It follows an iterative development approach so that each phase may appear more than once.|
|Define requirements at the start of the project with little change expected.||Requirements are expected to change and evolve.|
|Focus on completing the project.||Focus on meeting customers' demands.|
Need help? See our troubleshooting guide or provide specific feedback by reporting an issue.