In chapter 3, there are a few sentences describing why a team owning the software is important Team ownership also enables a team to think in multiple “horizons”—from exploration stages to exploitation and execution—to better care for software and its viability. I've found Simon Wardley's "Pioneers->Settlers->Town Planners" model to be really useful in discussing why people do or don't enjoy different types of work as time progresses (https://medium.com/org-hacking/pioneers-settlers-town-planners-wardley-9dcd3709cde7) Do you think a team will be self-selecting as to whether individuals prefer to be working on more exploratory things, or fine tuning a "well-oiled" service, or do you think the membership of the team, considering this aspect, needs to be curated?

In chapter 3, there are a few sentences describing why a team owning the software is important Team ownership also enables a team to think in multiple “horizons”—from exploration stages to exploitation and execution—to better care for software and its viability. I've found Simon Wardley's "Pioneers->Settlers->Town Planners" model to be really useful in discussing why people do or don't enjoy different types of work as time progresses (https://medium.com/org-hacking/pioneers-settlers-town-planners-wardley-9dcd3709cde7) Do you think a team will be self-selecting as to whether individuals prefer to be working on more exploratory things, or fine tuning a "well-oiled" service, or do you think the membership of the team, considering this aspect, needs to be curated?

<!channel> Get your AMA questions in here for Monday!