I recently psoted the follpwing question to the EPF forum, but received no
response. Would anyone here have an insight ?
Would anyone involved in earlier discussions on creating the content for
the xp and scrum method libraries be able to say why decisions were made
to select only one discipline (scrum_activities) for the scrum method
library and no disciplines for the xp method library? If the answer is
something to the effect that we're like constitutional scholars and the
approach to embedding the method content in the method library is very
formal and the methods do not formally acknowledge disciplines, I
understand. However, I thought tailoring consistent with the intent of the
unified process. If I remember correctly, that would be the role of the
process engineer. Assuming the decisions made as reflected in the current
method libraries, how do the method library authors of the xp and scrum
method libraries intend to represent the juxtaposition of what should be
abstracted disciplines against phases as in the up hump chart which seems
essential to the nature of iterative, incremental methods?
Best wishes,
Rick
office: 202-501-9199
cell: 202-557-1604
_______________________________________________
epf-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/epf-dev
