Assess and manage third-party and cloud dependencies in technology project estimation.
Building Strategies to Estimate Technology Project Costs and Schedules
Learn to design, measure and defend your organisation's approach to technology project estimation.
Course Overview
Availability targets for technology project estimation are commercial commitments, whatever the engineering team calls them. Most outages involving the practice within technology and systems delivery are triggered by a change somebody considered routine. It is appropriate for those preparing to take on wider responsibility for this part of technology and systems delivery. Comparative studies of technology project estimation across sectors find the same handful of failure points recurring. Each session closes with a decision the participant must justify about the wider technology and systems delivery agenda in their own setting. Ambition around this part of technology and systems delivery outruns capacity unless the sequencing is deliberate. The programme takes participants through technology project estimation end to end, from framing the problem to closing it out. Participants develop a defensible line of reasoning for the choices they make about this strand of technology and systems delivery. The course ends by identifying what the participant will stop doing to make this area of technology and systems delivery sustainable.
Expected Learning Outcomes
Document technology project estimation to the level a new engineer could operate it.
Establish monitoring and alerting on technology project estimation that reflects user experience.
Structure the service desk and support model for technology project estimation.
Reduce avoidable variation in how technology project estimation is carried out across teams.
Test the organisation's response to technology project estimation under conditions that are less than ideal.
Structure records of technology project estimation so that they answer the questions an auditor will actually ask.
Who Should Attend
IT governance and audit staff reviewing technology project estimation.
Software engineers and technical leads building technology project estimation.
Planning staff whose forecasts and budgets are affected by technology project estimation.
Managers in small and medium organisations who own technology project estimation alongside other duties.
Infrastructure and platform engineers operating technology project estimation.
Database administrators managing data within technology project estimation.
Course Modules
Technology project estimation: change control and rollback
2 sessions · 8 pointsSession 1Where technology project estimation typically breaks, and why
- Draft the minimum viable technical standard for technology project estimation.
- State the availability and recovery objectives for technology project estimation as numbers.
- Plan the sequence in which improvements to technology project estimation will be introduced.
- Confirm that those complying with technology project estimation understand why it exists.
Session 2Sizing capacity for technology project estimation on measured growth
- Rank the weaknesses in technology project estimation by consequence rather than by ease of fixing.
- Review whether technology project estimation is aligned with the objectives of the technical platform.
- Prepare the summary of technology project estimation that senior management will read.
- Review access rights on technology project estimation and remove what is no longer needed.
Technology project estimation: security, identity and least privilege
2 sessions · 8 pointsSession 1Retiring the legacy part of technology project estimation
- Inventory third-party dependencies inside technology project estimation and their update status.
- Apply change control to technology project estimation including emergency changes.
- Run a load test on technology project estimation at expected peak plus a margin.
- Identify the single points of failure in technology project estimation.
Session 2Least privilege in technology project estimation without blocking the work
- Define incident severity levels for technology project estimation and the response each triggers.
- Document the runbook for technology project estimation to the level a new engineer could use.
- Name a single owner for each element of technology project estimation.
- Confirm every release of technology project estimation can be rolled back within a defined time.
Technology project estimation: monitoring, alerting and observability
2 sessions · 8 pointsSession 1Monitoring technology project estimation from the user's point of view
- Agree what will be standardised in technology project estimation and what will not.
- Restore a backup of technology project estimation in a test environment and time it.
- Record the rationale for each significant choice made about technology project estimation.
- Confirm that contractual obligations around technology project estimation are understood.
Session 2Reviewing technology project estimation when nothing has gone wrong
- Review logging on technology project estimation for coverage and retention.
- Agree the indicators that will show whether technology project estimation is improving.
- Configure alerting on technology project estimation that reflects what users experience.
- Remove steps in technology project estimation that add effort without adding assurance.
Technology project estimation: requirements, targets and service levels
2 sessions · 8 pointsSession 1Proving the backup of technology project estimation by restoring it
- Establish who is informed, consulted and accountable in technology project estimation.
- Set delivery and reliability indicators for technology project estimation the team trusts.
- Record the technical debt in technology project estimation and schedule repayment.
- Define the trigger that would require technology project estimation to be redesigned.
Session 2Comparing technology project estimation with recognised practice
- Prepare the response for the most likely failure in technology project estimation.
- Identify single points of dependency in technology project estimation and reduce them.
- Test the failover for technology project estimation rather than assuming it works.
- Confirm data retention and deletion rules applied within technology project estimation.
Choose the package that suits you
Silver Package
At least 3 people
- 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
- 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.