Possibly related to How to communicate technical obstacles?.
In my current position I have found myself in difficulty when it comes to communicating technical difficulties or project management difficulties.
A bit of context: I work in a startup of 15 people, out of which 4 is our development team with me as the oldest one in the project (2 years), but the youngest in terms of age. There are often situations where I am asked to estimate the time of a given task where the difficulty level varies wildly. The code base was built by me over a 1 year period. Because I was the one always in charge of it, it is assumed that somehow I know every single aspect that can go wrong and that changing things is a linear process. Recently, our team grew and now I have the responsibility of managing the new team members as well as partially overseeing our project. For this we decided to use scrum. I have no issue with scrum, I have worked with it before and know my way around it. The COO and CEO however have never worked with it before and they are learning it now. Because of this, we did a half-way implementation of scrum where they decided what features to use or not. The problem is, they decided to remove user stories completely which is a massive mistake in my opinion as it removes a whole layer of validation of our progress.
The problem that I am facing is very often, I am unable to communicate clearly what the problem is. Although I can give clear answers and solutions when prompted too, a lot of the times I am faced with open questions from them such as "Why are user stories important? It's just a phrasing of a functionality." Or "Why does it take so long to change one text field?"
What are some ways to improve my communication to reach out the people that are not so knowledgeable in a topic? A lot of the times I feel that I am met with skepticism because I am relatively young (26 years), which seems to be more important than the fact that I have been working in software development for 5 years.