Handle the trade-offs in agile software project management between speed, cost and assurance explicitly rather than implicitly.
Building Agile Software Development Project Management Strategies
An applied course in agile software project management built around the decisions practitioners actually face.
📍 Tripoli🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Technical debt in agile software project management is borrowed against future delivery capacity, at compound interest. The documentation for project management is accurate only until the next release. Practitioner evidence points the same way: the wider technology and systems delivery agenda improves fastest where responsibility for it is named and owned. Participants gain a clear basis for measuring what agile software project management has actually achieved. Most organisations already have a policy on this part of technology and systems delivery; far fewer can show it working. The teaching approach is deliberately practical: participants build a technical standard for project management as they go. It treats agile software project management as an operating discipline and equips participants to run it as one. The content is relevant to those who own project management and to those who are held accountable for its results. The final module sets out how progress on this strand of technology and systems delivery will be evidenced six months later.
Expected Learning Outcomes
Measure delivery and reliability of project management with indicators teams trust.
Apply access control and least privilege throughout agile software project management.
Structure the service desk and support model for project management.
Establish escalation routes for agile software project management that work outside normal hours.
Secure the software supply chain and dependencies within project management.
Test the organisation's response to agile software project management under conditions that are less than ideal.
Who Should Attend
Network and communications engineers supporting agile software project management.
Business partners who must understand project management well enough to challenge it.
Service desk and support leads handling incidents in agile software project management.
Procurement and contracting staff whose agreements set obligations around project management.
Solution architects designing agile software project management.
Database administrators managing data within project management.
Course Modules
Agile software project management: documentation, support and handover
2 sessions · 8 pointsSession 1Reviewing agile software project management when nothing has gone wrong
- Confirm data retention and deletion rules applied within agile software project management.
- Assess the exit route from any cloud or vendor dependency in project management.
- Review access rights on agile software project management and remove what is no longer needed.
- Record what was learned when project management did not go as planned.
Session 2Making releases of project management routine instead of risky
- Define acceptance criteria for agile software project management in advance.
- Confirm every release of project management can be rolled back within a defined time.
- Confirm the support model and escalation path for agile software project management.
- Identify the data already collected that bears on project management.
Project management: change control and rollback
2 sessions · 8 pointsSession 1Running an incident on project management calmly
- Remove steps in agile software project management that add effort without adding assurance.
- Apply change control to project management including emergency changes.
- Confirm that contractual obligations around agile software project management are understood.
- State the availability and recovery objectives for project management as numbers.
Session 2Making project management work when resources are constrained
- Measure current load on agile software project management and project it forward twelve months.
- Configure alerting on project management that reflects what users experience.
- Rehearse the briefing on agile software project management that would follow an incident.
- Set delivery and reliability indicators for project management the team trusts.
Project management: security, identity and least privilege
2 sessions · 8 pointsSession 1Documenting project management so someone else can operate it
- Identify single points of dependency in agile software project management and reduce them.
- Build the competence framework that supports project management.
- Record the technical debt in agile software project management and schedule repayment.
- Define the trigger that would require project management to be redesigned.
Session 2The paperwork for agile software project management that is actually needed
- Test the failover for agile software project management rather than assuming it works.
- Restore a backup of project management in a test environment and time it.
- Rank the weaknesses in agile software project management by consequence rather than by ease of fixing.
- Define incident severity levels for project management and the response each triggers.
Project management: architecture and designing for failure
2 sessions · 8 pointsSession 1Least privilege in project management without blocking the work
- Identify the single points of failure in agile software project management.
- Collect evidence on the present handling of project management before proposing changes.
- Close out actions on agile software project management rather than leaving them open indefinitely.
- Inventory third-party dependencies inside project management and their update status.
Session 2The change to project management that caused the last outage
- Check that agile software project management still works when volumes rise unexpectedly.
- Establish the boundary of project management and record what sits outside it.
- Anticipate the objections agile software project management will raise and prepare the answers.
- Draft the minimum viable technical standard for project management.
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.