tag:blogger.com,1999:blog-33891833896879217712012-04-15T23:58:40.164-04:00Jesse Stockallhttp://www.blogger.com/profile/09863392964217008070noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-3389183389687921771.post-46073699209930028582008-02-03T19:29:00.000-05:002008-02-03T19:31:48.228-05:00<span style="font-family:verdana;">Just finished reading Mike Cohn's excellent book "<a href="http://www.mountaingoatsoftware.com/book/2">User Stories Applied: For Agile Software Development</a>". The buffalo bit one of the examples Mike uses to illustrate the problems with rigid requirements specifications written at the start of a traditional waterfall project. I've always hated trying to sift through a lengthy requirements document only to find ambiguous language that raises more questions that it answered. Mike explains in great detail how using short user stories that act as a reminder of a conversation can deliver requirements that are easy to understand as well as encouraging communication.</span><br /><p><br /><span style="font-family:verdana;">The start-up I work for is in the process of formalizing our process and Mike's book provides insight and ideas that are helping us to reap the benefits of agile development. Whether you're a development manager, team lead or a developer you'll benefit from Mike's in-depth knowledge and real world experience.</span></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3389183389687921771-4607369920993002858?l=scribblesnscrawls.blogspot.com' alt='' /></div>Jesse Stockallhttp://www.blogger.com/profile/09863392964217008070noreply@blogger.com0