5 ms·
I have to agree with the other commenters about #1. Adding people adds team overhead, and that is killer. It’s actually fairly surprising how people still think
by ChrisMarshallNY 6y ago
I have to agree with the other commenters about #1. Adding people adds team overhead, and that is killer. It’s actually fairly surprising how people still think of that as a solution, when there is so much prior art, showing it’s a lot less effective than you’d think (see Brooks, Fred -The Mythical Man-Month).
I encounter people all the time, that are inordinately proud of their infrastructure and process, and how that reduces team overhead, while allowing them to treat engineers like LEGO blocks. I worked for a Japanese company, and they actually make this work (sort of, and at a big price). It requires a fairly massive and inflexible structure (despite being labeled “agile,” it tends to be remarkably rigid).
There’s absolutely no substitute for a seasoned, experienced team that has worked together for years, and is secure in its cohesiveness. “Tribal Knowledge” is a dirty word in today’s business culture, but it is, hands down, the most efficient “team glue” in the world. It is also thousands of years old. No high-tech equipment required. Mammoth hunters worked as a team, and achieved big results. Military teams are as old as history, and that is all about commoditizing “tribal knowledge,” and investing in people, not just weapons and tactics.
When I read “add slack,” I was like “How does adding a gab tool improve innovation?”. Then I read that it meant adding downtime/flex goal stuff, and totally agree.
- WJW 6y agoHaving been a Navy officer myself, I cannot agree more about the role of experience and training in team formation. So many software companies just throw together a few people and expect them to be productive right off the bat but that is simply not how people work. Reorgs every six months actively destroy any sense of team formation too. That said, the military enjoys a level of personnel lock in that few software orgs can dream of. I don't know many software engineer that would agree to a five-year contract with no option for early leaving.
- ChrisMarshallNY 6y ago> I don't know many software engineer that would agree to a five-year contract with no option for early leaving. Which is why it's important to practice good, humane management. Good engineers can punch their own tickets. Need lots of carrot, and very little stick. I kept high-functioning, smart, experienced, C++ image processing engineers together for decades on my team, despite mediocre pay, and a pretty challenging environment (no, I won't go into detail). This required that I connect with each and every member of my team as a human, often on an equal basis, as opposed to as a "superior/inferior" basis. It also meant that I needed to learn about the drivers for each person, give them as much family time as they needed, back off from micromanaging, and find ways to help them to resolve differences in ways that strengthened the team. As I have stated before, when they finally rolled up my team, after 27 years, the person with the least tenure had a decade. In about a month, we'll be getting together for a cookout at one of my former employees' home. We haven't worked together in over 3 years, but we still share a bond.
- marcinzm 6y agoThe Mythical Man Month as I remember only argues that adding more people to a PROJECT is a killer and that adding more people to a team gives you non-linear productivity gains. Project being defined as a self contained piece of work with a scope and deadline. In the long term more people with a decent structure will give you more overall output although less efficiency. If that is worth it is a business decision.
- ChrisMarshallNY 6y agoGood point, but the OP was using the term "team," while diagramming what is clearly a project lifecycle. I think that the article is a bit of a "mashup." You can't really have a team "falling behind," but a team can certainly be "innovating."
- marcinzm 6y agoI saw his diagrams as referring to a stream of projects rather than a single project. Or a backlog of tickets if you look at it from an agile perspective. In that environment you can definitely have a team be falling behind in the sense of items going into the backlog faster than they are worked on. Each item is a project with a deadline that is being missed. However the team metric is not merely those individual existing projects but the aggregate of all current and future projects. A larger team will usually help with that last metric in the long term.