by Shane Gibson | 3.1 - AgileBI Team, Backlogged
[[moved form one project to new one]] [[started at the place i left off]] [[hadnt taken new team on the journey]] [[new team also picked up some things faster and other things slower than last team]] [[art is reading people]]
by Shane Gibson | 3.1 - AgileBI Team, Backlogged
[[teams go at different paces]] [[have to learn as they go]] [[may have had bad experience with agile]] [[need to fail to fix]]
by Shane Gibson | Backlogged, Process
As a BI practioner I want to understand when I can start backlog grooming So that I don’t start it to early and cause un-required rework, or leave it to late and not be ready to start the sprints [[curate the known sotries]] [[2 hours session in week 2 and week...
by Shane Gibson | 3.1 - AgileBI Team, Backlogged
We get taught during our life that 1 + 1 can equal three when we leverage the power of a team. This is often true and in AgileBI … [[scrum teams deliver more]] [[velocity]] But [[adding people mod sprint makes every thign slower]] So at the beginning 6 + 2 will...
by Shane Gibson | 6.1.1 - Vision and Scope, Backlogged
Vision and Scope As a BI Practitioner I want to understand how to set expectations and limit the scope of a set of iterations So that I have some boundaries which means we will not have endless iterations or additions to requirements, without agreeing these...
by Shane Gibson | 6.1.1 - Vision and Scope, Backlogged
[[why you need to do it]] [[stakeholder onion]] [[surprise stakeholders and their new requirements]] [[identifying who should be keep informed]]
