Fred is a software jack of all trades, having worked over the last 24 years at every stage of the SDLC and has authored [two books](https://www.amazon.co.uk/Fred-Heath/e/B08F3Q1H1M).
Pretty much agree Ben. We need to know what we're doing and why we're doing, before we decide how to do it. User Stories can help describe and clarify all of the above. But that's all they are: descriptors, properties, attributes. We need to start talking about the whats, whys and hows instead of their attributes.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think we should start with goals and capabilities so everyone knows the purpose of the functionality.
User stories should go into the details and remove the assumptions. clear acceptance criteria
Pretty much agree Ben. We need to know what we're doing and why we're doing, before we decide how to do it. User Stories can help describe and clarify all of the above. But that's all they are: descriptors, properties, attributes. We need to start talking about the whats, whys and hows instead of their attributes.