No diversity and direction, company will jump to do any project from any client the management find, even if we can't deliver. odd projects of differing industries that aren't even our focus. very low attention span, with one big client and attempt to broaden portfolio but failed miserably with projects that hardly last longer than 3 months, while forcing everyone to deliver full product as if it will scale for years to come.
Annual townhall talks about uninspiring focus where basically products that are off-the-shelves planned to be recycle with a local twist that caters to customization, aka client-ask-to-do-this-and-we-will-do-with-no-questions-asked. This is not an innovation driven company, but it's a service company that churns out feature after feature that nobody cares if it serves the purpose or even if people use it, it's the first company I worked where metrics are not important at all, but meeting contract timeline is crucial, regardless if quality or not, as long it passes the smoke test by QA team. Management usually will criticise and sketch issues of team's fault to justify inability to deliver on time, when in actual is that the requirements are not broken down properly because agile is not practiced here anyway.
Development cycle is waterfall method, anti-scrum, but at least everyone uses JIRA so it's agile, endless changes in requirement by product owners that makes slides everyday, then 3 hours sprint walkthrough with two whole departments, then lead will decide how many weeks should the sprint last, then one big-bang deployment usually once every 6 weeks with QA working till the next morning to test on deployment day (no OT).
Using legacy tech-stack that hardly any tech company uses hence limitations on innovating, hence we always ensure the product look like it's from the Y2K era. Main issue would be having to learn old tech stack to work better, react framework will be useful for informational purposes but hardly applied here.
One member could be working on two projects simultaneously of entirely irrelevant product, no objective or goals, so everyone goal is basically to chase timeline, of if you've done your part that stuck with dependency, then you are to act busy until the next sprint starts in about six weeks, hence the flexibility. And if your work contain bug, you will be frowned upon for holding back a deployment that contain six weeks worth of 20+ developers on a single codebase.
But on good notes, if you are on the good books for the management or a relative/friend of a manager even though different dept, you are basically shielded from anything by playing the nepotism card.
