[magicalhippo]

We don't do scrum. We release major versions once a month, and bugfixes daily. New features go into the next major version when done, bugfixes gets released as soon as they're done.

We use Kanban boards to get an overview and prioritize work. Apart from that devs mostly manage their own work.

We're a small shop though, perhaps that's why it works well.

[oneshtein]

Looks like SCRUM.

[magicalhippo]

But is it? Everything is the same if you squint hard enough.

We do not have anything like a SCRUM master.

We don't do stand-ups, we usually don't have a per-release target for features. For example, for the past three months I've had a target of October 1st for a feature, but no specific sub-deliverables for the realeases before that. This is typical.

We don't have a separate sprint retrospective meeting. We discuss such things during our weekly meeting, even between releases (ie we don't wait).

It doesn't feel like what I've been taught and have read about SCRUM. But sure I'll agree it's closer to SCRUM than to the waterfall method.

[oneshtein]

Yep, it's typical Agile.

Scrum masters are needed to coach a new team with inexperienced project manager only. Established teams don't need them.

Stand-ups can be easily replaced by a team chat, such as Slack, with even better results.

I saw very few retrospective meetings too. If everything goes smoothly, then retrospective meetings are useless.