It’s not always clear what to expect when building software especially when you’re reliant on user stories that don’t describe the full story.
But then again, sometimes user stories can’t be clear without some visual concepts what the users needs.
From experience with visual concepts, many users thought this was it, concrete.
Maybe that’s because it’s down to how polished a design concept is.
Depending what you’re target audience is, it should be very basic to explain itself to the user what each element of a concept does.
Factor in the user’s knowledge of what they may currently know to build the amount of detail needed in the design concept.
We all have to remember that visuals are just concepts, therefore there may be some changes in the pipeline that weren’t considered back then and that they may need looking into present.
Trying a different approach without the visuals is another challenge.
So when you’re building from scratch it only makes sense somewhere along the line where smaller components fit together but still don’t describe what they do.
Adding titles, labels, icons makes sense.
Then you start to see a pattern of inconsistency delivered in Agile methodology, that’s where you’re suppose to constantly deliver.
Sometime it’s better to extend and add a sprint to rectify these issues before it gets complicated to work with.
Yes it adds some time to productivity, but would you rather have this or the latter?