Section 1: Introduction to Technical Program Management

Section 3: Program Initiation (Requirements & Design)

1. Understanding the Problem Statement – Defining the Program Vision 
2. Learn how to effectively initiate a program without the over-design of waterfall vs. the undercooked  agile / scrum model 
3. The Ideal Iteration 0 wherein the team walks away with technical structure and working agreements 
4. Pitfalls of Requirements (Agile & Waterfall) → Waterfall Too Much, Agile Too Little
5. User-Centric categorization of requirements into Functional & Non-Functional  
6. Introduction to Journey Driven Development (JDD) as a method of defining technical value delivery and  financial / non-financial value add 
7. Using the JDD approach to better prioritize the technical work to deliver value  
8. Capturing the Intrinsic & Extrinsic Technical Requirements & Architecture Design fundamentals
9. Leveraging web tools to create technical artifacts such as Solution Architecture Diagrams, Class  Diagrams and Entity Relationship Diagrams 
10. Recognizing the importance of the Three Ts of Program Planning → Team, Technology & Time (TTT) 
11. Learn techniques on Scope Management & understand the common mishaps that create uncertainty

12. Understand the Theory of Estimation → Using Relative and Absolute estimates to factor in accuracy vs.  precision and the cone of uncertainty

13. How to navigate the organizational landscape by using political management & planning →  Organizational Limitations, Best Practices, Prior Experience

14. Closing out the initiation phase with a technical and program management structure with Cadence &  Artifacts Delivery Set-up and agreed

15. Team Exercise – A simulation of waterfall and agile requirements gathering to determine the efficacy of  the models and a need for change

16. Team Exercise – Real-world use case of enabling a new service to a brownfield initiative vs. a greenfield  program initiative

17. Team Exercise – Create a technical solution diagram using a web tool that depicts a real-world use case

18. Team Exercise – Initiation of a Technical Program in a Non-Technical, Political Landscape

Section 4: Technical Program Execution

1.  Recapping the execution of the various agile ceremonies in a delivery team of a technical program

2. How to Effectively communicate within a Technical Program at the various organizational levels

3. Learn the best practices of written communication such as emails and newsletters

4. How to actively measure team performance & technical progress beyond the traditional burndown  charts and velocity metrics

5. Understanding and installing the DevOps practices of Continuous Integration, Continuous Delivery and  Continuous Deployment in the technical delivery teams

6. How to effectively manage and respond to Program Management Bureaucracy

7. Acknowledge the common program execution pitfalls – DSU Fails, No Retros, No POs, No Testing in  Sprints, Backlog Readiness, Vendor Management, Resource Sharing – and how to effectively manage  these scenarios

8. Planning for and addressing technical debt in your technical program

9. Leveraging the different Technical Deployment Patterns for Roll-out & Release Management – Blue  Green Deployments, Dark Launches, A/B Testing, Canary Releases, Feature Flags etc. 

10. Setting up a DevOps, DevSecOps & Site Reliability Engineering Model for the program as it deploys  iteratively and needs to be maintained while continuously wowing the customer with new features

11. Recognizing the technical metrics and running the program using the NorthStar metric to gain Business  Intelligence using Telemetry, TDD, HDD, Logging, Monitoring and Notifications

12. Team Exercise – Creation of a Robust Execution Structure across the SDLC 

13. Team Exercise – Identify the appropriate deployment pattern for different real-world scenarios

14. Team Exercise – Create a release management plan for a greenfield large scale global launch

15. Case Study – Amazon AWS S3 Outage

Section 5: Program Control & Reporting

1. How to set up a Control & Reporting Structure at Different Levels of a Program – Team Level vs Line  Management Level vs Senior Leadership Level

2. What kind of Technical Delivery Metrics should be captured & reported at various levels of the  program – Code Coverage, Automation, Deployment Frequency, MTTR etc.

3. Capturing and reporting metrics around People, Performance & Program Management – Statuses, RAG,  capacity, workload, efficiency, and many others

4. Understanding and building a program matrix of the reporting information, frequency, target audience  and intended outcome for all communication and control

5. The role of a TPM in strategically dealing with political scenarios in organizations

6. Scaling, Expanding & Distributing the Technical Solution across the Organization as the TPM transitions  the program into its next state

7. Team Exercise – Sam Altman’s “What I Wish Someone Had Told Me” as it pertains to organizational  navigation and value delivery in your teams

8. Team Exercise – Considering the Spotify and Amazon S3 case studies that have been discussed, let’s  build a reporting chart

9. Team Exercise – Dashboard in traditional delivery management tools such as Smartsheet, Jira and  Azure DevOps 

Section 6: Capstone Program (Optional Day-3 for Customized Private Delivery only)

1. Technical Program Management Simulation
2. Team Exercise – Designing a modern application microservice from initiation to technical execution,  communication and reporting while dealing with challenges