Comments on: Agile Storytelling http://digitalbrikes.com/onebrikeatatime/2008/07/09/agile-storytelling/ Notes on software development Sat, 04 Feb 2012 01:56:27 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Denis http://digitalbrikes.com/onebrikeatatime/2008/07/09/agile-storytelling/comment-page-1/#comment-406 Denis Mon, 14 Jul 2008 17:19:51 +0000 http://digitalbrikes.com/onebrikeatatime/?p=50#comment-406 The article attempts a description of how to build a good story and what are its characteristics. It is not about the amount of details but mostly about building a shared vision of what the result of the story should be. Also a story is changing until it is called finished by the user. At that point it can disappear into oblivion. Second, I do not think it is only about trust. Trust is always a nice to have whatever the work and the process. It is certainly an important part of agile processes but it is not initially given. Collaborative story writing is an element to build trust but also goes beyond that. Everything that makes the process open and transparent helps building trust. The article attempts a description of how to build a good story and what are its characteristics. It is not about the amount of details but mostly about building a shared vision of what the result of the story should be. Also a story is changing until it is called finished by the user. At that point it can disappear into oblivion.

Second, I do not think it is only about trust. Trust is always a nice to have whatever the work and the process. It is certainly an important part of agile processes but it is not initially given. Collaborative story writing is an element to build trust but also goes beyond that. Everything that makes the process open and transparent helps building trust.

]]> By: Hering Cheng http://digitalbrikes.com/onebrikeatatime/2008/07/09/agile-storytelling/comment-page-1/#comment-405 Hering Cheng Sun, 13 Jul 2008 23:01:26 +0000 http://digitalbrikes.com/onebrikeatatime/?p=50#comment-405 I am not sure what "well-written" actually means here. If it means it contains enough details and specificity for a developer to translate it into code and for QA to verify the resulting behavior in a program, then I am afraid it would remove much of the agility in Agile. In my mind, being Agile should be like how the UNIX system was first developed by Ken Thompson and Dennis Ritchie. I wonder what UNIX would have become (or if it it would even be as popular) if they had needed to keep "well-written" stories as the code was written. If end-users and developers really share the trust and commitment that Agile requires, not having "well-written" stories should not be an issue. This begs the question: Do users and developers ever can have that kind of trust and commitment? I am not sure what “well-written” actually means here. If it means it contains enough details and specificity for a developer to translate it into code and for QA to verify the resulting behavior in a program, then I am afraid it would remove much of the agility in Agile.

In my mind, being Agile should be like how the UNIX system was first developed by Ken Thompson and Dennis Ritchie. I wonder what UNIX would have become (or if it it would even be as popular) if they had needed to keep “well-written” stories as the code was written. If end-users and developers really share the trust and commitment that Agile requires, not having “well-written” stories should not be an issue.

This begs the question: Do users and developers ever can have that kind of trust and commitment?

]]>