▲ 213 ▼ AI Software Development – What Does The Data Say? (codemanship.wordpress.com) submitted 2 weeks ago* (last edited 2 weeks ago) by rimu@piefed.social to c/programming@programming.dev 67 comments fedilink hide all child comments studies show a clear trend – output is up (more code, more commits, bigger diffs), but outcomes don’t reflect that trend. If anything, the average team is taking longer to ship worse software
[–] jtrek@startrek.website 46 points 2 weeks ago (2 children) Has management known that? A lot of problems seem to be downstream from "management are idiots and assholes" permalink fedilink source parent hideshow 4 child comments replies: [–] Feyd@programming.dev 9 points 2 weeks ago (3 children) I'm sure there were pockets but it legitimately seemed like that dragon had been slain until recently. Trying to assign more meaning to scrum points has been in vogue for a while though. permalink fedilink source parent hideshow 6 child comments replies: [–] jtrek@startrek.website 6 points 2 weeks ago (1 child) My team assigns both hours and points to tasks. I've never seen the points used for anything but they still spend time on it. permalink fedilink source parent hideshow 2 child comments replies: [–] Kissaki@programming.dev 3 points 2 weeks ago That's... an interesting approach. permalink fedilink source parent [–] dejected_warp_core@lemmy.world 2 points 2 weeks ago That battle is perpetual. Lazy management sees a number that resembles a statistic, and try to use it as an easy metric for stuff it doesn't represent. Points do aggregate into velocity, which is worth measuring. But on their own, points are a proxy for estimation in $SPRINT_LENGTH days. The way to manage up is to keep making it clear that the smallest unit of estimation in Agile is the sprint length; points are used to subdivide that but only to ensure that the sprint itself is not overloaded and thus an accurate estimate. permalink fedilink source parent [–] ripcord@lemmy.world 1 point 2 weeks ago (story points) permalink fedilink source parent [–] dreamkeeper@literature.cafe 3 points 2 weeks ago At any minimally competent company they are aware. However my company mostly has former engineers as engineering managers. permalink fedilink source parent
[–] Feyd@programming.dev 9 points 2 weeks ago (3 children) I'm sure there were pockets but it legitimately seemed like that dragon had been slain until recently. Trying to assign more meaning to scrum points has been in vogue for a while though. permalink fedilink source parent hideshow 6 child comments replies: [–] jtrek@startrek.website 6 points 2 weeks ago (1 child) My team assigns both hours and points to tasks. I've never seen the points used for anything but they still spend time on it. permalink fedilink source parent hideshow 2 child comments replies: [–] Kissaki@programming.dev 3 points 2 weeks ago That's... an interesting approach. permalink fedilink source parent [–] dejected_warp_core@lemmy.world 2 points 2 weeks ago That battle is perpetual. Lazy management sees a number that resembles a statistic, and try to use it as an easy metric for stuff it doesn't represent. Points do aggregate into velocity, which is worth measuring. But on their own, points are a proxy for estimation in $SPRINT_LENGTH days. The way to manage up is to keep making it clear that the smallest unit of estimation in Agile is the sprint length; points are used to subdivide that but only to ensure that the sprint itself is not overloaded and thus an accurate estimate. permalink fedilink source parent [–] ripcord@lemmy.world 1 point 2 weeks ago (story points) permalink fedilink source parent
[–] jtrek@startrek.website 6 points 2 weeks ago (1 child) My team assigns both hours and points to tasks. I've never seen the points used for anything but they still spend time on it. permalink fedilink source parent hideshow 2 child comments replies: [–] Kissaki@programming.dev 3 points 2 weeks ago That's... an interesting approach. permalink fedilink source parent
[–] Kissaki@programming.dev 3 points 2 weeks ago That's... an interesting approach. permalink fedilink source parent
[–] dejected_warp_core@lemmy.world 2 points 2 weeks ago That battle is perpetual. Lazy management sees a number that resembles a statistic, and try to use it as an easy metric for stuff it doesn't represent. Points do aggregate into velocity, which is worth measuring. But on their own, points are a proxy for estimation in $SPRINT_LENGTH days. The way to manage up is to keep making it clear that the smallest unit of estimation in Agile is the sprint length; points are used to subdivide that but only to ensure that the sprint itself is not overloaded and thus an accurate estimate. permalink fedilink source parent
[–] dreamkeeper@literature.cafe 3 points 2 weeks ago At any minimally competent company they are aware. However my company mostly has former engineers as engineering managers. permalink fedilink source parent