Reply to thread

Message

<blockquote data-quote="Mustrum_Ridcully" data-source="post: 9419821" data-attributes="member: 710">This seems to be a surprisingly common issue, it's a topic for software engineering, too. Customers know wether they like what they got, but getting the description of how it would need to be beforehand can be very hard. Some of the &quot;Agile Development&quot; methodoloy in software development is trying to get the feedback cycles shorter so you can better respond to changing requirements*. So maybe that's why session zero is not working as well as we hope - you need to iterate, because what the playing group thought they liked might actually change based on their experiences. So i guess asking for feedback regularly is a good idea, and being ready to adapt and change your campaign as you go. (Which you can't really do with purchased modules.)*) Maybe the truth is that it isn't really a changing requirement - it's more a discovery process of what was required all long, but we didn't know to describe?</blockquote>

[QUOTE="Mustrum_Ridcully, post: 9419821, member: 710"] This seems to be a surprisingly common issue, it's a topic for software engineering, too. Customers know wether they like what they got, but getting the description of how it would need to be beforehand can be very hard. Some of the "Agile Development" methodoloy in software development is trying to get the feedback cycles shorter so you can better respond to changing requirements*. So maybe that's why session zero is not working as well as we hope - you need to iterate, because what the playing group thought they liked might actually change based on their experiences. So i guess asking for feedback regularly is a good idea, and being ready to adapt and change your campaign as you go. (Which you can't really do with purchased modules.) *) Maybe the truth is that it isn't really a changing requirement - it's more a discovery process of what was required all long, but we didn't know to describe? [/QUOTE]

Verification