TL: DR You can’t observe a developer without altering their behavior. Several years in the past I worked on a largish venture as one among a group of builders. We had been building an internal system to assist an existing business course of. Initially issues went very nicely. The person necessities had been fairly well outlined and we worked successfully iterating on the backlog. We have been principally left to our own units.
We had a non-technical business proprietor and plenty of potential users who gave us broad targets, and who examined features as they turned accessible. Once we felt that piece wanted refactoring, we spent the time to do it. When a pain level appeared in the software program we modified the design to take away from it. We didn’t should ask permission to do any of issues, so lengthy options appeared at affordable intervals, everyone was blissful.
Then came that requirement. The one the place you attempt to exchange a knowledgeable user’s years of expertise and intuition with software. What started out as a vague and wooly requirement, soon became a monster as we began to dig into it. We tried to push again in opposition to it, or at the very least get it scheduled for a later version of the software to be delivered at some unspecified time in the future. But no, the enterprise was insistent, they wanted it in the subsequent version.
A really clever colleague thought the problem could be solved with a …