DXC's Technical Doctrine
DXC’s Technical Doctrine is a set of principles that enhance our technologists’ ability to drive strategy and vision and deliver results for our customers. The principles are the basis for best practices at DXC.
The squad is the minimal unit of organization.
High-performance agile teams are the way we work. Teams are the most efficient and effective structure for developing and deploying solutions.
Automate known good work.
Automate repeatable tasks in development, testing, deployment and operations. Make sure the process you automate is efficient and essential.
Design toward NoOps.
The utopia of software delivery is NoOps, where systems are self-healing and respond to events automatically — that is, with no human touch. When designing systems, consider NoOps your goal.
Everything must have an externalizable service interface.
Our products and services must have APIs to enable integration with partner and customer services. Platform DXCTM has an API gateway so that all onboarding services connect through APIs.
Security is a Day Zero consideration.
Include security at the start of the development project to reduce risk at later stages of development, avoid rework and be ready for go-live on Day One. Build security into the core foundation.
Data is the lifeblood of the modern business.
Build the solution architecture around data flow. Design data pathways to ensure systems can access the right data and process it, enabling business decisions.
Build reusable blueprints, not bespoke solutions.
All designs should be based on existing blueprints; if no blueprint exists, the design team should create one for future reuse. The blueprint, a one- to two-page document that describes the solution, should use common reference architectures and patterns.
Think serverless first.
Serverless needs to be considered as the first method for code execution in any solution or component, because serverless allocates cloud resources dynamically as they are needed. It’s efficient and elastic.