blob: 9d15cac69abfdb4978bfdc78ac7dfd19bc9a320c [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\tasks\develop_xp_vision.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: develop_xp_vision.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,{A8708FFB-BB20-40AF-BEF2-7A8A814FF74D} CRC: 2887983663 -->Define Vision<!-- END:presentationName,{A8708FFB-BB20-40AF-BEF2-7A8A814FF74D} -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: purpose<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:purpose,-W67fNE0rT1c2PM-20yXbrw CRC: 3266563031 --><a id="XE_define_vision__activity_definition" name="XE_define_vision__activity_definition"></a>
<ul>
<li>
The Vision defines the stakeholder's view of the product being developed specified in terms of the stakeholder's
key needs and features.
</li>
</ul><!-- END:purpose,-W67fNE0rT1c2PM-20yXbrw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_oB58MGE-EdqnIZeW8YpHcA CRC: 3076507154 -->Gain Agreement on the Problem Being Solved <!-- END:name,_oB58MGE-EdqnIZeW8YpHcA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_oB58MGE-EdqnIZeW8YpHcA CRC: 2696114523 --><a id="Gain" name="Step1"></a>
<p>
One of the simplest ways to gain agreement on the definition of the problem is to write it down and see if everyone
agrees.
</p>
<p>
Ask the group: What is the problem?
</p>
<p>
It is very common to rush headlong into defining the solution rather than taking time to first understand the problem.
Write down the problem and see if you can get everyone to agree on the definition.
</p>
<p>
Then ask the group again: What is the problem, really?
</p>
<p>
Search for root causes or the "problem behind the problem". The real problem is often hiding behind what is perceived
as a problem. Don't accept the first statement of a problem. Continue to ask "why?" to find out what the problem
"really" is. Sometimes the group can be so focused on an envisioned solution that it is hard to get them to formulate
the underlying problem. In such cases, it can be beneficial to explore the benefits of the solution and then try to
find the problems being solved by those benefits. You can then explore whether or not those problems are "real"
problems in the organization.
</p><!-- END:sectionDescription,_oB58MGE-EdqnIZeW8YpHcA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_oB58MWE-EdqnIZeW8YpHcA CRC: 1972005572 -->Identify Stakeholders <!-- END:name,_oB58MWE-EdqnIZeW8YpHcA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_oB58MWE-EdqnIZeW8YpHcA CRC: 3081152004 --><a id="Identify" name="Step2"></a>
<ul>
<li>
Who are the users of the system?
</li>
<li>
Who is the economic buyer for the system?
</li>
<li>
Who else will be affected by the output that the system produces?
</li>
<li>
Who will evaluate and bless the system when it is delivered and deployed?
</li>
<li>
Are there any other internal or external users of the system whose needs must be addressed?
</li>
<li>
Who will maintain the new system?
</li>
<li>
Is there anyone else?
</li>
<li>
Okay, is there anyone else?
</li>
</ul><!-- END:sectionDescription,_oB58MWE-EdqnIZeW8YpHcA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_oB58MmE-EdqnIZeW8YpHcA CRC: 1550591641 -->Define the Primary Features of the System <!-- END:name,_oB58MmE-EdqnIZeW8YpHcA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_oB58MmE-EdqnIZeW8YpHcA CRC: 1655924198 --><a id="Define" name="Step3"></a>
<p>
What primary features of the system allow the stakeholders to solve their problems? This should be a list of very
high-level features.<br />
</p><!-- END:sectionDescription,_oB58MmE-EdqnIZeW8YpHcA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_oB58M2E-EdqnIZeW8YpHcA CRC: 59390185 -->Communicate the Vision <!-- END:name,_oB58M2E-EdqnIZeW8YpHcA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_oB58M2E-EdqnIZeW8YpHcA CRC: 531123922 --><a id="Com" name="Step4"></a>
<p>
Once agreed upon by the stakeholders, the vision is communicated clearly to all project team members. When the project
starts, XP teams often write up the vision on one of the whiteboards in the team's open workspace so it can easily be
seen by all team members. After a short time, the team usually internalizes the vision and no longer needs the
reminder.
</p><!-- END:sectionDescription,_oB58M2E-EdqnIZeW8YpHcA -->
</body>
</html>