Development Pattern III
nEvolutionary
Development Pattern
–Objective: Flexibility on new product feature
requirements
–Related to: Component Architecture, Evolutionary
Prototyping, Feature Teams
–Description: Create initial baseline product. Schedule
multiple “mini-releases” using some other
development cycle (Waterfall). Mix and match
mini-releases to create desired product.
–Advantages:
nQuick responses to
market changes possible
nRelease schedule is
flexible
nAbility to measure
progress
–Drawbacks:
nHeavy dependencies
bog down cycle
nDifficult to verify
or validate requirements