News for hackers. Stuff that matters.
Re:JIRA is an antipattern by PeterisP on Sunday December 09, 2018 @04:28PM (#18643404)
What I see in this article is a point that there's a discrepancy between goals and tasks needed to achieve these goals. If you're using JIRA for both planning features and measuring work hours spent (which many organizations are) then this brings some trouble - in an agile sprint, it makes all sense to plan that you'll do features A, B and C this week and get to D and E next week; however, it may be that by the end of the week you've spent 4 hours each to finish A, B and C and 20 hours on an infrastructure task (that's mostly done but not yet) that's needed not only for A and C but also for the next week's tasks.

The detail level and task breakdown which is appropriate for planning which features you'll prioritize and do for a sprint may not be a good task breakdown for actually assigning sub-tasks for people, looking at their progress/status during a sprint, and mapping particular commits or hours worked to them. JIRA common practices sort of force those things to be the same, which may be considered harmful.

There are no comments on this comment yet.