pdfcoffee.com-systems…
Id I S%
)
Figure 5-6 Requirements and construction in a hybrid project (less up-front requirements effort than in Figure 5-5)
For example, projects with a high number of highly complex features tend to work better with a hybrid approach. This is straightforward. But consider other key factors. For example, how interdependent are those features? How clear are they? How stable? As each of these factors increase, hybrid becomes mom appropriate. But why this is so may not be obvious.
We explain each of these issues in the following discussion. However, before diving into this complex detail, we introduce a tool for simplification: visualizing a project’s characteristics using a radar chart.
Table 5-3 Home Grounds Model of project characteristics for agile and hybrid project approaches
Project characteristic Agile Home Ground Hybrid Home Ground Functional requirements characteristics • Small number of new features • Many new features
Number
Complexity
I o et-dependence
• Focused on one function • Small budget • Simple features • Single project • Simple data schema
• Single version of requirements • Brand-new software application
• Enhancements to a modern, well-designed existing application
• User stories are independent • Start-up business
• New product, service, or Clarity function
Stn bility
Performance
• Responding to confusing, turbulent environment • Requirements changing rapidly Nonfunctional requirements • Small number of users
• Low transaction/data volume
• Focused on multiple functions
• Large budget • Complex features
• Multiple interacting projects • Complex data schema • Many requirements variations
• Enhancements to an existing, “legacy” application that is poorly-designed
• User stories must be built in a specific, logical order
• Current business and software well-understood (or can be)
• New requirements well understood (or can be)
• Requirements changing slowly
characteristics • Many users
• High transaction/data volume