“Why Build Architecturally Complete BI/DW User Stories?” Selected for “Best Of” Publication
Best of TDWI 2014
My TDWI FlashPoint article, Why Build Architecturally Complete BI/DW User Stories?, was selected for their annual Best of TDWI digital magazine, which published in mid-February, 2015.
The Best of annual digital magazine features their most influential articles, research summaries, and newsletters from the previous year, as well as TDWI industry expert forecasts for the future of all things data.
Why Build Architecturally Complete BI/DW User Stories?
If you choose to slice user stories by technical function or skill set, you will put your delivery of timely business value at risk.
Originally published April 3, 2014 in TDWI Flashpoint: Tips, Techniques & Critical Research in BI and DW.
Sometimes “by the book” guidance for agile teams doesn’t easily apply to data warehousing (DW) teams. For instance, slicing user stories can cause a conundrum when we face two options: (1) slice user stories by technical function/skill set or (2) slice stories into thinner, architecturally complete features that encompass all of the work necessary, from source to report, to meet the organization’s needs. If you choose to slice user stories by technical function or skill set, you will put your delivery of timely business value at risk. However, if you slice user stories into architecturally complete functionality, you keep your team focused on–and honor the agile commitment to–frequent and consistent business value. Continue Reading: Why Build Architecturally Complete BI User Stories?