As your team grows, there are times when the interactions between team members start to feel "awkward." These "awkward interactions" can be potential triggers for team evolution - we need to evolve our teams because something doesn't feel right. However, knowing the team needs to evolve and deciding how the team should evolve are two different things.
This follows a real-world case study of a company growing its team and needing to find alternative ways of organizing itself. The talk explores how, in an ideal world, we might turn to techniques such as Wardley Mapping for strategic decision-making, Domain Driven Design for domain-related decisions, and Team Topologies for determining how to organize the teams. However, learning these techniques can seem overwhelming and cause us to procrastinate when attempting to adopt them. This talk explores how using techniques introduced with Team Topologies, such as Independent Service Heuristics and User Needs Mapping, can help us to identify and validate potential team and service boundaries while moving us closer to the adoption of techniques such as Wardley Mapping and DDD without the upfront cognitive overload.
mihofujita
recruitengineers
giuliapanozzo
sarahkey
ayaaoki1031
progmat
cltaylor
enechain
hashport
micoworks
yeseniaperezcruz
maltzj
akmur
jensimmons
paulrobertlloyd
keavy
morganepeng
holman
sonatard
garrettdimon
destraynor
moore