As part of the Agile Data Engineering we define the data layers so the AgileBI team can have clarity about what we do to data and where.  Data with an SLA, data with no SLA [[what happens if everything got turned off, who would care]] [[delvieres a repeatable...

[[data quality]] [[dont boil the ocean and validate all the data]] [[check it is correct but also is it fit for prupose]] [[need to understand what the purpose is, use the "who will do what" action call]]

[[how to keep finding going in an project org]] [[not the agile teams problem]] [[projetc pipeline option, and rolling one project ahead]] [[fund the team and business prioritisation option]] [[business unit funds the work outside of a project strucuture, direct...

One of the focuses of AgileBI should be removing latency from the entire delivery process. We do this by identifying patterns we can use to reduce the effort and risk in doing repeatable tasks.  And then when we have these patterns identified, we should automate...

We have seen a lot of new business intelligence vendors and tools enter the market over the last couple of years. [[introduction of apps concept]] [[encapsulation of data and layouts in one thing]] [[likened t the old dashboards, but can also finally deliver self...

There is a concept of being "ad-how" vs "doing agile" vs "being agile". [[adhoc]] [[table of points]] [[adhoc, team meeting, no stand ups, no documentation, milestone projetc plan, no done done]] [[doing, daily stand ups, no demo day, maybe planning, no retrospective,...

Introduction to the feature owner role The role of Product Owner is a hard role in a AgileBI project.  The product owner has to provide a number of capabilities:  [[Engage with the stakeholders to provide ]]  [[SME]]  [[data]]  [[business...