Visceral Requirements


With a strong developer focus in-house its hard not to head towards technology as a solution; issue tracking software, WIKI’s and online wireframe projects. But gazing at requirements one screen at a time, you can never see the big picture.

When we’re aggregating requirements, and getting ready for a development sprint we pump everything into “the system”; logging issues and priorities, building electronic “paper prototypes”, documenting in our WIKI. But once a project starts, we go visceral, printing out everything and sticking it to the walls.

Bugs, changes, misunderstandings… they’re all hashed out in multi-coloured post-it notes, scribbles on wireframes and scrawls on the idea paint. Making the bits and bytes tangible gets people talking. Development teams need to talk.