This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
Picking up from the last AMA, if we are attempting cross pollination, how do you address the too many team leads scenario? Max’s example of DevOps1 and DevOps2 - if both groups have different systems and/or approaches, how do you suggest they both join to work on a common backlog? Especially in terms of short sprints - there doesn’t appear to be a lot of time to get groups with disparate systems working together
Picking up from the last AMA, if we are attempting cross pollination, how do you address the too many team leads scenario? Max’s example of DevOps1 and DevOps2 - if both groups have different systems and/or approaches, how do you suggest they both join to work on a common backlog? Especially in terms of short sprints - there doesn’t appear to be a lot of time to get groups with disparate systems working together
Is there benefit in mapping out teams current communications channels across and out of an org chart (as teams or an org are seemingly in the middle of traditional org and a lean/agile org)?
Is there benefit in mapping out teams current communications channels across and out of an org chart (as teams or an org are seemingly in the middle of traditional org and a lean/agile org)?
What other "universal truths" did you consider for this book but didn't make it to the final print edition?
What other "universal truths" did you consider for this book but didn't make it to the final print edition?
I've worked for numerous small but growing companies over the past few years where there is always a lot of churn in staff and team structure due to growth and shifting priorities. This obviously conflicts with the notion of "long-lived" teams as a goal mentioned in the preface; how do you mitigate that?
I've worked for numerous small but growing companies over the past few years where there is always a lot of churn in staff and team structure due to growth and shifting priorities. This obviously conflicts with the notion of "long-lived" teams as a goal mentioned in the preface; how do you mitigate that?
Have you had success with an HR organization helping them understand Conway's law and its implications for org design?
Have you had success with an HR organization helping them understand Conway's law and its implications for org design?
Apologies if this is covered later in the book (I’m reading on a kindle and haven’t read ahead): our organisation has a dedicated & centralised 24x7 Enterprise Command Centre that deals with all 1st Line monitoring & support (across Service-Application-Infrastructure) & 2nd Line Support for infrastructure. This is separate to our end-user facing IT Service Desk. Do you have a view on how these could/should be considered when it come to potential bringing-together of IT Change/Dev & IT Ops teams? Thanks
Apologies if this is covered later in the book (I’m reading on a kindle and haven’t read ahead): our organisation has a dedicated & centralised 24x7 Enterprise Command Centre that deals with all 1st Line monitoring & support (across Service-Application-Infrastructure) & 2nd Line Support for infrastructure. This is separate to our end-user facing IT Service Desk. Do you have a view on how these could/should be considered when it come to potential bringing-together of IT Change/Dev & IT Ops teams? Thanks
I can see some great questions here 🤓 Looking forward to the AMA soon!
how do you capture the impact on conway's law and how it has shaped the existing architecture and teaming structure that we are trying to change? what approaches do you recommend for visualizing this to make it tangible for people who are nose-down in building and operating or the high-level leadership?
how do you capture the impact on conway's law and how it has shaped the existing architecture and teaming structure that we are trying to change? what approaches do you recommend for visualizing this to make it tangible for people who are nose-down in building and operating or the high-level leadership?
Can you name some apps that can be used to visualise teams in a networked structure? (Dynamic apps that are connected to a user directory service like Active Directory.) Do you have some real or close to real figures? Isn’t the hierarchical org chart still, unfortunately, the mostly used one? From your experience, how common are networked charts today?
Can you name some apps that can be used to visualise teams in a networked structure? (Dynamic apps that are connected to a user directory service like Active Directory.) Do you have some real or close to real figures? Isn’t the hierarchical org chart still, unfortunately, the mostly used one? From your experience, how common are networked charts today?
<!channel> Here's the link to join today's AMA with Matthew in 30 mins! https://zoom.us/j/588873365
We'll be getting through as many of the above questions as possible in order of receiving them.
https://codescene.io/projects/177/jobs/15348/results/social/social-networks
https://codescene.io/projects/177/jobs/15348/results/social/social-networks
https://codescene.io/docs/configuration/developers-and-teams.html
Thanks for the questions everyone 🙌 - I enjoyed the AMA. Hope it was useful.
<!channel> Still editing out the waiting time before starting the AMA today with Matthew, but here's the link to watch: https://youtu.be/kCzrqGLytUI