How do you plan sprints and epic at your company?

How do you guys approach to completing your tasks which are adjusted to be completed in 40 hours (or whatever amount of time is standard in your company) when 25% of the time goes in meetings and calls only?

So generally in my team, if a person completes his/her set of sprint tasks, he's using burdened with more tickets with an expectation to complete within the sprint itself. Wanted to know more about the culture from you guys. Once you are done with your sprint tasks do you get a short breather or do you sort of delay closing your tickets to avoid getting overburdened with newer things to do.

1. Who decides the deadlines for tasks? Are you responsible for scoping the task or does a senior do it for you? 2. How often do newer, more urgent tasks come in when you are working on your planned task? Does the deadline for the planned task move in such cases? 3. Do you often have to work long hours and over the weekends to meet the deadlines? How often do you think that the deadlines are unreasonable?

While I 100% agree that a PM at a company like Juspay that sells technical products needs to have good technical proficiency to the extent of understanding code as well, why are there no EMs? In a company that's as engineering driven as Juspay, it is all the more important to have EMs who bring in valuable 8+ years of industry experience and have the know how of guiding engineers on building reliable scalable systems and logic. I learnt that Juspay expects PMs to do it all. Questions to Juspay PMs : Do you conduct sprint planning meetings? Are you responsible for the Engg team's performance metrics like sprint deliverance ratio, production issues caused, bugs raised, etc. ? What's the importance and significance given to hardcore product work like doing quality product discoveries ? Do you do code reviews? Are you responsible for Engg downtimes? Given that you are donning multiple hats and doing more than one person's work, what's your WLB like? A good way to measure this is how much time do you get to pursue your personal hobbies, say like hitting the gym, on a daily basis ?

I’m curious about the working style of difterent companies operating at different levels. Do engineers ever directly talk to business or just product? Does the product give a detailed PRD covering all possible scenarios or a one pager? Are PRDs still a thing ? How long does the review cycle last? How strictly are estimates adhered to? How frequently do the requirements change during the dev cycle? Who owns the quality of outcome ?

This question is more focused toward startups. A single developer single handedly built entire backend over the two years and poorly documented everything during the process. Now he has left the company and there's so much chaos while working with APIs. My work mainly involves UI integration and hence I struggle a lot to do basic work. Sometimes I end up spending hours debugging and end up realizing this parameter expects a differ type of value than I was sending. Recently I got frustrated so much and decided to clean up everything and write well structured documentation. I want to know how other companies manage this. - What tools and services do you use? - When do you do it? How do you do it? Do you maintain it often? - Is there any guide/reference/open source project that I can refer to get better understanding of the whole process? Any additional help appreciated.

Started working in a new org two months back as a PM. while discussing new requirememts with the tech I am always affraid that whatever I am saying is correct or not. As I am not familiar with all the systems. Sometimes during sprint planning tech will tell me or my manager would say you missed this scenario or this functionality works like this so we may have some issue in approach you are taking. I feel like everyone is judging me if I am making any mistake. No idea how to overcome this , pretty low on confidence now a days and keep on thinking am I good enough ?