3 ms·
> you have to define what the job is Technically, you don't. Defining the work and then doing it is an overwhelmingly popular preference, but plenty of people
by marcosdumay 4y ago
> you have to define what the job is
Technically, you don't. Defining the work and then doing it is an overwhelmingly popular preference, but plenty of people do different and, AFAIK, it doesn't impact their success rate.
> That's what user stories are for
And yes, there are many other ways to do that besides user stories. "X was created to solve Y" is not by itself a good reason to use X when you need to solve Y. Whether X is any good is important too.
In fact, functionality description (the thing that user stories was created to fight against) seems to normally lead to much better systems than user-story based designs.
> There are lots of multi-billion dollar companies that use user stories.
And well, this stopped being relevant when user stories became a fad pushed by more than 99% of the managers.
- Supermancho 4y agoFor sake of clarity, "you" here means someone or some group. >> > you have to define what the job is > Technically, you don't. Technically, yes, "you" do. Most developers do not solely decide what they get paid for. This sentiment is as absurd as my example: I'll bring a toilet in tomorrow and call the serial processing job done because I delivered (without looking at any sort of work definition).
- marcosdumay 4y agoOh, your "you" here implies a manager-managed submission relation! Yeah, you can't have that without one of the parties defining the work. Again, that is a widely popular way for people to arrange themselves, but it's not obligatory. There are many people that do not work that way.