Contribution 6 - Revision history

Contribution 6 - Revision history http://commons.oreilly.com/wiki/index.php?title=Contribution_6&action=history Revision history for this page on the wiki en MediaWiki 1.11.0 Thu, 23 May 2013 08:41:25 GMT Rmonson at 17:28, 2 July 2008 http://commons.oreilly.com/wiki/index.php?title=Contribution_6&diff=11311&oldid=prev <p></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 17:28, 2 July 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Always ask for the value to be provided by a requested capability. ==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Always ask for the value to be provided by a requested capability. ==</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div><del style="color: red; font-weight: bold; text-decoration: none;">Very often </del>customers and end-users state what they think is a viable solution <del style="color: red; font-weight: bold; text-decoration: none;">on </del>a problem as a requirement. The classical story on this was told by Harry Hillaker, the lead designer of the F-16 Falcon. His team was requested to design a Mac 2 - 2.5 aircraft, which was then, and probably still is, a non trivial task to do. At least when the aim is a "cheap" lightweight aircraft. Remember that the force required to overcome drag quadruples when doubling the speed, and what impact that have on aircraft weight.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">Often </ins>customers and end-users state what they think is a viable solution <ins style="color: red; font-weight: bold; text-decoration: none;">to </ins>a problem as a requirement. The classical story on this was told by Harry Hillaker, the lead designer of the F-16 Falcon. His team was requested to design a Mac 2 - 2.5 aircraft, which was then, and probably still is, a non trivial task to do. At least when the aim is a "cheap" lightweight aircraft. Remember that the force required to overcome drag quadruples when doubling the speed, and what impact that have on aircraft weight.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>When the design team asked the air force why they needed Mac 2 - 2.5, the answer was to be able to escape from combat. With the real need on the table the design team was able to address the root problem and provide a working solution. Their solution was an agile aircraft with an high thrust-weight ratio, providing acceleration and maneuverability, not maximum speed.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>When the design team asked the air force why they needed Mac 2 - 2.5, the answer was to be able to escape from combat. With the real need on the table the design team was able to address the root problem and provide a working solution. Their solution was an agile aircraft with an high thrust-weight ratio, providing acceleration and maneuverability, not maximum speed.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>This lesson should be brought into software development as well. By asking for the value to be provided by a requested feature or requirement. By understanding the value the designers are able address the real problem, and hopefully provide a better and <del style="color: red; font-weight: bold; text-decoration: none;">hopefully </del>cheaper solution compared to addressing the stated need in a head-on approach. <del style="color: red; font-weight: bold; text-decoration: none;">By understanding </del>the value behind a requirement makes prioritizing simpler, as a value can be quantified and ranked. The most valued requirements become the driving requirements.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>This lesson should be brought into software development as well. By asking for the value to be provided by a requested feature or requirement. By understanding the value the designers are able address the real problem, and hopefully provide a better and cheaper solution compared to addressing the stated need in a head-on approach. <ins style="color: red; font-weight: bold; text-decoration: none;">Understanding </ins>the value behind a requirement makes prioritizing simpler, as a value can be quantified and ranked. The most valued requirements become the driving requirements.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>So, how to proceed then? </div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>So, how to proceed then? </div></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>There is probably only one way, arrange workshops and meetings with the customer. The architects focus in such session </div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>There is probably only one way, arrange workshops and meetings with the customer. The architects focus in such session should be on understanding customer needs, including helping the customer to answer the question <ins style="color: red; font-weight: bold; text-decoration: none;">"</ins>why<ins style="color: red; font-weight: bold; text-decoration: none;">"</ins>. Be aware that answering the <ins style="color: red; font-weight: bold; text-decoration: none;">"</ins>why<ins style="color: red; font-weight: bold; text-decoration: none;">" </ins>question can be difficult because we very often talk about tacit knowledge. Discussions on how to provide a technical solution should be avoided in these workshops, because they move the discussions away from the customers domain and into the domain of software development.</div></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>should be on understanding customer needs, including helping the customer to answer the question why. Be aware that answering the why question can be difficult because we very often talk about tacit knowledge. Discussions on how to provide a technical solution should be avoided in these workshops, because they move the discussions away from the customers domain and into the domain of software development.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div></div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>The list of ranked capabilities should be brought back to office and assessed with respect to technical feasibility, and the impacts of the assessment should be discussed with the customer. For a large system such assessment involves development of prototypes or demonstrators.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>The list of ranked capabilities should be brought back to office and assessed with respect to technical feasibility, and the impacts of the assessment should be discussed with the customer. For a large system such assessment involves development of prototypes or demonstrators.</div></td></tr>  </table> Wed, 02 Jul 2008 17:28:44 GMT Rmonson http://commons.oreilly.com/wiki/index.php/Talk:Contribution_6 Elandre: /* Always ask for the value to be provided by a requested capability. */ http://commons.oreilly.com/wiki/index.php?title=Contribution_6&diff=11032&oldid=prev <p><span class="autocomment">Always ask for the value to be provided by a requested capability.</span></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 19:13, 29 May 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Always ask for the value to be provided by a requested capability. ==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Always ask for the value to be provided by a requested capability. ==</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>Very often customers and end-users state what they think is a viable solution on a problem as a requirement. The classical story on this was <del style="color: red; font-weight: bold; text-decoration: none;">first </del>told by Harry Hillaker, the lead designer of the F-16 Falcon. His team was requested to design a Mac 2 - 2.5 aircraft, which was then, and probably still is, a non trivial task to do. At least when the aim is a "cheap" lightweight aircraft. Remember that the force required to overcome drag quadruples when doubling the speed.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>Very often customers and end-users state what they think is a viable solution on a problem as a requirement. The classical story on this was told by Harry Hillaker, the lead designer of the F-16 Falcon. His team was requested to design a Mac 2 - 2.5 aircraft, which was then, and probably still is, a non trivial task to do. At least when the aim is a "cheap" lightweight aircraft. Remember that the force required to overcome drag quadruples when doubling the speed<ins style="color: red; font-weight: bold; text-decoration: none;">, and what impact that have on aircraft weight</ins>.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>When the design team asked the air force why they needed Mac 2 - 2.5, the answer was to be able to escape from combat. With the real need on the table the design team was able to address the problem and provide a working solution. Their solution was an agile aircraft with an high thrust-weight ratio, providing acceleration, not maximum speed.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>When the design team asked the air force why they needed Mac 2 - 2.5, the answer was to be able to escape from combat. With the real need on the table the design team was able to address the <ins style="color: red; font-weight: bold; text-decoration: none;">root </ins>problem and provide a working solution. Their solution was an agile aircraft with an high thrust-weight ratio, providing acceleration <ins style="color: red; font-weight: bold; text-decoration: none;">and maneuverability</ins>, not maximum speed.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>This lesson should be brought into software development as well. By asking for the value to be provided by a requested feature or requirement. By understanding the value <del style="color: red; font-weight: bold; text-decoration: none;">and real need </del>the designers are able address the real problem, and hopefully <del style="color: red; font-weight: bold; text-decoration: none;">in the end </del>provide a better and cheaper solution compared to addressing the stated need in a head-on approach. By understanding the value behind a <del style="color: red; font-weight: bold; text-decoration: none;">requirements also </del>makes prioritizing simpler, as a value can be quantified and ranked.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>This lesson should be brought into software development as well. By asking for the value to be provided by a requested feature or requirement. By understanding the value the designers are able address the real problem, and hopefully provide a better and <ins style="color: red; font-weight: bold; text-decoration: none;">hopefully </ins>cheaper solution compared to addressing the stated need in a head-on approach. By understanding the value behind a <ins style="color: red; font-weight: bold; text-decoration: none;">requirement </ins>makes prioritizing simpler, as a value can be quantified and ranked<ins style="color: red; font-weight: bold; text-decoration: none;">. The most valued requirements become the driving requirements</ins>.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>So, how to proceed then? </div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>So, how to proceed then? </div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>There is probably only one way, arrange workshops and meetings with the customer. The architects focus in such session </div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>There is probably only one way, arrange workshops and meetings with the customer. The architects focus in such session </div></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>should be on understanding customer needs, including helping the customer to answer the question why. Be aware that answering the why question can be difficult because we very often talk about tacit knowledge. Discussions on how to provide a technical solution should be avoided. </div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>should be on understanding customer needs, including helping the customer to answer the question why. Be aware that answering the why question can be difficult because we very often talk about tacit knowledge. Discussions on how to provide a technical solution should be avoided <ins style="color: red; font-weight: bold; text-decoration: none;">in these workshops, because they move the discussions away from the customers domain and into the domain of software development</ins>.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>The list of ranked capabilities should be brought back to office and assessed with respect to technical feasibility, and the impacts of the assessment should be discussed with the customer. For a large system such assessment involves development of prototypes or demonstrators.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>The list of ranked capabilities should be brought back to office and assessed with respect to technical feasibility, and the impacts of the assessment should be discussed with the customer. For a large system such assessment involves development of prototypes or demonstrators.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>With respect to development process, it should be fairly easy to see that this approach is best served by some sort of iterative process. That said, capabilities should be ranked as part of the initial product planning, helping <del style="color: red; font-weight: bold; text-decoration: none;">us </del>to maximize customer value as early as practical possible. <del style="color: red; font-weight: bold; text-decoration: none;">It should also be part of </del>the iteration <del style="color: red; font-weight: bold; text-decoration: none;">planning</del>, making sure that the value is sustained when requirements are further detailed. </div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>With respect to development process, it should be fairly easy to see that this approach is best served by some sort of iterative process. That said, capabilities should be ranked as part of the initial product planning, helping <ins style="color: red; font-weight: bold; text-decoration: none;">both customers and developers </ins>to maximize customer value as early as practical possible. <ins style="color: red; font-weight: bold; text-decoration: none;">At </ins>the <ins style="color: red; font-weight: bold; text-decoration: none;">beginning of each </ins>iteration <ins style="color: red; font-weight: bold; text-decoration: none;">should be assessed and ranked</ins>, making sure that the value is sustained when requirements are further detailed. </div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>  </table> Thu, 29 May 2008 19:13:55 GMT Elandre http://commons.oreilly.com/wiki/index.php/Talk:Contribution_6 Elandre: /* Always ask for the value to be provided by a requested capability. */ http://commons.oreilly.com/wiki/index.php?title=Contribution_6&diff=10872&oldid=prev <p><span class="autocomment">Always ask for the value to be provided by a requested capability.</span></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 13:44, 16 May 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Always ask for the value to be provided by a requested capability. ==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Always ask for the value to be provided by a requested capability. ==</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>Very often customers and end-users state what they think is a viable solution on a problem as a requirement. The classical story on this was first told by Harry Hillaker, the lead designer of the F-16 Falcon. His team was requested to design a Mac 2 - 2.5 aircraft, which was then, and probably still is, a non trivial task to do. At least when the aim is a "cheap" lightweight aircraft. </div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>Very often customers and end-users state what they think is a viable solution on a problem as a requirement. The classical story on this was first told by Harry Hillaker, the lead designer of the F-16 Falcon. His team was requested to design a Mac 2 - 2.5 aircraft, which was then, and probably still is, a non trivial task to do. At least when the aim is a "cheap" lightweight aircraft<ins style="color: red; font-weight: bold; text-decoration: none;">. Remember that the force required to overcome drag quadruples when doubling the speed</ins>.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>When the design team asked the air force why they needed Mac 2 - 2.5, the answer was to be able to escape from combat. With the real need on the table the design team was able to address the problem and provide a working solution. Their solution was an agile aircraft with an high thrust-weight ratio, providing acceleration, not maximum speed.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>When the design team asked the air force why they needed Mac 2 - 2.5, the answer was to be able to escape from combat. With the real need on the table the design team was able to address the problem and provide a working solution. Their solution was an agile aircraft with an high thrust-weight ratio, providing acceleration, not maximum speed.</div></td></tr>  </table> Fri, 16 May 2008 13:44:29 GMT Elandre http://commons.oreilly.com/wiki/index.php/Talk:Contribution_6 Elandre: /* Always ask for the value to be provided by a requested capability. */ http://commons.oreilly.com/wiki/index.php?title=Contribution_6&diff=10869&oldid=prev <p><span class="autocomment">Always ask for the value to be provided by a requested capability.</span></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 07:15, 16 May 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 13:</td> <td colspan="2" class="diff-lineno">Line 13:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>The list of ranked capabilities should be brought back to office and assessed with respect to technical feasibility, and the impacts of the assessment should be discussed with the customer. For a large system such assessment involves development of prototypes or demonstrators.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>The list of ranked capabilities should be brought back to office and assessed with respect to technical feasibility, and the impacts of the assessment should be discussed with the customer. For a large system such assessment involves development of prototypes or demonstrators.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>With respect to development process, it should be fairly easy to see that this approach is best served by some sort of iterative process. That said, capabilities should be ranked as part of the initial product planning, helping us to maximize value <del style="color: red; font-weight: bold; text-decoration: none;">for the customers </del>as early as practical possible. It should also be part of the iteration planning, making sure that the value is sustained when requirements are further detailed. </div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>With respect to development process, it should be fairly easy to see that this approach is best served by some sort of iterative process. That said, capabilities should be ranked as part of the initial product planning, helping us to maximize <ins style="color: red; font-weight: bold; text-decoration: none;">customer </ins>value as early as practical possible. It should also be part of the iteration planning, making sure that the value is sustained when requirements are further detailed. </div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>  </table> Fri, 16 May 2008 07:15:39 GMT Elandre http://commons.oreilly.com/wiki/index.php/Talk:Contribution_6 Elandre: /* Always ask for the value to be provided by a requested capability. */ http://commons.oreilly.com/wiki/index.php?title=Contribution_6&diff=10868&oldid=prev <p><span class="autocomment">Always ask for the value to be provided by a requested capability.</span></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 07:13, 16 May 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 9:</td> <td colspan="2" class="diff-lineno">Line 9:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>So, how to proceed then? </div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>So, how to proceed then? </div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>There is probably only one way, arrange workshops and meetings with the customer. The architects focus in such session </div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>There is probably only one way, arrange workshops and meetings with the customer. The architects focus in such session </div></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>should be on understanding customer needs, including helping the customer to answer the question why. Be aware that answering the why question can be difficult because we talk about tacit knowledge. Discussions on how to provide a technical solution should be avoided. </div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>should be on understanding customer needs, including helping the customer to answer the question why. Be aware that answering the why question can be difficult because we <ins style="color: red; font-weight: bold; text-decoration: none;">very often </ins>talk about tacit knowledge. Discussions on how to provide a technical solution should be avoided. </div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>The list of ranked capabilities should be brought back to office and assessed with respect to technical feasibility, and the impacts of the assessment should be discussed with the customer. For a large system such assessment involves development of prototypes or demonstrators.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>The list of ranked capabilities should be brought back to office and assessed with respect to technical feasibility, and the impacts of the assessment should be discussed with the customer. For a large system such assessment involves development of prototypes or demonstrators.</div></td></tr>  </table> Fri, 16 May 2008 07:13:33 GMT Elandre http://commons.oreilly.com/wiki/index.php/Talk:Contribution_6 Elandre: /* Always ask for the value to be provided by a requested capability. */ http://commons.oreilly.com/wiki/index.php?title=Contribution_6&diff=10867&oldid=prev <p><span class="autocomment">Always ask for the value to be provided by a requested capability.</span></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 07:12, 16 May 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 5:</td> <td colspan="2" class="diff-lineno">Line 5:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>When the design team asked the air force why they needed Mac 2 - 2.5, the answer was to be able to escape from combat. With the real need on the table the design team was able to address the problem and provide a working solution. Their solution was an agile aircraft with an high thrust-weight ratio, providing acceleration, not maximum speed.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>When the design team asked the air force why they needed Mac 2 - 2.5, the answer was to be able to escape from combat. With the real need on the table the design team was able to address the problem and provide a working solution. Their solution was an agile aircraft with an high thrust-weight ratio, providing acceleration, not maximum speed.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>This lesson should be brought into software development as well. By asking for the value to be provided by a requested feature or requirement. By understanding the value and real need the designers are able address the real problem, and hopefully in the end provide a better and <del style="color: red; font-weight: bold; text-decoration: none;">hopefully </del>cheaper solution compared to addressing the stated need in a head-on approach. By understanding the value behind a requirements also makes prioritizing simpler, as a value can be quantified and ranked.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>This lesson should be brought into software development as well. By asking for the value to be provided by a requested feature or requirement. By understanding the value and real need the designers are able address the real problem, and hopefully in the end provide a better and cheaper solution compared to addressing the stated need in a head-on approach. By understanding the value behind a requirements also makes prioritizing simpler, as a value can be quantified and ranked.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>So, how to proceed then? </div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>So, how to proceed then? </div></td></tr>  </table> Fri, 16 May 2008 07:12:04 GMT Elandre http://commons.oreilly.com/wiki/index.php/Talk:Contribution_6 Elandre: /* Always ask for the value to be provided by a requested capability. */ http://commons.oreilly.com/wiki/index.php?title=Contribution_6&diff=10866&oldid=prev <p><span class="autocomment">Always ask for the value to be provided by a requested capability.</span></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 07:10, 16 May 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 1:</td> <td colspan="2" class="diff-lineno">Line 1:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Always ask for the value to be provided by a requested capability. ==</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>== Always ask for the value to be provided by a requested capability. ==</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>Very often customers and end-users state what they think is a viable solution on a problem as a requirement. The classical story on this was first told by Harry Hillaker, the lead designer of the F-16 Falcon. His team was requested to design a Mac 2 - 2.5 aircraft, which was then, and probably still is, a non trivial task to do. </div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>Very often customers and end-users state what they think is a viable solution on a problem as a requirement. The classical story on this was first told by Harry Hillaker, the lead designer of the F-16 Falcon. His team was requested to design a Mac 2 - 2.5 aircraft, which was then, and probably still is, a non trivial task to do<ins style="color: red; font-weight: bold; text-decoration: none;">. At least when the aim is a "cheap" lightweight aircraft</ins>. </div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>When the design team asked the air force why they needed Mac 2 - 2.5, the answer was to be able to escape from combat. With the real need on the table the design team was able to address the problem and provide a working solution. Their solution was an agile aircraft with an high thrust-weight ratio, providing acceleration, not maximum speed.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>When the design team asked the air force why they needed Mac 2 - 2.5, the answer was to be able to escape from combat. With the real need on the table the design team was able to address the problem and provide a working solution. Their solution was an agile aircraft with an high thrust-weight ratio, providing acceleration, not maximum speed.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>This lesson should be brought into software development as well. By asking for the value to be provided by a requested feature or requirement. By understanding the value and real need the designers are able address the real problem, and hopefully in the end provide a <del style="color: red; font-weight: bold; text-decoration: none;">more elegant, </del>better and hopefully cheaper solution compared to addressing the stated need in a head on approach. By understanding the value behind a requirements also makes prioritizing simpler, as a value can be quantified.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>This lesson should be brought into software development as well. By asking for the value to be provided by a requested feature or requirement. By understanding the value and real need the designers are able address the real problem, and hopefully in the end provide a better and hopefully cheaper solution compared to addressing the stated need in a head<ins style="color: red; font-weight: bold; text-decoration: none;">-</ins>on approach. By understanding the value behind a requirements also makes prioritizing simpler, as a value can be quantified <ins style="color: red; font-weight: bold; text-decoration: none;">and ranked</ins>.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>So, how to proceed then? <del style="color: red; font-weight: bold; text-decoration: none;">My experience </del>is <del style="color: red; font-weight: bold; text-decoration: none;">to have </del>workshops <del style="color: red; font-weight: bold; text-decoration: none;">or </del>meetings with the customer<del style="color: red; font-weight: bold; text-decoration: none;">, where the </del>architects focus <del style="color: red; font-weight: bold; text-decoration: none;"> </del>should be on understanding customer needs, including helping the customer to answer the question why<del style="color: red; font-weight: bold; text-decoration: none;">, not </del>on how to provide a technical solution. <del style="color: red; font-weight: bold; text-decoration: none;"> </del></div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>So, how to proceed then? </div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">There </ins>is <ins style="color: red; font-weight: bold; text-decoration: none;">probably only one way, arrange </ins>workshops <ins style="color: red; font-weight: bold; text-decoration: none;">and </ins>meetings with the customer<ins style="color: red; font-weight: bold; text-decoration: none;">. The </ins>architects focus <ins style="color: red; font-weight: bold; text-decoration: none;">in such session </ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>should be on understanding customer needs, including helping the customer to answer the question why<ins style="color: red; font-weight: bold; text-decoration: none;">. Be aware that answering the why question can be difficult because we talk about tacit knowledge. Discussions </ins>on how to provide a technical solution <ins style="color: red; font-weight: bold; text-decoration: none;">should be avoided</ins>. </div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>The <del style="color: red; font-weight: bold; text-decoration: none;">meeting </del>should be <del style="color: red; font-weight: bold; text-decoration: none;">part </del>of the <del style="color: red; font-weight: bold; text-decoration: none;">release planning process, helping both </del>the customer <del style="color: red; font-weight: bold; text-decoration: none;">and producer to create </del>a <del style="color: red; font-weight: bold; text-decoration: none;">list </del>of <del style="color: red; font-weight: bold; text-decoration: none;">ranked capabilities </del>to be <del style="color: red; font-weight: bold; text-decoration: none;">provided </del>by <del style="color: red; font-weight: bold; text-decoration: none;">the solution. The </del>process should be <del style="color: red; font-weight: bold; text-decoration: none;">repeated when high level features are detailed into more specific requirements. Its probably more important here</del>, to <del style="color: red; font-weight: bold; text-decoration: none;">help sort </del>the <del style="color: red; font-weight: bold; text-decoration: none;">important stuff from </del>the <del style="color: red; font-weight: bold; text-decoration: none;">less important stuff</del>.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>The <ins style="color: red; font-weight: bold; text-decoration: none;">list of ranked capabilities </ins>should be <ins style="color: red; font-weight: bold; text-decoration: none;">brought back to office and assessed with respect to technical feasibility, and the impacts </ins>of the <ins style="color: red; font-weight: bold; text-decoration: none;">assessment should be discussed with </ins>the customer<ins style="color: red; font-weight: bold; text-decoration: none;">. For </ins>a <ins style="color: red; font-weight: bold; text-decoration: none;">large system such assessment involves development </ins>of <ins style="color: red; font-weight: bold; text-decoration: none;">prototypes or demonstrators.</ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div> </div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">With respect </ins>to <ins style="color: red; font-weight: bold; text-decoration: none;">development process, it should </ins>be <ins style="color: red; font-weight: bold; text-decoration: none;">fairly easy to see that this approach is best served </ins>by <ins style="color: red; font-weight: bold; text-decoration: none;">some sort of iterative </ins>process<ins style="color: red; font-weight: bold; text-decoration: none;">. That said, capabilities </ins>should be <ins style="color: red; font-weight: bold; text-decoration: none;">ranked as part of the initial product planning</ins>, <ins style="color: red; font-weight: bold; text-decoration: none;">helping us </ins>to <ins style="color: red; font-weight: bold; text-decoration: none;">maximize value for </ins>the <ins style="color: red; font-weight: bold; text-decoration: none;">customers as early as practical possible. It should also be part of </ins>the <ins style="color: red; font-weight: bold; text-decoration: none;">iteration planning, making sure that the value is sustained when requirements are further detailed</ins>. <ins style="color: red; font-weight: bold; text-decoration: none;"> </ins></div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>The approach fits well into agile methods, as it should be an integral part of the iteration planning process. For those practicing water-fall this need to be part of their requirement elicitation practice. Walking through hundreds of requirements up-front and ask why is a daunting task. </div></td><td colspan="2"> </td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>By [[Einar Landre]]</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>By [[Einar Landre]]</div></td></tr>  </table> Fri, 16 May 2008 07:10:56 GMT Elandre http://commons.oreilly.com/wiki/index.php/Talk:Contribution_6 Elandre: /* Always ask for the value to be provided by a requested capability. */ http://commons.oreilly.com/wiki/index.php?title=Contribution_6&diff=10858&oldid=prev <p><span class="autocomment">Always ask for the value to be provided by a requested capability.</span></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 16:32, 15 May 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 7:</td> <td colspan="2" class="diff-lineno">Line 7:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>This lesson should be brought into software development as well. By asking for the value to be provided by a requested feature or requirement. By understanding the value and real need the designers are able address the real problem, and hopefully in the end provide a more elegant, better and hopefully cheaper solution compared to addressing the stated need in a head on approach. By understanding the value behind a requirements also makes prioritizing simpler, as a value can be quantified.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>This lesson should be brought into software development as well. By asking for the value to be provided by a requested feature or requirement. By understanding the value and real need the designers are able address the real problem, and hopefully in the end provide a more elegant, better and hopefully cheaper solution compared to addressing the stated need in a head on approach. By understanding the value behind a requirements also makes prioritizing simpler, as a value can be quantified.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>So, how to proceed then? My experience is to have workshops or meetings with the customer, where the architects focus should be on understanding customer needs, including helping the customer to <del style="color: red; font-weight: bold; text-decoration: none;">state </del>the <del style="color: red; font-weight: bold; text-decoration: none;">value from a stated need</del>, not on how to provide <del style="color: red; font-weight: bold; text-decoration: none;">an implementation</del>. </div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>So, how to proceed then? My experience is to have workshops or meetings with the customer, where the architects focus should be on understanding customer needs, including helping the customer to <ins style="color: red; font-weight: bold; text-decoration: none;">answer </ins>the <ins style="color: red; font-weight: bold; text-decoration: none;">question why</ins>, not on how to provide <ins style="color: red; font-weight: bold; text-decoration: none;">a technical solution</ins>. </div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div><del style="color: red; font-weight: bold; text-decoration: none;">This </del>approach fits well <del style="color: red; font-weight: bold; text-decoration: none;">with SCRUM sprint planning sessions, for those practicing </del>agile methods. For those <del style="color: red; font-weight: bold; text-decoration: none;">stuck in their </del>water fall <del style="color: red; font-weight: bold; text-decoration: none;">processes, </del>this <del style="color: red; font-weight: bold; text-decoration: none;">type of meeting </del>need to be <del style="color: red; font-weight: bold; text-decoration: none;">an integral </del>part of their <del style="color: red; font-weight: bold; text-decoration: none;">requirements </del>elicitation <del style="color: red; font-weight: bold; text-decoration: none;">process</del>. <del style="color: red; font-weight: bold; text-decoration: none;"> </del></div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">The meeting should be part of the release planning process, helping both the customer and producer to create a list of ranked capabilities to be provided by the solution. The process should be repeated when high level features are detailed into more specific requirements. Its probably more important here, to help sort the important stuff from the less important stuff.</ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div> </div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">The </ins>approach fits well <ins style="color: red; font-weight: bold; text-decoration: none;">into </ins>agile methods<ins style="color: red; font-weight: bold; text-decoration: none;">, as it should be an integral part of the iteration planning process</ins>. For those <ins style="color: red; font-weight: bold; text-decoration: none;">practicing </ins>water<ins style="color: red; font-weight: bold; text-decoration: none;">-</ins>fall this need to be part of their <ins style="color: red; font-weight: bold; text-decoration: none;">requirement </ins>elicitation <ins style="color: red; font-weight: bold; text-decoration: none;">practice. Walking through hundreds of requirements up-front and ask why is a daunting task</ins>. </div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>By [[Einar Landre]]</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>By [[Einar Landre]]</div></td></tr>  </table> Thu, 15 May 2008 16:32:46 GMT Elandre http://commons.oreilly.com/wiki/index.php/Talk:Contribution_6 Elandre: /* Always ask for the value to be provided by a requested capability. */ http://commons.oreilly.com/wiki/index.php?title=Contribution_6&diff=10856&oldid=prev <p><span class="autocomment">Always ask for the value to be provided by a requested capability.</span></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 15:52, 15 May 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 5:</td> <td colspan="2" class="diff-lineno">Line 5:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>When the design team asked the air force why they needed Mac 2 - 2.5, the answer was to be able to escape from combat. With the real need on the table the design team was able to address the problem and provide a working solution. Their solution was an agile aircraft with an high thrust-weight ratio, providing acceleration, not maximum speed.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>When the design team asked the air force why they needed Mac 2 - 2.5, the answer was to be able to escape from combat. With the real need on the table the design team was able to address the problem and provide a working solution. Their solution was an agile aircraft with an high thrust-weight ratio, providing acceleration, not maximum speed.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>This lesson should be brought into software development as well. By asking for the value to be provided by a requested feature or requirement. By understanding the value and real need the designers are able address the real problem, and hopefully in the end provide a more elegant, better and hopefully cheaper solution compared to addressing the stated need in a head on approach.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>This lesson should be brought into software development as well. By asking for the value to be provided by a requested feature or requirement. By understanding the value and real need the designers are able address the real problem, and hopefully in the end provide a more elegant, better and hopefully cheaper solution compared to addressing the stated need in a head on approach. <ins style="color: red; font-weight: bold; text-decoration: none;">By understanding the value behind a requirements also makes prioritizing simpler, as a value can be quantified.</ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div> </div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">So, how to proceed then? My experience is to have workshops or meetings with the customer, where the architects focus should be on understanding customer needs, including helping the customer to state the value from a stated need, not on how to provide an implementation. </ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div> </div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><ins style="color: red; font-weight: bold; text-decoration: none;">This approach fits well with SCRUM sprint planning sessions, for those practicing agile methods. For those stuck in their water fall processes, this type of meeting need to be an integral part of their requirements elicitation process. </ins></div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>By [[Einar Landre]]</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>By [[Einar Landre]]</div></td></tr>  </table> Thu, 15 May 2008 15:52:17 GMT Elandre http://commons.oreilly.com/wiki/index.php/Talk:Contribution_6 Elandre: /* Always ask for the value to be provided by a requested capability. */ http://commons.oreilly.com/wiki/index.php?title=Contribution_6&diff=10852&oldid=prev <p><span class="autocomment">Always ask for the value to be provided by a requested capability.</span></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 07:58, 15 May 2008</td> </tr> <tr><td colspan="2" class="diff-lineno">Line 3:</td> <td colspan="2" class="diff-lineno">Line 3:</td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>Very often customers and end-users state what they think is a viable solution on a problem as a requirement. The classical story on this was first told by Harry Hillaker, the lead designer of the F-16 Falcon. His team was requested to design a Mac 2 - 2.5 aircraft, which was then, and probably still is, a non trivial task to do. </div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>Very often customers and end-users state what they think is a viable solution on a problem as a requirement. The classical story on this was first told by Harry Hillaker, the lead designer of the F-16 Falcon. His team was requested to design a Mac 2 - 2.5 aircraft, which was then, and probably still is, a non trivial task to do. </div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'>-</td><td style="background: #ffa; color:black; font-size: smaller;"><div>When the design team asked the air force <del style="color: red; font-weight: bold; text-decoration: none;">[[</del>why<del style="color: red; font-weight: bold; text-decoration: none;">]] </del>they needed Mac 2, <del style="color: red; font-weight: bold; text-decoration: none;">they </del>was <del style="color: red; font-weight: bold; text-decoration: none;">told that Mac 2 was required </del>to escape from combat. <del style="color: red; font-weight: bold; text-decoration: none;">When </del>the real need <del style="color: red; font-weight: bold; text-decoration: none;">was articulated </del>the design team was able to address the problem and provide a working solution. Their solution was an agile aircraft with an high thrust-weight ratio, providing acceleration, not maximum speed.</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div>When the design team asked the air force why they needed Mac 2 <ins style="color: red; font-weight: bold; text-decoration: none;">- 2.5</ins>, <ins style="color: red; font-weight: bold; text-decoration: none;">the answer </ins>was <ins style="color: red; font-weight: bold; text-decoration: none;">to be able </ins>to escape from combat. <ins style="color: red; font-weight: bold; text-decoration: none;">With </ins>the real need <ins style="color: red; font-weight: bold; text-decoration: none;">on the table </ins>the design team was able to address the problem and provide a working solution. Their solution was an agile aircraft with an high thrust-weight ratio, providing acceleration, not maximum speed.</div></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr> <tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>This lesson should be brought into software development as well. By asking for the value to be provided by a requested feature or requirement. By understanding the value and real need the designers are able address the real problem, and hopefully in the end provide a more elegant, better and hopefully cheaper solution compared to addressing the stated need in a head on approach.</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>This lesson should be brought into software development as well. By asking for the value to be provided by a requested feature or requirement. By understanding the value and real need the designers are able address the real problem, and hopefully in the end provide a more elegant, better and hopefully cheaper solution compared to addressing the stated need in a head on approach.</div></td></tr>  </table> Thu, 15 May 2008 07:58:47 GMT Elandre http://commons.oreilly.com/wiki/index.php/Talk:Contribution_6