How to write requirements that Engineers can understand

This is a really easy to get started guide on how to better write requirements that engineers can understand

How to write requirements that Engineers can understand
  • ✅ This is a really easy to get started guide on how to better write requirements that engineers can understand
  • ✅ For people who are just getting started or new to writing requirements
  • ❌ This is not a comprehensive document on this topic. There is a whole school of thought in Agile around how to write user stories

In short,

  1. Describe the expected behaviour (users can send a message)
  2. Describe the technical constraints or business rules (e.g. should only trigger when a user fails their payment or for admin users only)
  3. Use a consistent format with your development team

Write excellent requirements that give our software developers the right amount of context and detail to build amazing software

User Stories

The most popular standard of writing requirements in modern companies is called, writing User Stories. It typically involves understanding the end-user that you are building or designing for.

NB: A user is not the same as a customer.

  • Users are the people who interact with your product/service usually through media or technology
  • Customers are the people who pay

💡Give users a great user experience that requires no directions or learning curves. Understand who is making the decision to buy your product to inform your marketing and sales efforts

How to write a user story

Photo Credit: visual-paradigm.com

Further reading

  1. User Stories applied by Mike Cohn
  2. INVEST in great users stories by Bob Hartman
  3. User Stories: Bin, Thin or Split? by Adrian Howard