Dishing up SharePoint BI
•
1 like•504 views
Planning on implementation Business Intelligence in SharePoint? What are your options for technologies and how should you plan your deployment
Recommended
Recommended
More Related Content
Similar to Dishing up SharePoint BI
Similar to Dishing up SharePoint BI (20)
Recently uploaded
Recently uploaded (20)
Dishing up SharePoint BI
- 3. Agenda • What is BI in SharePoint • The main course – TV Dinners • Making it sweet – Approach – Critical success factors
- 4. Starters – BI Solutions Online Visual Navigation Large Datasets Pivot PowerPivot Power Viewer Visio Services Mapping KPI / Status Indicator PerformancePoint SharePoint List SQL Reporting Services Chart Web Part Access Services Excel Services Printing or Exporting Small Datasets
- 6. Data Sauces and Sides • http://msftdbprodsamples.codeplex.com/releases/view/5592 6 • http://www.microsoft.com/silverlight/pivotviewer/ • http://powerpivotsdr.codeplex.com/ • http://blogs.msdn.com/b/sqlrsteamblog/archive/2011/11/17/ what-s-new-in-power-view.aspx
- 7. Know your customer! • Understand business drivers and aspirations • Business Objectives for BI • Establishing relative importance • Build IT and Business Relationships -> Partnership
- 8. What’s in the Pantry? • Meat and Veg – ERP – CRM – User Data – Local and Foreign produce • Sauces and Spices – Business Rules – Known Limitations – Complexities – Data Quality
- 9. Creating the BI Menu Planning and Prioritisation Chop sticks and knife and fork Value Complexity
- 10. Lets cook • Who’s the paying customer? • Pots or pans, how many? • Arrange the meal before you cook it • Use a recipe • They don’t want what they ate in school
- 11. Before you serve • Iterative approach is tried and true • Fail fast (if it’s fast you didn’t fail!) • Serve when it’s good enough, don’t over cook • Minimise risk
- 12. Taking it to the table • Making it welcoming • Meals served on site not takeaway • Laying out meal • Who ordered which meal • Serving it to the customer • Follow up
- 13. Chef Ramsey’s Advice Don’t cook stuff you Only cook what don’t have the f***g Don’t f**k it up b customers want boy ingredients for Don’t let customers cook in Don’t give the kitchen someone who uses only forks, soup Start simple so you don’t loose Don’t cook stuff you your customer don’t have the f***g experience to do well
- 14. The SharePint Diner Pantry Kitchen Diner Meal Market • Data Sources • Data • Bi • SharePoint Research Warehouse 2010 Ent Components • Excel
- 15. What is WhereScape RED? • Integrated Agile DW development environment • Built in leading practice DW development methodology • Promotes rapid prototype-iterate and deploy cycles • Speed up development productivity - generates data warehouse objects and code • Management & maintenance framework
- 16. Gold Sponsors Silver Sponsors Technology Bronze Sponsors Sponsor Media Sponsors
- 17. The following are example slides. These can all be removed once you have referenced them.
Editor's Notes
- Opening slide please include
- We have fish – chocolate fish
- Shows SharePoint 2010 BI solutions based on Static/Dynamic as they relate to dataset size.The tools can also be viewed by self-service, community driven reporting and business organisationAl – you should make these pies
- Everyone loves demonstrations if you’re able to show one!If not just delete or hide this slide in your presentation.
- Thanks Alan, great. The only problem with TV dinners is they don’t teach you how to cook. What do you say we show them?
- Not requirements. What are their challenges, objectives and aspirationsUnderstand what the business are hoping that BI will do for them to meet their dreams, aspirations etc.Get a feeling for the relative importance of the business drivers etc, this will help later when we look at data sourcesPartnership most important. Shared responsibility, shared ownership, easy flow of information, constructive engagementIf the going gets tough partnership will save youIf the going is easy then it will carry you faster
- What data have we gotWhat are the key limitations of these sources now, DQ, security, complexity etcWe can only cook what we’ve got ingredients for, regardless of what the business want. Be Honest.End of this process we have a Shared Understanding of what is possible
- We know what we want and what we haveAgree what can be done -> prioritiseSolid conceptual framework based on progress so far.At the end of this we should know “What, When, How much”Don’t over document, looking for conceptual framework and roadmap, high level plan + agreementThings will change, don’t waste time on detailIf you get to this point and the business aren’t engaged, forget it, save your time and their money.We are putting together the market research to what we can makeBusiness users we request complicated meals, but these have significant risk in data quality, incomplete problem we are answeringDeserts that matches the mainsAvoid confusion – people can’t recognise what they are eating
- Get a business sponsor! They will help maintain focus, commit resources and make key decisions.Decide where you’re going to put the dataData WarehouseMart or MartsHub and Spoke, MonolithicDecide on a modelling technique, Star, 3NF, Data Vault. Probably Star, but just decideTake the time to plan, use tried and true techniques, don’t re-invent the wheelRemember recipes are guidelines not instructions, experimenting to your taste is OKArranging the information in a clear way with meaningful descriptions is keyPeople want to know what they’re eatingThey appreciate effort in presentation
- Iterative approach with feedback loop between IT and business superior to SDLCYou know if you’re on the right track fasterYour risk is minimisedBusiness engaged and on sideTime to value important, get it done and into production as soon as possible.
- If you have a partnership you won’t f**k it upFailing early isn’t a f**k upIf you seriously f**k it up you’re probably f**ked
- Significant point highlighted in a box, plus increased font size and bold.