My team is very inexperienced in how manager our only work and how much time is necessary to spend in some tasks. So many sample things like just develop what our client needs and show it for her (like agile methodology) are transformed into boring and unnecessary meetings which some members try to guess what the customer needs rather than simply delivering a basic version.
We don't have a leader and I don't know exactly how tell "please, stop make so many software requirements specification and let's code that".
Of course is so important know all the software specifications/requirements but we are spend so many time in this steps (the project will be delivered on 2 months), like define all stakeholders and what they impact in project (why? the client just need approve) and I hope they don't want to do class diagram e uml diagram.
How explain for my team "there is no problem if the requirements need to change after a sprint and is normal if some things go wrong in this process, please let's code"?