I wrote about general meeting problems in Recognize the Problems That Prevent Effective Meetings (Collocated, Remote, Hybrid). But “hybrid” teams have much worse meeting problems. During the pandemic, most of us understood how to create nebula team meetings that worked. (Dispersed teams are nebula teams. See How To Understand Your Team Type: Collocated, Satellite, Cluster, Nebula for […]
Meetings. We all have them. Most of us hate them. When I ask why, here are some of the responses I hear: They take too much time away from our “real work.” It’s too hard to find time to meet. Our calendars are too full. We can’t find a place to meet. If we’re back
I thought watermelon status was something “everyone” knew about. But it’s not! Read No More Watermelon Status Reports: How to Use Stories to Explain Project State. That’s a persona-based approach to help other people understand the project’s reality. You also might like Velocity is Not Acceleration to see charts and data I use and recommend.
Several people on social media have denigrated the terms “project manager” and “program manager.” These people claim there is no need for either role in an effective team, especially an agile team because the team can manage its own deliverables. While some agile teams can manage their own deliverables, that’s not the only role for
A colleague unfamiliar with lifecycles or agility asked, “How can we use sprints in this approach?” and pointed to a phase-gate approach with documentation deliverables after each phase. It looked just like the serial lifecycle in the image on the left. (That’s because a finance person drew the lifecycle.) I said, “You can’t use ‘sprints.’
Does your organization have an enterprise architect or Chief Product Person? We create these positions to check that the teams don’t try to implement something “wrong.” However, a single person in this position creates bottlenecks and dependencies. (A committee might create even tighter bottlenecks.) Those dependencies slow the work. If a person delays the work,
Even when managers try to create cross-functional teams, the teams still have dependencies. Dependencies slow and make finishing the work more difficult. Too many teams have a built-in dependency creator—code review. When we take time to perform code review after we write the code (or the tests), we create dependencies between the people on the
I’m seeing different kinds of “hybrid remote” teams these days. I already wrote about satellite teams (see Five Tips for Your Successful (Hybrid Remote) Satellite Team). Now, I’m also seeing cluster teams. Cluster teams have people in several locations, with collocated people in some locations. (See How To Understand Your Team Type: Collocated, Satellite, Cluster,
Here’s a scenario I see in all kinds of businesses. Your team has product-focused work. And, the team also has “fast” response-required, ad hoc work: Production support, when something breaks. You need to fix this right away. Provide technical support when people have questions. The team needs to answer these questions on a “timely” basis.
You’ve spent the better part of two years organizing for all-remote work. Now, your managers want people back in the office. However, your team won’t all be back in the same time and space. People get to choose which days (and possibly hours) they come into the office. That means you don’t have a collocated