How To: Manage PowerView Project

How To: Manage PowerView Project

Rate This
  • Comments 1

PowerView Development Process

  • Understand business requirement or change request
  • Design high level data model
  • Determine and verify according data sources and their properties
  • Investigate each data source, including data relationships, data cleanliness, data granularity and refresh schedule
  • Co-operation with external data source team owners on existing issues and/or questions
  • Create the data model in PowerPivot (low level data model)
  • Query design, coding and testing (SQL, MDX, DAX)
  • PowerPivot model configuration
  • PowerView UX design
  • Styles
  • Interactions
  • Slicers
  • Filters
  • Graphics
  • Data verification and interaction testing
  • Review and feedback
  • Next cycle...

 

PowerView Project Must Know

  • PowerView is 100% self-services BI. Typically, users prefer developing their own story. So please anticipate additional change requests from users as opposed to traditional reporting.
  • PowerView is more complicated than the traditional reporting because it can consume and integrate heterogeneous data sources along with rich UI interaction. Usually with multiple related charts sharing uniform slicers within a single screen.
  • Some change requests might cause a complete change to the entire data model although there may be minimal UX modification.
  • Current version of PowerView (Excel 2013 and SharePoint 2013) still has some limitations and defects, it cannot replace SSRS or Excel PivotTable completely.
  • The best scenario of applying PowerView is through user's emphasis on the diagram interaction or public representation.

 

Bob Zhao (http://www.linkedin.com/pub/bob-zhao/13/a66/53a/)

David Lin (http://www.linkedin.com/pub/david-lin/14/611/b8b/)

Leave a Comment
  • Please add 5 and 1 and type the answer here:
  • Post
Page 1 of 1 (1 items)