I am afraid you are wrong. Requirement analysis is step #0 in the SDLC. You are failing to capture non functional requirements and moving a technical discussion

I am afraid you are wrong. Requirement analysis is step #0 in the SDLC. You are failing to capture non functional requirements and moving a technical discussion to a interpersonal level. Until you understand that you will be stuck. In this thread for example. I have proposed different rational courses of action that you dismissed without providing a reason. This communicational style will certainly bring you issues at the time of capturing requirements for your deliverables. Ignoring requirements from technical stakeholders will only reinforce the idea that you need more feedback and more mentoring, or that you just need to be let go.