Agile methodologies like Scrum have several benefits over traditional waterfall methodologies, such as:
- Seeking progress within each iteration (or sprint) to review the accuracy of requirements and adjust course
- Implementing a simple structure and focus on the team's effectiveness as primary goals
- Encouraging breaking larger efforts into smaller, more manageable chunks
- Emphasizing team collaboration -- especially business and IT)
At its core, Agile assumes change is going to happen along the way — and provides the structure and process to respond to that change. Many of your projects likely revolve around complex business processes, integrations and user interfaces that will need to adjust and shift as more is discovered about the project.
- Luckily, tools like Oracle BPM make this very easy with Process Composer and a shared view of the process with BPMN models. Everyone can see the process (put it up on the screen!) and make the changes or improvements needed
- This also helps ensure the business doesn't need to wait six months to see progress or a working version
- This is generally good practice, but Scrum supports this approach within the methodology itself.
- This prevents you from getting too deep into the weeds of exception handling right away
- Often, “good enough” may allow you to ship the product or system sooner to reap benefits for the business and start the change process