pdfcoffee.com-systems…
)
Integration Technology IT team size
IT team locations
IT team skills
Customer team
• Software subject to legal audit or requires formal requirements • Software must integrate or interface with many other systems • Need to use or integrate new or unproven technologies
• Technology is obsolete and needs to be updated or replaced Team characteristics • Many IT team members
• Multiple IT teams to coordinate • Multiple locations • Multiple time zones • Multiple native languages and cultures
• Multiple organizations (e.g., internal team working with a vendor) • Many skill sets with high levels of team member specialization
• Team needs training on new or existing technologies
• Team needs training on software development process
• Team needs better cohesiveness and communication • Many subject matter experts (SMEs), sponsors, and/or other stakeholders
• Multiple areas of expertise • Multiple locations, time zones, languages, and cultures • Customers face diverse laws, regulations, and market practices • Customers value formal project planning and management
This can be seen more plainly in Table 5-3. Here, we list these same categories and characteristics, but we also express the values of characteristics that define projects that best fit the “Agile Home Ground” versus the “Hybrid Home Ground.”
Fieure 5-6 shows another portrayal of the hybrid approach. While it is generally similar to Lig= =6 illustrates that idea of a “less hybrid” or, if you will, “more agile” version of the hybrid approach. That is, by changing the proportion of requirements occurring prior to and during software construction, we can tune our approach to each specific project_ Comparing figures 5-5 and 5-6 in the latter we may decide that there are a few complex and risky features that need up-front requirements analysis using BRUF. However, remaining features may be less risky and less clear, such that the team would be better off using emergent requirements for them.