Working in a service based company in a project with dumb fcking manager/lead who can't plan proper workflow and design, where backend and frontend work on the same feature simultaneously and u get API's in the end of the Sprint and it has be integrated, tested and deployed in the same day...and the manager is a fcking virgin and starts drooling with backend team as they are most females and is very lenient towards them

What kind of company has sprints and separate teams for backend and frontend ????

If they want to be agile (sprints indicate that they're pretending to be) then 1 team should be capable of delivering the whole story. (If a PHB is splitting a story into tasks and assigning tasks to teams or individuals then you're still in waterfall territory.

Normal agile workflow:

1) Story: as a retarded user i want a simple way to get X information because of Y

2) Team responsible checks if getting info X is the best/easiest/only way for users to deal with Y

3) Team decides on what they can build in a few weeks

3.5) PHB ensures the team stays sufficiently caffienated

4) Team builds, tests, and deploys whatever it was they decided on.

5) Evaluate, iterate or move on.

If the Team doesn't have all the (non tech) skills required then you pull in someone with those skills (even if its just to join standups and sit nearby to answer questions and provide feedback)

Oof, my condolences, it's beyond corporate cringe

@ItsNotMyFault the company is a fcking joke, even after raising multiple concerns on how the project is being handled...nothing has changed. So I did what I could. Resigned.
The cruel part is I've to serve 3 months notice period :(

Sounds like you work for the same fucking idiot I work for.

@ItsNotMyFault
Few companies have the "you build it, you run it," mentality, unfortunately. Plenty of asshats still baked into 90s architecures where there's a "service team," and a front "front end team," alongside a way team, deployment team, and ops team. And then when your code is done they hand it to an "AM" team that couldn't code their way out of a paper bag.

The tell is usually the stack being topped by an everything architect would couldn't lay down a line of code to save his life and wouldn't know the boundary between enterprise and software architecture if it kicked him in the face.

@rajeshzmoke Have been in the same situation 2 years back. Worked in one of the top service firms. Couldn't continue as it was frustrating. Luckily 1 year back got offer from a US Product based MNC. It's not perfect but still much much better. Never going to try for service companies ever. Wish you all the best for your next endeavor.