Problem Creep: Noticing Problem

Yesterday, I wrote about current participants in a growing code repository.

As long as the number of participants do not grow OR participants do not introduce any new computers, growing more code repositories will not be a problem.

When there is a new participant OR a new computer for a current participant, only then would current participants would notice the number of code repositories as a problem.

The operative word is: notice.

Depending on the team, the following can happen:

• the team stops and fixes the problem
• the team asks everyone if it’s a big enough of a problem to fix (does it affect them?)
• the team says to whoever has the problem: “works for me, if I can get it working, you can too.”

Ultimately, the question is for a manager: dedicate resources to fix the current problem or let the person with the problem resolve on their own?

More on this topic tomorrow