> /Do you have suggestions or ressources for an easy-to-apply-workflow for
> establishing requirements and goals?/
I don't have a workflow, per se, but I have a rule I like to share.
It's called the "Rocket-Propelled Hamster" rule, or RPH as my current
boss likes to call it.
The story goes like this: Once upon a previous job I was working with
the business team on a requirements document and came across the
'requirement' that "The system should index all saved emails." My
response was that this sentence didn't belong in a requirements(*)
document.
"Why not?" asked the product
