Re: Practice: Daily Deployment

On May 26, 2005, at 9:39 AM, Adrian Howard wrote:

>
> On 26 May 2005, at 17:07, John Goodsen wrote:
>
>>
>> On May 26, 2005, at 2:21 AM, Adrian Howard wrote:
>>
>>
>>>
>>> On 26 May 2005, at 07:20, Kent Beck wrote:
>>> [snip]
>>>
>>>>  As long as you don't change the user's
>>>> experience of the system, you can deploy all the rest of that work.
>>>> On the
>>>> last day you put the "keystone" in place, the change to the user
>>>> interface.
>>>>
>>> [snip]
>>>
>>> Hmmm... how do you manage that in a way that can get you useful
>>> feedback? If the new UI is the only way to get at new features
>>> they're not going to get tested until the keystone stage. Or am I
>>> missing something?
>>>
>>
>> You can be running acceptance tests against the functionality
>> before you put the keystone in.
>
> Yes - of course. But if the users can't get at the features with the
> UI how does Daily Deployment help?
>
> Ah. Of course. You deploy the acceptance tests to and have a
> mechanism to report their results back to the team. That would make
> sense.

right.  Your getting feedback even before the end user sees the finished
feature.

----
John Goodsen                 RADSoft / Better Software Faster
jgoodsen-Ft5HhTtJyqRBDgjK7y7TUQ@xxxxxxxxxxxxxxxx            Extreme Programmer 
and Coach
http://www.radsoft.com          Enterprise Java and .NET Solutions