\Relysis\Management\Hybrid Agile>

Hybrid Agile

I don’t think either agile or waterfall are the right approach if followed zealously as both have their shortfalls. Using a hybrid of both methodologies can help avoid some of their individual disadvantages.

2 main downsides of pure agile

1. Regular re-architecting. As each sprint is supposed to deliver the minimum possible to meet the business requirements (as more detail can be added in future sprints if necessary) then often whole sprints are consumed refactoring code to support functionality that everybody knew was coming.
2. Lack of documentation. The only artefacts from agile development are the “done” user stories, which means there is no central document specifying how the system should behave. Looking at old stories may be misleading if they over been superseded by later stories.

2 main downsides of pure waterfall

1. The system has to be designed entirely upfront requiring lengthy specification documents which business users often struggle to review. Requirements are more easily understood and agreed with a basic prototype to generate discussion and feedback before big architectural decisions are made.
2. Change is difficult. There is no room in the project plan to cope with change requests so every update has an impact on project delivery. And if you’ve outsourced your development that means they have you over a barrel when it comes to costs!

>HOME - Resources
>RESEARCH - Business Research - Competitor Analysis - Technology Reports
>ANALYSIS - Requirements - Modelling - Documentation
>MANAGEMENT - Scrum Master - Waterfall - Hybrid Agile
>ABOUT US - Contact Us - Privacy Policy - Terms of Use
Healthcare IT, ehealth, mhealth, digital health - research, analysis, management