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.
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! Read more
My response to the question, “What’s in your Definition of Ready? When does the ‘ready’ criteria apply? – i.e. ready by the end of Spring Planning (how?) or ready for the beginning of the Sprint?” Read more
If you are looking to hire product owners for your analytics team, and can’t find the perfect person on the market, I have an idea for you. Read more
An example of good acceptance criteria — beyond the obvious “the report should match the mockup and the data should be accurate.” Read more
When quality and testing is moved up front on a BI project, everyone enjoys a higher quality project even before implementing key automation tools. Read more