blob: 706b6246f6f3194af560b6a0fa1f87c93cc2490c [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
<!-- VERSION rmc:7.1.0 -->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<!-- START NON-TRANSLATABLE -->
<title>\xp\roles\xp_customer.xmi</title>
</head>
<!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. -->
<body>
Element Name: xp_customer.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,{3C90DD4F-CFDB-4111-922D-3B840B8942DE} CRC: 2406660688 -->XP Customer<!-- END:presentationName,{3C90DD4F-CFDB-4111-922D-3B840B8942DE} -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,{3C90DD4F-CFDB-4111-922D-3B840B8942DE} CRC: 39828424 -->The XP Customer role has the responsibility of defining what is the right product to build, determining the order in which features will be built, and making sure the product actually works.<!-- END:briefDescription,{3C90DD4F-CFDB-4111-922D-3B840B8942DE} -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: mainDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:mainDescription,-92rjXjWhll5LOtPc58YERg CRC: 374212800 --><a id="XE_xp_customer__role_definition" name="XE_xp_customer__role_definition"></a><a id="Description"
name="Description"></a>
<p>
The <a class="PresentationName" guid="{3C90DD4F-CFDB-4111-922D-3B840B8942DE}">XP Customer</a> role has the
responsibility of defining what is the right product to build, determining the order in which features will be built
and making sure the product actually works.
</p>
<p>
The <a class="PresentationName" guid="{3C90DD4F-CFDB-4111-922D-3B840B8942DE}">XP Customer</a> writes system features in
the form of user stories that have business value. Using the planning game, he chooses the order in which the stories
will be done by the development team. He also defines acceptance tests that will be run against the system to prove
that the system is reliable and does what is required.
</p><!-- END:mainDescription,-92rjXjWhll5LOtPc58YERg -->
</body>
</html>