Productivity and the Workweek (2000)

Re:Productivity and the Workweek (2000) by dtech on Thursday August 22, 2019 @07:52AM (#20767025)

Your planning system is bad. This was the original origin of using story points instead of days, because the designers of extreme programming found that the work of 1 "ideal day" (8 hours of uninterrupted productive coding) could be done in about 3 days.

And don't get me started on measuring velocity, especially across teams. Your environment sounds like its poisoned by middle management.

[ Parent | on HN ]

Re:Productivity and the Workweek (2000) by ChuckNorris89 on Thursday August 22, 2019 @08:00AM (#20767076)

It's not my planning system but it was broken indeed even though they brought in a licensed scrum master as a consultant but he was more interested in running things the way middle managers wanted it as that guaranteed his job security.

Anyway, thank God I left, but from what I hear from other mates in the industry it's not better in other companies in my area since they're all run by middle managers.

Maybe it's a problem specific to Germany where managers are always right and their authority is unquestionable.

[ Parent | on HN ]

Re:Productivity and the Workweek (2000) by majewsky on Thursday August 22, 2019 @11:47AM (#20769386)

That's not specific to Germany. Middle managers are politicians inside a company. Their ultimate goal is almost always to accumulate power.

[ Parent | on HN ]

Re:Productivity and the Workweek (2000) by cassianoleal on Thursday August 22, 2019 @08:00AM (#20767077)

Agree. From the agile manifesto's principles [0]:

> Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

> Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

If either of these requirements are not met, you're not being agile.

[0] https://agilemanifesto.org/principles.html

[ Parent | on HN ]