Operations and Maintenance#
Overview#
Operations is not a separate phase but an integral part of the continuous delivery lifecycle. In a DevOps model, development and operations are unified - the team that builds the system also runs and maintains it.
What you will learn#
After completing this chapter, you will learn how to perform below activities:
- Perform Periodic Evaluation
- How to prepare user review report
- How to document defects and incidents
- How to monitor data quality and compliance metrics
- How to conduct periodic reviews of metadata attributes for recency and accuracy
- How to gather feedback from users for continuous improvement
- How to accept and plan for feature requests
- How to document and plan for patching and system updates
Key Personas & Stakeholders - RACI Matrix#
| Activity | Product Owner | System Manager | Data Engineer | Solution Architect | Business Stakeholders | Governance Team |
|---|---|---|---|---|---|---|
| Periodic Evaluation | R | A | C | C | I | C |
| User Review Report | R | A | I | I | C | C |
| Incidents and Defects | C | R | A | C | I | I |
| Monitoring | I | R | A | C | I | I |
| Patching and Updates | I | A | R | C | I | I |
R = Responsible, A = Accountable, C = Consulted, I = Informed
Prerequisites#
Coming Soon
Continuous Activities (this stage isn't a step by step stage)#
In the operations phase, key activities are often continuous in nature and each sub activity has a step by step guide adopted as a chosen practice within the data team
Example
- Assign incident to yourself
- Respond to user by acknowledging the incident and a tentative ETA
- Work on the incident and provide timely updates
- Open a defect or resolve the incident permanently
- Inform user with defect id and ETA while consulting product owner and solution architect.
Coming Soon