Don't say "capacity" when you mean "headcount"
A team's /capacity/ is how much they're capable of doing together.
Pretending they're equivalent is (foolishly) pretending that programming is mostly typing.
A team's /capacity/ is how much they're capable of doing together.
Pretending they're equivalent is (foolishly) pretending that programming is mostly typing.
Capacity is the right idea, though.
What can you do to increase the ability to do work other than bumping up the number of developers.
But likely you can improve skills and focus and tooling and raise capacity, remove waits and queues and returns.
Your capacity isn't headcount.
What can you do to increase the ability to do work other than bumping up the number of developers.
But likely you can improve skills and focus and tooling and raise capacity, remove waits and queues and returns.
Your capacity isn't headcount.
BTW: if you're doing Angular but nobody really understands Angular, then maybe adding an Angular expert to the team will increase capacity. It's SKILL and FOCUS after all.
If you have individual assignments it won't help much, though.
If you have individual assignments it won't help much, though.
The /capacity/ of a three-person team may be considerably higher or lower than the capacity of a five-person team. A set of 12-person teams may each have a very different /capacity/ depending on skills, experience, and problem domain.
Counting noses is unreliable.
Counting noses is unreliable.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
