The challenge with "agility" is that it isn't a tangible concept. There isn't a magic button in your company to enhance agility. The most concrete manifestation of agility for business stakeholders is the regular delivery of new or updated functionality in your BI/DWH system. If a new requirement is delivered within two to four weeks, it is perceived as agility.
To enable frequent deliveries, consider the benefits of short iterations. If iteration lengths are four to six weeks, it's impossible to deliver more frequently. However, with one-week iterations, you can produce potentially shippable data warehouse increments weekly. Short iterations are made possible through automation, which can be applied to standardized steps in your development process. This creates a paradox: even though agility is often linked to freedom and flexibility, heavy standardization is a key enabler.
Downtown-Patterns outlines areas for standardization using design patterns and consistent development standards. The first stop is "Data Layer Patterns," which explores various architecture sizes for BI/DWH systems. Other stops address common BI design patterns, such as data modeling patterns, naming conventions, and even data product patterns like data visualization best practices proposed by the International Business Communication Standards.