tag:blogger.com,1999:blog-6005334108330583722.post1126136495452718081..comments2008-07-27T21:57:03.375-04:00Dawnhttp://www.blogger.com/profile/00149191486108175617noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6005334108330583722.post-60326813032973554192008-07-27T21:57:00.000-04:002008-07-27T21:57:00.000-04:00Lisa,<BR/>Thank you for continuing to follow and for suggesting answers to my questions. I really do appreciate your feedback.<BR/><BR/>And of course, I have my own response, and it starts with "But what if ..."?<BR/><BR/>I *feel like* we've done exactly what you have suggested. After all, it makes perfect sense. But what if, the *team* decides on something, and then simply doesn't do it. What if they then agree to Plan B, and then simply don't do it? What if they try Plans C, D, E, F, G, A, A, A, A, A, A, A, and still ... simply don't do it?<BR/><BR/>I suppose this feels like my underlying frustration, and I am not sure how to solve it. I can say that I have said the same thing at every retrospective since, at least, January.dawnhttp://www.blogger.com/profile/08732687146414579552noreply@blogger.comtag:blogger.com,1999:blog-6005334108330583722.post-74931014426202844482008-07-18T15:31:00.000-04:002008-07-18T15:31:00.000-04:00I know you're looking for more than just my idea on it! But can you ask your team this question at your next retrospective? Brainstorm how you might solve this? Let's say you decide to document with test cases on a wiki, or with executable tests wherever they live. Put whatever "start" you come up with on a Big Visible Chart, and talk about it every day in the standup. If the requirements still don't get documented, get the team together and come up with plan B.<BR/><BR/>We're not always great at keeping our requirements up to date, but we do have executable tests, which to me are the ultimate documentation because you can see the results.Lisahttp://www.blogger.com/profile/10230090963033880060noreply@blogger.com