Agile Methods for BI Delivering Higher ROI, Earlier Results, User Adoption

Transcription

1 Agile Methods for BI Delivering Higher ROI, Earlier Results, User Adoption Michael Taylor Practice Area Lead Business Intelligence With input from Gareth Cook Agile Thought Leader and Project Mgr.

2 Agenda Who are Tridant? What has led us towards Agile Essence of Agile and Key Techniques for BI Agile BI lessons from the field Tools for Automation Agile Case Studies Q&A at our booth 2

3 Who are Tridant? Established in 2007 as a Business Analytics Implementer 58 employees, 51 consultants nationally Facilities in Sydney, Melbourne, Adelaide, Perth Numerous awards for Project Success Breadth of competencies: - Business Intelligence - Financial Performance Management - Information Management - Project Management - Predictive Analytics - Helpdesk and Support Services

4 What has led us towards Agile Stating our requirements up-front can be difficult Quick wins, frequent deliverables; keep people engaged Workshops alone not always engaging Agile Iterative Prototyping aids visualisation We re becoming allergic to excessive documentation, say it on a card instead Embracing change Simplicity 80% matters, 20% is low bang for buck 4

5 Epic-level requirements Backlog Waterfall ANALYSE DESIGN BUILD TEST Agile ITERATION 0 ITERATION 1 ITERATION 2 ITERATION 3 Deploy Deploy Deploy Analyse Analyse Analyse Design/Build/Test Design/Build/Test Design/Build/Test 5

6 6 Agile Techniques

7 Gathering Requirements in Agile Epic An epic is a large user story that needs to be broken down into smaller stories or a collection of user stories that can be grouped together. Epic Perform Mortgage Book Analysis User Story Describes the basic need of a user and how it might be satisfied. I want to see details on the Mortgage Holder(s) Include Loan $ paid vs. owing Graph of top/bottom 10 User Stories 7

8 Card Name AS A : Who the user is, what is their role, how they are related to the project? I WANT : What is the requirement? SO THAT: How is this requirement going to be used or what will it enable?

9 Late Returns of Books AS A: Book Hirer User suggesting the solution I WANT: The Library to stay open until 9pm SO THAT: I can return my books after I finish work late This statement provides greater clarity on the reason behind the requirement, and potential alternate solutions (e.g. after hrs. return slot)

10 Mortgage Default Report AS A: Collections Officer I WANT: To see a full list of all customers that have mortgages SO THAT: I can identify those who are behind by 3 or more repayments The So That is the critical statement

11 FST Conference Objective #4 AS A: Conference Attendee I WANT: Friday afternoon to go quickly SO THAT: We can go to drinks already! The So That is the critical statement

12 TIME CRITICALITY Low High DELIVERY RISK High Low Agile Snapshot Prioritising Requirements Note: the axis measures swap from one Priority Map to another First to implement Priority 2 Priority 1 Priority 3 Priority 2 12 Low High High Low IMPORTANCE Lead times and dependencies need to be considered SOLUTION COMPLEXITY

13 The Agile Card wall or Kanban wall 13

14 Lessons Learned from the Field 14

15 Agile Estimation Techniques Fibonacci sequence 1,2,3,5,8, 13,21 Allows for more contingency the larger the work. Too Large for a single Iteration and needs to be broken down (EPICS) T-Shirt Sizes Agile Heart Beat - Best guess for your first iteration - Complete 2-3 iterations, then calculate average progress to develop your Heart Beat or Velocity the number of story points per iteration or sprint. 15 S M L XL A combination can be used in an iteration as long as it does not equal or is greater than 8, or > Large.

16 Team structure is vitally important Working closely with the business/customer allows for a better end-product Get the right people on the bus Extended Team Core Team 17

17 You can mix techniques Analyse Design Build Scheduled Time Test Backlog Build (Generic Steps for all Stories) USER STORY USER STORY In progress In review Done Testing 18

18 The Daily Stand-up Meeting The secret sauce of Agile Should be run by an experienced Agile Practitioner Each and every person answers three questions: What did I achieve yesterday? What am I going to achieve today? What will stop me from achieving my goals? No more than 1/2 an hour Everyone must participate to be effective Held standing up so that they are kept short and everyone is visible An effective method of doing a stand-up is in front of a card wall. 19

19 Leverage Tools for automation Trello for online multi-user Agile tracking Come to our Booth for a demo 20

20 Leverage Tools for automation Balsamiq for rapid Requirement Gathering mockups Come to our Booth for a demo 21

21 Smart People - Win an i m Watch Come have a chat at our booth & enter our competition to win the latest in smartwatch technology an i m Watch Smart Watch Smart People 22

22 Breaking News! At our booth On display, IBM s new Business Analytics Visualisation engine currently in the labs for future release! To learn more contact Michael.Taylor@tridant.com.au 23