I have worked recently on a project that used the Scrum methodology applied to UX, and it didn't work quite well. I think that the reasons behind it was that the backlog wasn't properly laid out. I would also advise you not to mix early stages of UX development with implementation as it will really mess things up.
A pretty good Agile "Scrum" method diagram can be found here: http://www.softhouse.se/Uploades/scrum-diagram.gif All in all I learned a few "Agile" valuable lessons: - Doing a backlog with chunks of work (achievable in "sprints" of 1 or 2 weeks) is a really great way of thinking ahead of what you can do and how long it will take you. - Daily "scrum meetings" are a really good way to give you focus for the day ahead while at the same time giving you some insight on what other team members are doing and how you can work with them. - Pushing deliverables out at the end of the sprint is a good way to force you to have something "real" at the end of it. Alas, no development methodology is perfect, but if you embrace it properly it helps out a lot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=28227 ________________________________________________________________ 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
