image from Tech Lead

Tech Lead

Type: Training
Time: 3+ days / 20+ hours
Target: Development teams, architects
Form: 40% theory / 60% practice
Place: Client's premises or Remote

Today, as a technical leader, you need much broader skills than ever before.

In the past, everything revolved around technical knowledge. However, now it’s just the tip of the iceberg. You also need to collaborate with business, define and evaluate solutions, plan work, and lead a team. A very wide range of skills.

The “Tech Lead” training will help you acquire these skills. You will learn techniques that will assist you in your daily work at every level of operation. This comprehensive training will provide you with the skills needed to overcome any challenge that comes your way.

If you are interested in this workshop, please contact me below 👇

Contact me

What you will learn

  • Learn to collaborate with business using business and architectural drivers
  • Define solution proposals, compromises, and ways to mitigate them
  • Develop an implementation plan for the selected solution along with dependencies
  • Visualize architectural models
  • Learn team collaboration techniques for architecture projects and daily work

Training Program

The program described below is a proposal - for each workshop, we create a customized program based on your needs.

  1. Responsibilities of a Technical Leader
  2. Characteristics of a Technical Leader

  1. Business Drivers - Requirements, Goals, Risks
  2. Architectural Drivers
  3. Quality Attributes
  4. Architecture Acceptance Criteria

  1. Application Patterns
  2. Integration Patterns
  3. Microservices Patterns
  4. Distributed Process Patterns
  5. Data Storage Patterns

  1. Use Cases and Diagrams
  2. Event Storming Process Level
  3. BDD - System Work Specification
  4. Architecture Diagrams - C4 Model
  5. Sequence Diagrams, API Contracts
  6. Event Storming Design Level

  1. Teamwork Models
  2. Setting Design Goals
  3. Delegating Responsibilities
  4. Different Personality Types

  1. Defining Different Solution Proposals
  2. Determining Compromises
  3. Selecting a Solution Based on Drivers
  4. Architectural Decisions

  1. Identifying Risks - People, Processes, Technologies
  2. Risk Assessment - Probability and Impact
  3. Determining Mitigation Methods

  1. Breaking Tasks into Smaller Tasks
  2. Establishing Task Dependencies
  3. Delivery Priorities
  4. Experiments

  1. Request for Comments
  2. Architectural Decision Record
  3. Processes Around Documentation

  1. Assessing Requirement Fulfillment Based on Drivers
  2. Testing and Quality Strategy
  3. Observability, Monitoring, Error Handling
  4. Good Teamwork Practices