- daily standups (often one per day per team so multiple per person)
- sprint based development cycles, often with retrospectives
- fondness for the "as an X I want to Y" story
- story points defined in terms of developer hours or days
- Kanban style "pick a thing to work on", even in sprints
- burndown charts
Seems nearly inevitable that when anyone here says "we need more process" they're looking to have more of one or more of the above. I essentially never hear anyone in project management say anything like "we need to build more prototypes" or "we need to streamline our deployment process" or any of the other concepts that would actually characterize a (lower case a) agile development process.
(edited for formatting)
Its popular because managers can implement it. Agile- the manifesto version- was intended as a way to re-introduce the notion of discipline that newer generations of programmers had lost (where previously they were engineers and scientists who wrote code, now people who code exclusively eithout other backgrounds).
It feels like we have come full circle to where the new generations of programmers have delegated (or lost) all discipline to managers' Scrum plannings.
Managers and "product owners" aren't engineers or programmers. They shouldn't be expected to "manage" a developer's day-to-day, and yet them presiding over sit-down-stand-up meetings and demanding points and determining deadlines and features is precisely what it has come to. We are right back where we were when the manifesto was drafted.
User stories? Oh, a neat way to keep requirements general and open-ended so we can properly address how we're actually going to solve a user's problem. Surely it'll prevent PMs from over-specifying requirements that lose sense of true objectives.
2 week Sprints? Cool, estimates are hard, and now I never have to estimate more than 10 business days worth of labor.
Retrospectives? Great idea, we can finally do proper post-mortems and knowledge-sharing!
Scrum Masters? Wonderful, there's someone whose dedicated to running the process and making sure we have everything we need!
What I wasn't anticipating:
User Stories? But what about critical requirements that need to be prioritized that don't fit into "As an X I need Y"
2 Week Sprints? I now have so much technical debt a repo man is confiscating my laptop.
Retrospectives? This is always going to be 100% about how we didn't estimate correctly and not about far more important matters like: how these features didn't help our users, technical knowledge-sharing, and ticking-out technical debt.
Scrum Masters? Oh, you mean Project Managers?
Probject managers and product owners were kept at arms length in the sense that they didn't dictate how, what or when we did what we did. They translated the business requirements and timelines into something we could understand and react to.
Somehow, all of that turned into two week sprints that felt sustainable... At least until the company bought out another company, and everything went downhill. That, however, is a story for another time.
Here's the thing: I have been lucky enough to work with engineer-founders as my bosses for most of my career. You know what the downsides are? None. It's just pure awesome.
It's getting to the point that they're the only people I want to work for.