Hello!
The comments on this profile are unclaimed and thus are unverified.
Do they belong to you? Claim these comments.
Stewart Rogers
Is this you? Claim Profile »
9 months ago
in What Are Good Requirements? on Write That Down
I agree that Agile user stories, scenarios, requirements are equivalent to waterfall requirements. Fortunately FeaturePlan is aligned with that. ;-) However, I am not sure I agree that Agile features are 1:1 with Agile requirements but I would recommend that is a goal. Too often people starting writing requirements and it is either one line that breaks all requirement writing rules or becomes one big paragraph that breaks rules in the other direction. This is why I am such a big fan of Mike Cohn's user story template. Short, specific and well written. http://blog.mountaingoatsoftware.com/?p=24
1 reply
9 months ago
in Statistics on Write That Down
Statistics can be great... but can also be biased. You always have to question the source behind the provider.
1 reply
Adam Bullied
Yep, for sure. I am starting to lean more and more to running simple,
quick listening labs and meshing that with actual analytics or numbers
to see how things line up.
Problem is, you want the product to mature a bit before diving in to
those activities. Not years, but a couple of months and a solid user
base.
quick listening labs and meshing that with actual analytics or numbers
to see how things line up.
Problem is, you want the product to mature a bit before diving in to
those activities. Not years, but a couple of months and a solid user
base.
the the post was un-clear, but I always think about a feature as a
collection of requirements; not necessarily 1:1. With agile, you can get in
to much trouble that way for the exact reasons you mention.