Demo: proposing a team split aligned with the context map
On This Lesson 3 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
run a worked session proposing a team split with engineering managers; prepares SRA-018-LAB1.
Draft outline details
Step by step
- Start from the data: the overloaded team owns pricing, promotions, and seller fees, which belong to different subdomains.
- Map to the context map: pricing and promotions are consumer-side; seller fees belong to the seller domain.
- Propose the split with interfaces and data ownership, and estimate the reduction in dependencies.
- Planned mistake: present a reorganization chart without the architectural changes. Fix: pair it with the interface and data-ownership steps that make the boundary real.
- Discuss manager constraints (headcount, careers, timing) and agree the transition plan and communication.
Demonstration
before-and-after dependency counts for the affected teams.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.