[creakingstairs]

> I especially find it frustrating that many PMs think that the instant a system goes into production, the project is finished and everyone should be putting tools down and walking away.

This mentality and Agile mixed together creates monster technical debts. A team is rushed to create an MVP. Since it’s an MVP, things are skipped, rushed and riddled with edge cases. This is fine if the team can now use the customer feedback and deeper understanding of the domain to iterate and polish the product. Write some documentation, refactor rough edges etc.

But of course, this often doesn’t happen and the team begins sprinting to deliver on yet another “top priority”. After a while, management starts to wonder why doing anything takes forever and devs are leaving.

[cogman10]

Scrum is so anti-agile it's not even funny. Just TRY to convince a scrum lord that maybe we shouldn't put process before people. It's a treat.

[bazmattaz]

As a PM I feel seen. So many past experiences in companies with poor product culture where this happens. Companies like to say they’re hot on agile and have a strong product culture involving mvp, test, learn, iterate frameworks but in reality so many are just; mvp, test, learn, release, move on to the next different mvp

Leadership often say they want agile processes and iteration but at the end of the day they just want releases of new features

[pif]

> but at the end of the day they just want releases of new features

I do not understand how this reality could surprise any professional developer.

Code quality, clean architecture, elegant algorithms, technical documentation, unit tests... they do not sell. Whatever my process is, if it is not aimed to a constant output of new features and bugfixes, then my process is not good, and I am an idiot to insist on respecting it.