Agile. Specs have no place in our Scrum environment. 1. Stories (and daily discussions with product owners) drive the plan. 2. Stakeholders (and invited customers) approve/criticize/reject the work done every other week, at our reviews -- they don't approve descriptions about what to code, they approve functionality as demonstrated. 3. Testers use their product knowledge to help shape the development decisions throughout the sprint, so they're not passively waiting for direction.
I'm very grateful our days of coding by specs are over. We just jump in and do it, and fix it if we get it wrong. Mary Connor PS: For environments where specifications work, I feel strongly that they belong in a wiki or web CMS (like Drupal) for collaboration, rather than standalone Office documents. Takes a while to wean folks from that. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of siegy adler <snip> I can't think of a good reason not to spec. Can you? ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
