3 ms·
Whether this works on not depends on the team structure and person writing the task. Yes, directly writing tasks is more efficient, but it requires the person
by kube-system 6y ago
Whether this works on not depends on the team structure and person writing the task. Yes, directly writing tasks is more efficient, but it requires the person writing the task to deeply understand the perspectives of both the development team and the people using the software.
Most teams don't have (enough of) these types of people. It is fairly common for teams to primarily consist of people who are non-engineer users, and technical engineers who aren't intimately familiar with the users' jobs. If your team has these groups working together, and these lines aren't clearly drawn, then you often get people overstepping their bounds: users demanding technical changes that make no technical sense, and developers building features that make no business sense.
And this isn't a fault of the users or developers, it's a failing of process. People inherently want to decrease friction in their requests and their interactions. Five completely reasonable requests over the course of a year might add up to a horrible application -- not because the user or the developer was at fault for making a bad decision, but because the entirety of the goal was never communicated. This is what user stories do: force different groups to fully communicate.