One of the important qualities of an experienced PM is the ability to quickly figure out the complexity and main components of your product. This allows you to communicate with the team using the same language, share work, calculate the time more efficiently, and understand where risks may lie or interesting opportunities may be hiding.
What You Will Learn:
→ What the main building blocks of products are (services, integrations, databases, etc.)
→ How to build a service diagram and why a product needs it
→ What types of service architectures exist, and why is it important for scaling
What it Looks Like:
→ You help CTO to build taxi service architecture step by step
→ You get the "Architecture for PM" checklist which can be applied in your work
→ You receive additional materials on the topic
→ The lesson will take 2 to 5 hours to complete
What Students Say About the Lesson:
→ Eugene: "I began to think differently. Quite an interesting approach with a description of services like the name + what it does. I applied it at work, and it helped show several teams the areas of responsibility for each part of the project at once."
→ Anton: "It's like I've lost my technical virginity now, I'll drink coffee for that."
→ Mira: "The lesson structures knowledge well. In my product, I have an understanding of what microservices are needed, but there was no beautiful interconnected structure to draw. Now there is."
→ Ivan: "It's great that complex things are described in a very accessible way! It was useful to learn about the services within the projects and their architecture. I hadn't thought about it before because the project used a monolithic approach, but now I'll figure out what services we might need."
→ Veronika: "Finally, I have a little understanding of how I can start working on a new version of the delivery product!"