| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmi:id="-Fi7O_m7ncR5dLB_Mze0L-g" |
| name="new_concept,_63H5cCd-EdymavVWiFnAjw" guid="-Fi7O_m7ncR5dLB_Mze0L-g" changeDate="2007-07-11T09:46:19.750-0400"> |
| <mainDescription><p>
 |
| OpenUP has been heavily influenced by Scrum, Eclipse Way, XP, DSDM, and RUP.
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The Iteration Lifecycle borrows from Scrum’s practices around self organization and leverages Product and Sprint
 |
| Backlogs (represented in OpenUP by Work Items). The Iteration Lifecycle also borrows from the Eclipse Way
 |
| describing how the focus of the team changes as it goes through an iteration.
 |
| </li>
 |
| <li>
 |
| The Micro Increments borrows primarily from RUP in the areas of requirements, architecture and test, and XP for
 |
| guidance on test-driven development, among others.&nbsp;
 |
| </li>
 |
| <li>
 |
| The Project Lifecycle borrows primarily from RUP, with the 4 phases, focus on stakeholder oversight, and the
 |
| balance between risk mitigation and value creation, as well as DSDM for stakeholder involvement.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| OpenUP has also been influenced by many other sources, including many books and individual practitioners, too many to
 |
| be mentioned. It is the objective of the team that develops OpenUP to continually harvest what has been proven to work,
 |
| and what we ourselves have had successes with, to continuously evolve OpenUP.
 |
| </p>
 |
| <p>
 |
| We invite the broader community to contribute to the ongoing evolution of OpenUP.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
