5.7 Summary

The section covered five alternative methodologies to SCRUM, all categorized as AGILE.







  • Ideal for JIT logistics

  • Easy to understand

  • Easy to monitor

  • Prevents overproduction

  • Demand problems: stable amount of output

  • An outage of one element can block the whole process flow

Extreme Programming

  • Strong on the side of technology

  • Continuous QA

  • Frequent feedbacks

  • Customer ownership

  • High customer involvement (on-site)

  • Documentation is weak, emphasis on verbal communication only


  • Family of methodologies to be determined by size and criticality

  • Emphasis on testing

  • Hard implementation if co-location is present

  • Need adjustment based on factors

  • No upward or downward compatibility (shift from one to an other is hard)

Dynamic Systems Method

  • Aligns with business goals

  • Understanding goals is easy

  • Emphasis on testing and quality

  • Requirements are easily manageable

  • Sets stakeholder expectations

  • Heavy documentation for the methodology

  • Heavy documentation needs for the project

  • Hard to implement and master

  • No detailed processes and view on the technology side

Driven Development

  • Multiple teams can work parallel

  • Scales to large projects

  • Individual code ownership, essential individuals

  • Model centric approach can't fit to maintain already given systems

  • No well definition of iterations