Download this episode
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.
Available formats for this video:
Actual format may change based on video formats available and browser capability.
Event HomepageTech·Ed North America 2011
More episodes in this series
Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.