| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:PracticeDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/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" |
| version="1.0.0"> |
| <mainDescription>The nature of DSDM projects means that low-level requirements are not necessarily fixed when the developers are originally
 |
| approached to carry out the work. Hence the short-term direction that a project takes must be quickly decided without
 |
| recourse to restrictive change control procedures. The stakeholders include not only the business and development staff
 |
| within the project, but also other staff such as Service Delivery or resource managers. 
 |
| <p>
 |
| When development is procured from an external supplier, both the vendor and the purchaser organisations should aim for
 |
| as efficient a process as possible while allowing for flexibility during both the pre-contract phase and when the
 |
| contracted work is carried out.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:PracticeDescription> |
