This content originally appeared in TDWI. TDWI members can see the original here.
With so many teams “going agile,” it’s important for your BI team to keep a few things in mind that will help your agile transformation go more smoothly. This series, “10 Mistakes to Avoid In an Agile BI Transformation”, will show you how to prevent the most common pitfalls I’ve encountered in my experience as an Agile Coach.
Business intelligence (BI) teams are increasingly embracing agile approaches. The 2017 TDWI BI/DW Teams, Skills, and Budgets Report reflected that 79 percent of teams are now using agile for their development work, a significant increase from the 33 percent a similar report indicated in 2016. With so many teams “going agile,” it’s important for BI teams to keep a few things in mind that will help your agile transformation go more smoothly.
In this upcoming series of blog posts, I will the adress the primary problems I’ve seen in BI agile transformations. Fortunately, agile approaches provide solutions that prevent you from making these mistakes.
In fact, many of these mistakes come from teams only adapting part of the agile mindset because some agile practices appear counterintuitive based on our previous experience. Every habit we have, good or bad, serves a purpose. Some habits were created because they served a good purpose at the time, but now the world demands something different of us. We need to adapt our habits to a new way of working.
According to the 2016 TDWI BI Benchmark Report, “Once again, the use of agile development methodologies reached new heights of popularity in this survey, rising from 29 percent in 2015 to 33 percent [in 2016].”