One of the platitudes of the agile community is trust. Asking to be trusted, asking to be allowed to self-organize and spend other people's money in the development of value. Many times asking to not be asked for an estimate, or to show progress to plan, or to not be held to a deadline, or to report on when they'll be done.
Trust Requires a Track Record
So before trust can be achieved, performance to plan is needed. You've done this before, showed up when needed, at the needed cost, with the needed Features. That's the source of trust in the software development business.
Asking for trust before verification that you can be trusted isn't going to get you very far with those paying for your services.
Here's an excerpt from a book I recommend Project Management the Agile Way: Making It Work in the Enterprise, John Goodpasture.
Trust is believing that others will act not only in their interests but also in yours. It requires an exchange of power, and power exchange is only enabled by honesty, openness, and a track record of dependability and accountability. "Trust lies at the heart of a functioning, cohesive team. Without it, teamwork is all but impossible, writes Patrick Lencioni
