Re: XP & Open Sounce Development share the same roots
> BTW, I think there are some
> mis-characterizations of proprietary
> software development in this piece. For
> example, all commercial software
> development projects in which I have
> been involved have engaged customers
> very early in the development process
> and done alpha and beta releases as soon
> as there's an interesting degree of
> functionality that would make it worth
> the customer's time to use. At my
> current job, we even do things like
> getting customer feedback on UI mockups.
Perhaps I have been guilty of some unwarranted generalization. But hardly, I think, of mis-characterization. For one, the section you quote compares XP with 'conventional' software development methodologies, not 'proprietary' software development (whatever that is). And a comparison of these traditional development methodologies with more agile ones like XP, clears shows that XP offers customers a wider, more influential role in the _entire_ development lifecycle (not just validation, which is plenty much what your examples describe).
Further, if you have developed in scenarios where customers were engaged early and _remained_ engaged throughout, you probably were following some tenets of Agile development techniques in your process
> It's my understanding that these are
> all relatively standard practices.
Again, perhaps. But like I said, the kind of practices you describe were not the kind that particular section was about.