I don't disagree - I worked on a task management system many years ago and task and subtask always made a lot more sense than story and task. And epic should just be project.
It's the brittle systems that try and force a peg in a hole regardless of size or shape.
I've worked with customers who stories worked well because the concept is just to talk through use-cases. Others have been involved in building software previously and it's overkill.
Current corpo job uses the phrase stories, but refuses to get involved with any planning or spec building so task and subtask would make more sense, but subtasks aren't visible on the board and we aren't allowed to update it.
We also aren't allowed to move a task back, so every time someone accidentally moves the wrong task we have to cancel it and recreate it. Such a pain.
It's the brittle systems that try and force a peg in a hole regardless of size or shape.
I've worked with customers who stories worked well because the concept is just to talk through use-cases. Others have been involved in building software previously and it's overkill.
Current corpo job uses the phrase stories, but refuses to get involved with any planning or spec building so task and subtask would make more sense, but subtasks aren't visible on the board and we aren't allowed to update it.
We also aren't allowed to move a task back, so every time someone accidentally moves the wrong task we have to cancel it and recreate it. Such a pain.