36954Re: A tale of two Scrums
- Mar 7, 2009--- In email@example.com, "jens.meydam" <jens.meydam@...> wrote:
>This seems to imply that Scrum and XP are the same. I'm pretty new to Scrum and agile so I'm hoping to improve my understanding. My understanding of Scrum is it's a way to manage agile software development and a wrapper for the engineering practices. XP represents the engineering practices that seem to align best with Scrum but are not prescribed by Scrum.
> Hi Adam
> I appreciate your detailed comments concerning the usage of the term "spike" and the history of the adoption of fine-grained user stories as the preferred way to specify requirements. (Mike Cohn probably deserves some credit for the latter.)
> Let me just add that my association of certain practices (like specification of soon-to-be developed requirements in form of small, well understood user stories) with XP may stem from my observation that people close to XP seem to feel particularly strongly about these practices.
> What I still wonder, though, is whether we are really heading towards a kind of "Unified Agile Method" combining the best of Scrum, XP, Chrystal, ... - or whether these approaches to software development and creative work are not really to some extent incompatible.
> I have the impression that - depending on the style of Scrum - doing Scrum and doing XP can feel very different.
- << Previous post in topic Next post in topic >>