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.
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
Acceptance Criteria for Data-Focused User Stories: Part 2
In the first part of this blog series, I defined what acceptance criteria are and why data teams need them. Now, I am going to address a possible outcome related to acceptance criteria when it comes to a user story:
What happens when the product owner does not accept a story?
Acceptance Criteria for Data Focused User Stories: Part 1
Acceptance criteria are a game-changing tool for data teams. They directly lead to more efficient team members who understand the impact their work has on the organization. Unfortunately, acceptance criteria are not always used or implemented well. It is important to know what they are (and what they aren’t) in order to get the best results.
The Benefits Acceptance Criteria Have on Your Team
Reprinted with permission from Media 1105, Inc. Originally published September 12, 2017 – TDWI Flashpoint Article
Problem: One of the biggest challenges for agile data teams is embracing test automation as a technical enabler for agility.
Fellow data professionals often ask me for recommendations for test automation tools, thinking that the implementation of a tool will make their process easier. My advice is to defer focus on a tool until the team can consistently define
Originally published by the Agile Alliance. By Chris Murman, Mary Striby Chang, and Lynn Winterboer In any given moment, we are faced with around 11 million pieces of information. Of those bits of info, the brain can only process 40 at a time. If that’s the case, what do we do with the remaining 10,999,960 pieces? According to Timothy Wilson’s book, Strangers to Ourselves: Discovering the Adaptive Unconscious, the
Why Aren’t All Data Teams Automating Their Tests?
If test automation is so important, why aren’t teams doing it already? In my past life, I was a developer and I learned quickly the value of testing our work. I moved out of development and into project management and business analysis then found my true calling in data warehousing and business intelligence as a consultant.
Reprinted with permission from Media 1105, Inc. Originally published May 4, 2017 – TDWI Flashpoint Article Agile business intelligence (BI) teams typically designate one person as the product owner (PO) whose role entails: (1) defining and prioritizing the user stories (business needs) to be delivered by the BI team; (2) being available to the team daily to answer questions and resolve issues; and (3) reviewing and then accepting or rejecting the finished
Which Presentations I’m Planning on Attending at Agile 2017
Agile2017 is such an awesome conference. With 274 sessions to choose from, I have to focus on what I’m going do and see. This year, I’ll be focusing on Audacious Salons, Product Ownership, Technical Enablers and some wonderful other options! I attend the annual Agile Alliance conference each year. To prepare, I
This year, Mile High Agile expanded to two days, and I had the honor of co-chairing it with the AMAZING Colleen Johnson. I will forever be grateful to Colleen and the Agile Denver Board of Directors for inviting me to bring a “new” voice to the event, regardless of my lack of prior conference-organizing experience.
BEHIND THE SCENES — Scaling MHA