Don’t start your agile transformation with a new APM software tool. Lynn Winterboer gives reasons why in this article “10 Mistakes to Avoid in an Agile BI Transformation.”
Acceptance Criteria for Data-Focused User Stories: Part 3 In parts 1 and 2 of this blog series, I explained what acceptance criteria are/how they benefit data teams and what happens when the product owner does not accept a story. Now, I am going to walk you through the creation of acceptance criteria. Creating acceptance criteria is started and led by the product owner, but it involves the entire team to ensure complete understanding and clear […]
There are several ways to handle a story that is not accepted by the product owner, and the correct response must be decided on a case-by-case basis. It is important that the data team stays focused on creating value, and that requires regular reviews and adaptations.
Acceptance criteria applies to individual stories. They come from the product owner and are used by the stakeholders to assess whether or not the purpose of a story has been accomplished.
New product owners who lean on classes of service find their prioritization work goes more smoothly, and they can instead focus their attention on the proper definition of user stories for creating business value. Read more
Working in Agile Data Warehousing (DW) and Business Intelligence (BI) over many years, I’ve worked with a lot of teams and coaches. Read more
A consideration for agile teams that don’t yet have push-button builds, continuous integration, and automated testing. Read more
Why some agile DW/BI teams should consider adopting Kanban as their agile framework. Read more
Three hallmarks of a good Agile BI coach that you should consider when looking for a coach. Read more
This TDWI FlashPoint article, Why Build Architecturally Complete BI/DW User Stories?, was selected for TDWI’s annual “Best of TDWI” digital magazine. Read more