Book Image

Data Democratization with Domo

By : Jeff Burtenshaw
Book Image

Data Democratization with Domo

By: Jeff Burtenshaw

Overview of this book

Domo is a power-packed business intelligence (BI) platform that empowers organizations to track, analyze, and activate data in record time at cloud scale and performance. Data Democratization with Domo begins with an overview of the Domo ecosystem. You’ll learn how to get data into the cloud with Domo data connectors and Workbench; profile datasets; use Magic ETL to transform data; work with in-memory data sculpting tools (Data Views and Beast Modes); create, edit, and link card visualizations; and create card drill paths using Domo Analyzer. Next, you’ll discover options to distribute content with real-time updates using Domo Embed and digital wallboards. As you advance, you’ll understand how to use alerts and webhooks to drive automated actions. You’ll also build and deploy a custom app to the Domo Appstore and find out how to code Python apps, use Jupyter Notebooks, and insert R custom models. Furthermore, you’ll learn how to use Auto ML to automatically evaluate dozens of models for the best fit using SageMaker and produce a predictive model as well as use Python and the Domo Command Line Interface tool to extend Domo. Finally, you’ll learn how to govern and secure the entire Domo platform. By the end of this book, you’ll have gained the skills you need to become a successful Domo master.
Table of Contents (26 chapters)
Section 1: Data Pipelines
Section 2: Presenting the Message
Section 3: Communicating to Win
Section 4: Extending
Section 5: Governing

Managing content backlog

The content backlog is the list of requests that are candidates to be implemented via the Sprint Planning process. We suggest a seven-stage process, as seen in Figure 19.24. The following is a description of each stage in the backlog process:

  • New: This is a list containing all the tasks from the Requests project, and is where each task is evaluated for what stage to be advanced to in the backlog.
  • Hold: This is a list containing all the tasks determined to be given on-hold status. A task can be put on hold at any point in the journey.
  • Backlog: This is a list containing all the tasks from the New list that have been determined to qualify for implementation at some point. This is the idea queue for potential development work. Items in the Backlog list can be placed in priority order from top to bottom by dragging and dropping a task card within the list.
  • Planned Sprint: This is a list enabling the next Sprint to be planned for convenience....