Content (Blog): Blended Teams - Yes you CAN include your Data Scientists in your blended team

[jeblackburnvmw]

Summary of content

This document will focus on the process of taking an ML/DS model, making the code robust and maintainable, and preparing it to deploy to production. One of our key recommendations: the data scientist role is no different from the designer or product manager role. If we are prepared to argue for blended teams, cross-discipline pairing, short delivery cycles, and iterative development, then we should be proposing to embed data scientists into every project that needs them. We also argue for changes to the workflow around unit testing, TDD, and refactoring.

Summary of audiences

Delivery leads, sales, anchors, anyone involved in proposing staffing levels for projects and setting the terms of engagement on a project. These people should be ready to educate our clients about the advantages of embedding data science workflows right into projects early and often.

Level of content

Level of content as it pertains to the topic proposed. Delete those not applicable.

• 101: "Awareness / Exploration" (?)

Draft of Content

https://docs.google.com/document/d/1LjNmqLaruSz9cSyfMfkdfpH0jb78jZMMjUmZ9JWIWLc/edit?usp=sharing

Contributor Checklist

1. I have added a card to the GitHub Content Backlog and/or moved it to the proper column. See Content Prewriting and Ideation
2. If contributing via Google Docs: I have added a link to my document to this issue, and set the document's Share settings to "Anyone on the internet with this link can comment".
3. My content is drafted in accordance with existing style guides and best practices. See Drafting Content
4. The front matter (metadata) is filled out completely (e.g. description, topics, tags, author, etc - as appropriate for the content type). See Drafting Content
5. My content has been reviewed by my team for technical accuracy. See Editing Content
6. My content has beed reviewed and edited by a copy editor. See Editing Content
7. If applicable: My content has gone through a legal review (VMware Employees Only). See Editing Content
8. If applicable: I have tested my content locally and everything passes. See Testing Content
9. Optional: I have filled out the Social Media request form (optional) (VMware Employees Only). See Next Steps
10. If applicable: I have created an author page and opened a pull request to get it added. See Next Steps

Reviewer Checklist

• Review if the content is a good fit for the Tanzu Developer Center. See Content Prewriting and Ideation
• There this GitHub issue has been added to the content backlog project
• Ensure with the author that the content has been reviewed for technical accuracy.
• Ensure with the author that the content has been through copy editing.
• If applicable: Ensure with the author that the content has been through Legal review.
• Review fit with the Tanzu Developer Center Style Guide and the VMware Style Guide (VMware Employees Only).
• Ensure the front matter is filled out correctly and completely.
• If applicable: Review additions to custom_dict.txt.
• Ensure with the author they have reviewed the staging site for correctness. The reviewer should review this too.
• If applicable: Review any new Team pages.
• Optional: Ensure the author has provided copy for Social Media distribution.\
• If contributing via Google Docs: Send the staging link to the author to review. The reviewer should review this too. Get the final 👍 from the author to push the content public.