This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
My company is about to create so called business strategy department (it is announced, but not formed yet). It will consists of product owners, "business architects" (people who know what our system does as a whole, know different domains and interconnections between them) and analysts who translate new laws to requirements for our system. Management is about to define who decides about what and who is responsible for what. Maybe you have some advice on that? What would be a big no-no and should be avoided? How should the business units be formed to best support value creating teams? Are there any books about this? I would be also happy to hear from club members about your experience.
My company is about to create so called business strategy department (it is announced, but not formed yet). It will consists of product owners, "business architects" (people who know what our system does as a whole, know different domains and interconnections between them) and analysts who translate new laws to requirements for our system. Management is about to define who decides about what and who is responsible for what. Maybe you have some advice on that? What would be a big no-no and should be avoided? How should the business units be formed to best support value creating teams? Are there any books about this? I would be also happy to hear from club members about your experience.
This is AMA, so let's have fun: what is the worst team topology you have heard of? What happened there?
This is AMA, so let's have fun: what is the worst team topology you have heard of? What happened there?
When the team is a delivery bottleneck, how can we identify if it is a cognitive load problem or it's a result of bad estimation/planning practices?. Thanks
When the team is a delivery bottleneck, how can we identify if it is a cognitive load problem or it's a result of bad estimation/planning practices?. Thanks
We don't want to overload the team cognitive load, that's fine. But Agile and DevOps suggests that team should have all the skills to do their work. We want people to not only have 1 expertise, but to expand their knowledge and become T-shape people. How to we balance that with cognitive overloads ? (ref: chapter 1,page 11)
We don't want to overload the team cognitive load, that's fine. But Agile and DevOps suggests that team should have all the skills to do their work. We want people to not only have 1 expertise, but to expand their knowledge and become T-shape people. How to we balance that with cognitive overloads ? (ref: chapter 1,page 11)
Is there a core definition of ‘team’ that you use? I just want to make sure I and others have correct context. Is it Pod, two pizza team, or other such construct. I see Team of Teams concepts are covered later, but what is the core team. One issue that we face is that Team can be considered either 8 people or 80 people. This when we try to discuss concepts of Cognitive Capacity, it gets lost on others as they can’t imagine that 80 people cannot comprehend something. Later on you cover monoliths and coupling etc, and I evidence that these things have been created and not seen as a problem because the concept of ‘team’ was so huge.
Is there a core definition of ‘team’ that you use? I just want to make sure I and others have correct context. Is it Pod, two pizza team, or other such construct. I see Team of Teams concepts are covered later, but what is the core team. One issue that we face is that Team can be considered either 8 people or 80 people. This when we try to discuss concepts of Cognitive Capacity, it gets lost on others as they can’t imagine that 80 people cannot comprehend something. Later on you cover monoliths and coupling etc, and I evidence that these things have been created and not seen as a problem because the concept of ‘team’ was so huge.
What was the most surprising thing you learned while writing this book? (eels and groupers don't count!)
What was the most surprising thing you learned while writing this book? (eels and groupers don't count!)
What belief(s) or opinion(s) did you have changed as a result of researching and writing the book?
What belief(s) or opinion(s) did you have changed as a result of researching and writing the book?
Along this line - what were the key thoughts which crystalized in the process of writing the book?
<!channel> We've got more than enough questions to fill the hour with Manuel, and so we are closing submissions for this AMA. (There will be more!) The AMA will be hosted on Zoom at 8am PDT (~35 minutes from now) here: https://zoom.us/j/555599342 Click the link a few minutes early to give yourself time to get setup. And it will be recorded so that it can be shared with people who couldn't join live.
@alexb will the session be recorded for later viewing? I have conflicting meetings some of the days...
How long does it typically take to post or see the recorded session? I was hoping to watch during my lunch hour, but the video doesn’t seem to be available.
Great AMA session today. Thanks @manuel.pais and @alexb for packing so much value in an hour
@wall.jt Still adding details, but you can access here: https://youtu.be/8em9l2mdni8
<!channel> video from the AMA with Manuel earlier is now live! https://youtu.be/8em9l2mdni8 — see description for timestamp links.