The document outlines the rules and characteristics of a DevOps team at NetApp, emphasizing that such a team should consist of 3 to 8 members and led by a designated team lead. It describes the DevOps approach as one that applies agile methodologies, focuses on continuous product enhancement, and encourages collective ownership among team members. The document also highlights the importance of learning from failures and the capability of DevOps teams to independently release product updates.

1. 10
A DevOps team owns
one or more products.
A DevOps team is responsible
for the development, QA, and
operations of the products
they own.
1
| WWW.NETAPPIT.COM
Does your enterprise IT organization practice
DevOps without a common team approach?
RULES For
Forming A
DevOps Team
To create a standardized way for development and operations teams to
work together at NetApp, the IT team differentiates a DevOps team from a
regular development team based on these 10 rules. Learn more in our latest
whitepaper, "DevOps the NetApp Way."
2
A DevOps team should
not be smaller than three
people and not larger
than eight people.
A DevOps team has one
assigned team lead, who
leads and contributes to
the team.3
4
A DevOps team's size
and scope can be
changed over time.
5
A DevOps team applies
agile methodologies to
continuously enhance
the products they own.6
© 2020 NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consent
of NetApp, Inc. Specications are subject to change without notice. NetApp, the NetApp logo OnCommand, and ONTAP
are trademarks or registered trademarks of NetApp, Inc. the United States and/or other countries. All other brands or
products are trademarks or registered trademarks of their respective holders and should be treated as such. A current
list of NetApp trademarks is available on the web.
DevOps is a journey, and these rules apply to where we are
in our journey today. As we further mature, we will continue
to evolve these rules.
A DevOps team actively observes
their products to assess and
improve their operational health.7
A DevOps team embraces
failures as opportunities
to learn and improve.
8
A DevOps team can release a
new version of their product
independently and at any
time.9
A DevOps team maintains
collective ownership of
the products and shares
the knowledge with the
team.
10