Hacker News Reader

Comment by mindvirus | Hacker News Reader

One pet peeve of mine: people often say they run a "lightweight" version of some project management philosophy and end up paying the costs of it without the benefits. For example lightweight agile scrum meaning sprints, but no retros and work constantly coming into and out of a sprint.

View on HN

I have been on teams like that. It's just biweekly planning meetings. I don't see how that means you pay the full costs of something like Scrum.

Is biweekly twice a week or every two weeks? My previous gig had grooming/internal grooming every week. We had stand ups twice a week (biweekly). Almost all of these meetings were relatively worthless imo. They existed to justify a BA's position and "track velocity".

Every two weeks, in our case. Confusing word, sorry. We had two week "sprints". Every day a 15 minute standup before lunch.

We planned what we were going to do the next two weeks. During that time urgent work would also be added and other things wouldn't be finished, but they just moved to the next sprint. Releases were quarterly (customers didn't like frequent releases) so not related to the "sprints".

Some managers described this as "Scrum light", fine with me.

It depends: when I was hired 12 years ago the manager said "we're going to mix agile and waterfall". What he really meant was that there wasn't any methodology at all and I would be left alone on how to organize myself.

I'm still employed there so I guess my methodology (or lack thereof) isn't that bad ;)

Reply on news.ycombinator.com