Ask HN: What is your agile product development process?
In all my experience, the agile product development process has been pretty much the same. For example, in my latest role, the PM will verbally or in a very short and vague document describe something that we want to build to the Engineering Manager (or to one of the engineers) and then they will gather the engineers to refine the problem by discussing possible solutions and as an outcome we will produce tickets that are ready to be picked up.
While this process has been working fine, we always had the same complaints, a) very vague requirements b) no documentation/history produced during the process and as a result, in a few months we will have forgotten what we've done and why c) communication between engineers and stakeholders is rare and as a result, many times, the stakeholders will receive something else that what they actually needed d) very poorly written tickets description exactly because the communication is poor.
I've been trying to figure out what could be a better approach but because my experience has been the same, I'm not able to sell any alternative to the team/stakeholders. I've reading about user stories and other agile-related solutions but I'm struggling to understand the nitty gritty details of such a process.
What is your current process and if possible, describe it in as much detail as you think someone that has never done it before will understand.
Thank you