You should talk to the customer to understand the problems they have, and work with them to figure out the smallest thing that might help them solve their biggest problem. Build and deliver that small thing fast, then iterate.
It's amusing but sad to see that Agile rent-seekers have managed to creep into the process once again.
And developers have bought it.
Nice but now there isn't anyone to shield us from the insanity and micromanagement of PMs.
Especially the ones who "dabble in programming every weekend".
My current company has been run into the ground because we had a salesperson in charge of product map making wild promises to customers. What they wound up settling on was a PDF report that costs us $5-$20 to make and we sell for $1!!! Utter insanity. We'll be pivoting out of necessity but we could have saved 6 months by putting someone technically competent in the role.
In SW they are the PM's. Without a good PM to shield you from the customers insanities you are lost. In architecture or other engineering professions it's the same. As architect you have a special man to deal with politicians and special clients, and in many other professions even with the press, who has no idea either.
Never talk directly to the customer. Or if so, you are not allowed to make promises.