I've now seen this happening in a lot of teams where developers refuse to pick up a user story because there is no detailed wireframe for it.
This was actually my same reaction about 10 years ago, when I did not really understand the MVC architecture and I could not really think about data in isolation.

The fact is that you can start working on the business logic as soon as you know what data needs to be displayed and not how it needs to be displayed.

I'm not saying that wireframes are useless, I'm just trying to encourage developers to think outside the box and not get sucked into graphical details.

I also found that, most of the time, a wireframe or a ui design can influence a developer's choice of datastructures in the business logic layer. This should not happen as, again the UI is just a representation of the data and it should not dictate how the data is stored.

My favourite example is the Clock application.

Say that you need to create an application that displays the time like an analog clock.

If you were to wait for the design, you'll maybe be influenced to store the time in degrees, which will keep track of the angle of each hand of the clock and increase it every minute.
I understand that this is a bit of an extreme example, but I thought it was simple enough to explain the problem here.

From experience I've seen it a lot of time, and I did it myself, and the conseguences can be really painful, as your data is tightly bounded to its graphical representation.

So, the next time you find yourself saying "I cannot start working on this until I see the detailed desing" stop and ask yourself "Do I know what data we need to display?" and if the answer is "yes" then, make an effort and start developing the business layer.

About Author

Simone Vicentini

Simone Vicentini

Creative Agilist, Scrum Master, Tinker, Developer.