I have expressed my doubts about how often the business sees a feature file in one of previous posts How often Customers see your Features?
. Not knowing enough of why the customers are not motivated enough to look at the feature files I started looking at whats my role in it?
As a developer I influence the style of feature files a lot (we typically outnumber other roles in projects and our collective decibel levels seems to work ;) ) and the good practices from the programming world creeps into feature files. One such thing is DRY(Dont Repeat Yourself) and manifests as step reuse in Feature files.An example explains this better.
Anyone would want to reuse the above step irrespective of the actual value of the shipping charge.
That seems quite right too.
How about when the shipping charge is 0(zero)?
That is technically correct, may work and also conforms to DRY, I am happy with my developer hat on.
But I just missed the most important thing, the word FREE. And with that my ability to communicate effectively with the business.
What other patterns affects the customer motivation to see the Feature Files as a collaboration aid?
No comments:
Post a Comment