Executable Requirements Let You Play More Foosball!

Download

Right click “Save as…”

Slides (view online)
Many teams build software that does not behave as expected by their stakeholders. Teams that build valuable software need more than written specifications to ensure the value of that software. Agile engineering practices add “Executable Requirements” to your specifications arsenal. Writing excellent requirements has been considered a dark art up until now. Eric Landes shares principles of building executable requirements (or acceptance criteria) that deliver value for your customer. Eric shows developers how they can create these "excellent" requirements in difficult situations. These difficult situations include collaborating in different time zones,refining "vague" requirements,and helping product owners use "one voice". He shows Business Analysts collaboration techniques that help BAs write requirements that business and developers can understand. All these techniques can be utilized by Project Managers looking for ways to help increase their teams deliver value when they deliver software.

Follow the Discussion

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.