Is there an industry standard in communicating requirements to front end developers?

I have a project coming up where I will have annotated wireframes that will have front end dev input and complete designs. I normally work with back end developers and use User Stories as part of a Scrum setup but am unsure whether this is the best way to present these requirements to a front end dev given the nature of the task.


  • 6
    Have you asked your front-end developers how they would like to receive the requirements? Apr 18 '13 at 18:40
  • Of course,some preferred user stories who were use to a Scrum setup where as others preferred annotated wireframes who were less familiar with Scrum. I have asked around and there appears to be no industry standard way of communicating these front end requirements, all dependent on the situation.
    – brakes
    Apr 23 '13 at 19:24

If you're using a Scrum methodology then I think it makes sense to continue using the same approach for both front-end and back-end developers. User stories are a perfectly legitimate and effective way to communicate requirements for both groups. The benefit to you as the project manager is consistency in terms of requirements creation, management and review.

If you are concerned that some deliverables (e.g. annotated wireframes) are non-functional and thus unsuited to user story creation you may find Mike Cohn's article on this subject useful.

Mark Phillips' point is correct though - you definitely need to get the people who will do the work involved in making decisions about how that work is defined.

  • 3
    If you're using a Scrum methodology then ideally your back-end and front-end developers are on the same team anyway...
    – Lunivore
    Apr 19 '13 at 10:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.