blob: c5a9b63e82740d9ba68036ce1478bc807e7f3672 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:RoleDescription 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="-u0-b4PNo9XzOh1-dv_aaKA"
name="StakeHolder,_Qqmp8P_AEdqtbrr0B1TG-A" guid="-u0-b4PNo9XzOh1-dv_aaKA" authors="Claude Aubry"
changeDate="2006-12-03T00:39:26.078-0800" version="1.0.0">
<mainDescription>&lt;p>&#xD;
A stakeholder is not a member of the team, but is interested in the developed product. He can influence the project&#xD;
roll-out. he participates to Scrum meetings: see his contribution to &lt;a class=&quot;elementLink&quot;&#xD;
href=&quot;./../../Scrum/guidances/concepts/Travail%20collaboratif_8AECB83B.html&quot;&#xD;
guid=&quot;_OUjj0AEZEduzRosbOajx7w&quot;>Collaborative work&lt;/a>.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
In Scrum slang, stakeholders are called chickens from which a team of pigs, must be protected from their direct&#xD;
influence on the projet during a sprint. This means that stakeholders have windows to submit their input, strictly&#xD;
defined in order to not disturb the team work.&#xD;
&lt;/p></mainDescription>
<synonyms>&lt;p>&#xD;
Interested party&#xD;
&lt;/p></synonyms>
</org.eclipse.epf.uma:RoleDescription>