Done Done
Articles that are as completed as I will ever get them.
No Results Found
The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.
Done
Articles that are as completed but need to be reviewed at some stage.
No Results Found
The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.
Underway
Articles that I am currently working on.
No Results Found
The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.
Refined
Articles that have bullet points added, which effectively are my acceptance criteria of the content.
Initiation Phase
[[layer architecture]] [[design standards]] [[backlog groom epics]] [[create team space]] [[pick agile boards, local or software if remorse team]] [[pick Comms tools, yammer, slack etc]]
Agile Myths
As a BI Manager
I want to understand what the common Agile Myths are
So that I know how to identify them when they are referenced
Information Products
As a Developer
I want to understand how to capture content reqiurements quickly
So that I can estimate their size and obtain a priority for the order to deliver
FAQs as documentation
Add them in the vision statement for the info product -Who are our top 10 customers Add them in the wire frames Add them in the business rules - how are the top 10 identified -- rank by total revenue Add them in the doco maps -Where can I find...
Test Driven Development
[[test first]] [[test last]] [[must test, can't handball]]
Business Rules
As a Developer I want to understand how to document business rules So that we can increase the speed of delivery Another of the more difficult capabilities in data warehousing is the definition and...
Data Layer Patterns
Over the last 20 years a number of patterns have emerged for dealing with the data layers in a centralised data repository. These have typically been attributed to the person who has championed this model, people such as Bill Inmon and Ralph Kimball. These patterns...
Agile Overview
As a BI Practioner
I want to understand what Agile is all about
So that I can understand if I want to adopt it
Musings, Ramblings and Structure
As a Reader of this site
I want to understand what it is about
So that I know whether I should keep reading
Backlogged
Articles that have a title and not much else.
6 + 2 = 4
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...
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 changes upfront [[...
Identifying the Stakeholder
[[why you need to do it]] [[stakeholder onion]] [[surprise stakeholders and their new requirements]] [[identifying who should be keep informed]]
Demo Day
Demo day is where the team prove it has delivered the user stories as "done done" at the end of the sprint, typically in a one hour session. In theory the Product Owner should run through the finished deliverables to make sure they work. Demo days are always a...
Multiple Scrum teams
[[scrum of scrubs nope]] [[ two stand ups , inner and outer rings]] [[archutect sits on all planning sessions]]
This guy vs That Guy
Agile Discipline – Planning
There is a myth that Agile is all about being adhoc and that there is no planning upfront involved. It's not true. In fact when undertaking a AgileBI approach the team will spend far more time in planning sessions than in a typical waterfall project. What is different...
Agile Discipline – Documentation
There is a myth that Agile doesn't deliver documentation. It's not true. We always do the documentation that is required during a BI project, such as design and as built documents, what differs is the way we create them and when. A waterfall project is all about...
Developer Stories
[[developer stories vs user stories]] [[task oreinted]] [[team have to talk through the process/steps they wil use to deliver the user story which is highly valuable in itself]] [[less than a days effort]] [[allows multiple developers to work on user story...