Book Image

Managing Data Science

By : Kirill Dubovikov
Book Image

Managing Data Science

By: Kirill Dubovikov

Overview of this book

Data science and machine learning can transform any organization and unlock new opportunities. However, employing the right management strategies is crucial to guide the solution from prototype to production. Traditional approaches often fail as they don't entirely meet the conditions and requirements necessary for current data science projects. In this book, you'll explore the right approach to data science project management, along with useful tips and best practices to guide you along the way. After understanding the practical applications of data science and artificial intelligence, you'll see how to incorporate them into your solutions. Next, you will go through the data science project life cycle, explore the common pitfalls encountered at each step, and learn how to avoid them. Any data science project requires a skilled team, and this book will offer the right advice for hiring and growing a data science team for your organization. Later, you'll be shown how to efficiently manage and improve your data science projects through the use of DevOps and ModelOps. By the end of this book, you will be well versed with various data science solutions and have gained practical insights into tackling the different challenges that you'll encounter on a daily basis.
Table of Contents (18 chapters)
Free Chapter
1
Section 1: What is Data Science?
5
Section 2: Building and Sustaining a Team
9
Section 3: Managing Various Data Science Projects
14
Section 4: Creating a Development Infrastructure

Dealing with prototypes and MVP projects

If you are dealing with data science, I bet you will find yourself doing a lot of prototyping. Prototypes often have very strict time and money limitations. The first lesson of prototyping is to approach every prototype as an MVP. The key idea behind MVP is to have just enough core features to show a working solution. Bells and whistles can be implemented later, as long as you are able to demonstrate the main idea behind your prototype.

Focusing on core features does not mean that your prototype should not have a pretty UI or stunning data visualizations. If those are the main strengths of your future product, by no means include them. To identify the core features of your product, you should think in terms of markets and processes.

Ask yourself the following questions to check whether a particular feature should be included in the MVP...