We organise our tasks into a hierarchy where the outer Feature is user-oriented, the next level down (Product backlog item) are the developer-oriented detail of

We organise our tasks into a hierarchy where the outer Feature is user-oriented, the next level down (Product backlog item) are the developer-oriented detail of the user feature and the next level are tasks that break down the work needed to compete the PBIs, in 1-8 hour chunks. Features can parent features, so what we end up with is whatever amount of detail is necessary to capture the user stories and other requirements, under which are the work items the developers care about. I think this separation provides a decent balance between producing the features the users need while still allowing developers to focus on the actual technical work required.