Set acceptance criteria for development and operations collaboration before work begins rather than after.
Building a Culture of Collaboration Between Development and Operations Teams
An applied course in development and operations collaboration built around the decisions practitioners actually face.
📍 Abu Dhabi🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
The documentation for development and operations collaboration is accurate only until the next release. Technical debt in operations collaboration is borrowed against future delivery capacity, at compound interest. Participants gain a realistic view of what the practice within technology and systems delivery costs and what it returns. Sessions alternate between guided analysis of development and operations collaboration and supervised application. The programme suits teams tackling this strand of technology and systems delivery together as readily as individuals attending alone. The course sets out a working method for operations collaboration that participants can apply the week they return. The professional literature on development and operations collaboration converges on a small set of controls that reliably work. Plans for operations collaboration often fail at the handover point between functions. The course ends by identifying what the participant will stop doing to make this part of technology and systems delivery sustainable.
Expected Learning Outcomes
Establish monitoring and alerting on operations collaboration that reflects user experience.
Assess and manage third-party and cloud dependencies in development and operations collaboration.
Apply a repeatable review cycle to operations collaboration and act on what it produces.
Build the internal capability for development and operations collaboration rather than depending on external support indefinitely.
Document operations collaboration to the level a new engineer could operate it.
Apply access control and least privilege throughout development and operations collaboration.
Who Should Attend
Software engineers and technical leads building development and operations collaboration.
Network and communications engineers supporting operations collaboration.
Project managers delivering changes to development and operations collaboration.
Training and development staff building internal capability in operations collaboration.
Database administrators managing data within development and operations collaboration.
Members of committees that take decisions affecting operations collaboration.
Course Modules
Development and operations collaboration: incident response and severity
2 sessions · 8 pointsSession 1Sizing capacity for development and operations collaboration on measured growth
- Assess the exit route from any cloud or vendor dependency in development and operations collaboration.
- Configure alerting on operations collaboration that reflects what users experience.
- Rank the weaknesses in development and operations collaboration by consequence rather than by ease of fixing.
- Review access rights on operations collaboration and remove what is no longer needed.
Session 2Least privilege in operations collaboration without blocking the work
- Draft the minimum viable technical standard for development and operations collaboration.
- Estimate the resource operations collaboration requires to run as designed.
- Confirm that contractual obligations around development and operations collaboration are understood.
- Apply change control to operations collaboration including emergency changes.
Operations collaboration: backup, recovery and continuity
2 sessions · 8 pointsSession 1Where operations collaboration typically breaks, and why
- State the availability and recovery objectives for development and operations collaboration as numbers.
- Inventory third-party dependencies inside operations collaboration and their update status.
- Document the runbook for development and operations collaboration to the level a new engineer could use.
- Check that operations collaboration still works when volumes rise unexpectedly.
Session 2Comparing operations collaboration with recognised practice
- Measure current load on development and operations collaboration and project it forward twelve months.
- Write down the assumptions underpinning the approach to operations collaboration.
- Test the failover for development and operations collaboration rather than assuming it works.
- Build the internal briefing that explains operations collaboration to those affected.
Operations collaboration: monitoring, alerting and observability
2 sessions · 8 pointsSession 1The hard cases in operations collaboration and how to reason about them
- Confirm the support model and escalation path for development and operations collaboration.
- Set delivery and reliability indicators for operations collaboration the team trusts.
- Confirm that reporting on development and operations collaboration reaches the people who can act.
- Prepare the response for the most likely failure in operations collaboration.
Session 2Designing development and operations collaboration around how it will fail
- Remove steps in development and operations collaboration that add effort without adding assurance.
- Identify the single points of failure in operations collaboration.
- Define the trigger that would require development and operations collaboration to be redesigned.
- Define incident severity levels for operations collaboration and the response each triggers.
Operations collaboration: documentation, support and handover
2 sessions · 8 pointsSession 1Retiring the legacy part of operations collaboration
- Agree the smallest change to development and operations collaboration that would be visibly useful.
- Review logging on operations collaboration for coverage and retention.
- Distinguish symptoms from causes when development and operations collaboration underperforms.
- Build the competence framework that supports operations collaboration.
Session 2Making releases of operations collaboration routine instead of risky
- Collect evidence on the present handling of development and operations collaboration before proposing changes.
- Confirm data retention and deletion rules applied within operations collaboration.
- Run a load test on development and operations collaboration at expected peak plus a margin.
- Prepare the summary of operations collaboration that senior management will read.
Choose the package that suits you
Silver Package
At least 3 people
USD1,250
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Gold Package
At least 3 people
USD1,850
- 5-night stay in a 5-star hotel
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Complete your registration
We will contact you within one business day to confirm.