Building High-Performing Information Technology Project Teams

Build a working method for technology project teams that stands up to scrutiny and survives daily pressure.

📍 Istanbul🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points

Course Overview

Technical debt in technology project teams is borrowed against future delivery capacity, at compound interest. Systems supporting this part of technology and systems delivery fail in ways that are obvious afterwards and invisible before. Teams frequently over-invest in documenting this strand of technology and systems delivery and under-invest in testing it. It treats technology project teams as an operating discipline and equips participants to run it as one. The programme works equally well for those formalising this aspect of technology and systems delivery for the first time and those improving an existing approach. Participants gain a clear basis for measuring what the technology and systems delivery discipline has actually achieved. Participants apply technology project teams to their own technical platform throughout, so the output is directly usable. Practitioner evidence points the same way: the wider technology and systems delivery agenda improves fastest where responsibility for it is named and owned. It closes by agreeing the smallest change to this strand of technology and systems delivery that would make a visible difference.

Expected Learning Outcomes

01

Translate policy on technology project teams into procedures that hold up under day-to-day pressure.

02

Design a training and briefing approach that sustains competence in technology project teams.

03

Establish monitoring and alerting on technology project teams that reflects user experience.

04

Secure the software supply chain and dependencies within technology project teams.

05

Assess and manage third-party and cloud dependencies in technology project teams.

06

Design backup and recovery for technology project teams and prove it by restoring.

07

Recognise early indicators that technology project teams is drifting away from its intended design.

Who Should Attend

01

Database administrators managing data within technology project teams.

02

Information security specialists protecting technology project teams.

03

Quality and test engineers verifying technology project teams.

04

Department heads accountable for the results of technology project teams.

05

Compliance and governance staff whose remit includes technology project teams.

06

Project managers delivering changes to technology project teams.

Course Modules

01

Technology project teams: requirements, targets and service levels

2 sessions · 8 points

Session 1What to measure in technology project teams and what to ignore

  • Check that records of technology project teams answer the questions likely to be asked.
  • Close out actions on technology project teams rather than leaving them open indefinitely.
  • Collect evidence on the present handling of technology project teams before proposing changes.
  • Confirm that contractual obligations around technology project teams are understood.

Session 2Designing technology project teams around how it will fail

  • Review logging on technology project teams for coverage and retention.
  • Anticipate the objections technology project teams will raise and prepare the answers.
  • Set delivery and reliability indicators for technology project teams the team trusts.
  • Confirm the support model and escalation path for technology project teams.
02

Technology project teams: security, identity and least privilege

2 sessions · 8 points

Session 1Sizing capacity for technology project teams on measured growth

  • Name a single owner for each element of technology project teams.
  • State the availability and recovery objectives for technology project teams as numbers.
  • Run a load test on technology project teams at expected peak plus a margin.
  • Document the runbook for technology project teams to the level a new engineer could use.

Session 2Testing technology project teams before relying on it

  • Record the technical debt in technology project teams and schedule repayment.
  • Identify single points of dependency in technology project teams and reduce them.
  • Measure current load on technology project teams and project it forward twelve months.
  • Decide what will be stopped to create capacity for technology project teams.
03

Technology project teams: capacity, performance and load

2 sessions · 8 points

Session 1Proving the backup of technology project teams by restoring it

  • Identify the single points of failure in technology project teams.
  • Draft the minimum viable technical standard for technology project teams.
  • Define incident severity levels for technology project teams and the response each triggers.
  • Remove steps in technology project teams that add effort without adding assurance.

Session 2Least privilege in technology project teams without blocking the work

  • Define the trigger that would require technology project teams to be redesigned.
  • Build the competence framework that supports technology project teams.
  • Set the review interval for technology project teams and who attends.
  • Set out the decisions in technology project teams that require sign-off and by whom.
04

Technology project teams: backup, recovery and continuity

2 sessions · 8 points

Session 1Documenting technology project teams so someone else can operate it

  • Review whether technology project teams is aligned with the objectives of the technical platform.
  • Confirm every release of technology project teams can be rolled back within a defined time.
  • Set out how exceptions to technology project teams are requested and approved.
  • Test the failover for technology project teams rather than assuming it works.

Session 2Reviewing technology project teams when nothing has gone wrong

  • Assess the exit route from any cloud or vendor dependency in technology project teams.
  • Apply change control to technology project teams including emergency changes.
  • Inventory third-party dependencies inside technology project teams and their update status.
  • Confirm data retention and deletion rules applied within technology project teams.

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.