blob: f932acfb9e8d0616aa12de1e78dee046d4039ae3 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:PracticeDescription xmi:version="2.0"
xmlns:xmi="" xmlns:org.eclipse.epf.uma=""
xmlns:epf="" epf:version="1.5.0" xmi:id="-EkjHzEXlvX4rzNg-YobaIg"
name="new_practice,_SLydAFleEdul8L-IGeA7TA" guid="-EkjHzEXlvX4rzNg-YobaIg" changeDate="2006-10-11T13:26:09.250-0700"
<mainDescription>The nature of DSDM projects means that low-level requirements are not necessarily fixed when the developers are originally&#xD;
approached to carry out the work. Hence the short-term direction that a project takes must be quickly decided without&#xD;
recourse to restrictive change control procedures. The stakeholders include not only the business and development staff&#xD;
within the project, but also other staff such as Service Delivery or resource managers. &#xD;
When development is procured from an external supplier, both the vendor and the purchaser organisations should aim for&#xD;
as efficient a process as possible while allowing for flexibility during both the pre-contract phase and when the&#xD;
contracted work is carried out.&#xD;