Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
ben657448ystandard PM behaviour in my experience.
Same thing with code documentation, always a back seat to new features. -
same thing everywhere.. on a meeting we were asked why development slowed down during last sprint, so I explained it was because of some critical bugs on production we had to fix urgently. "yeah, but that doesn't mean you don't have to deliver what was planned in the sprint".. I just replied "we're happy to leave the website broken and offline for two weeks until we complete current sprint, but I don't think that's what you want".. didn't get any stupid questions after that
Related Rants
PM asked us to skip the unit test and just deliver untested application to SIT environment due too tight timeline. But when there are defects raised by tested, PM asked why got bugs and asked us to fix them immediately while we have to develop other new features at the same time.
undefined
bad pm
wk9