<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">PJUgers-<div><div>I am pleased to be conducting a one-day agile design workshop, in conjunction with Oregon Graduate Institute's Center for Professional Development in Beaverton. <i>Skills for the Agile Designer</i> is a hands-on workshop where we have time to explore several different techniques including problem framing techniques, designer stories, CRC card modelling, resolving design conflicts, and some simple measures for design efforts and debt. <br></div><div><br></div><div>This course is intended for software developers who are familiar with agile development and are looking to add a few software design techniques and improve how they discuss/debate design and interact with customers.</div><div><br></div><div>I need six registered students to hold this class.</div><div><font class="Apple-style-span" face="Arial" size="3"><span class="Apple-style-span" style="font-size: 13px; "><b><br></b></span></font></div><div><span class="Apple-style-span" style="font-family: Arial; font-size: 13px; "><b>Course Overview</b></span></div><div><span class="Apple-style-span" style="font-family: Arial; font-size: 13px; ">Agile designers need to quickly see the essence of a problem, shape</span></div><div><font class="Apple-style-span" face="Arial" size="3"><span class="Apple-style-span" style="font-size: 13px; "><b><span class="Apple-style-span" style="font-weight: normal; ">reasonable solutions, and communicate effectively. When things don't<br>exactly go according to plan, they must react, readjust their thinking, and try again. Seasoned agile designers strike a balance. They know the difference between core and revealing design tasks and plan accordingly. When unanticipated difficulties crop, they adapt their work rhythms. They know how to give and take criticism and ask clarifying questions of teammates and project stakeholders.<br><br><b>Objectives</b><br><br>At the end of this short course attendees should be able to:<br><ul><li>Identify problem frames (types) and use them to ask probing questions of their customers<br></li><li>Write and share designer stories to kick off an iteration<br></li><li>Use a common vocabulary for characterizing various aspects of a design<br></li><li>Sort through designs tasks and identify their project impact<br></li><li>Conduct a CRC card modeling session<br></li><li>Recognize when a "wicked" problem crops up and how it affects project flow<br></li><li>Effectively discuss issues and come to meaningful agreements<br></li><li>Measure design progress and track technical debt</li></ul><br><b>Course Outline</b> <br><ul><li>What makes a designer agile?<br></li><li>Problem Frames: a tool for seeing typical patterns of software tasks<br></li><li>A designer's story: a tool for seeing/communicating what's important<br></li><li>Object Role Stereotypes: a tool for seeing object behaviors<br></li><li>CRC card modeling basics and when a responsibility model can help<br></li><li>Control centers and collaboration styles: a tool for shaping<br>collaborations where "defensive" behavior is needed and specific<br>tests are required<br></li><li>Design problem types: A tool for balancing priorities<br></li><li>Handling design criticism: What to do with valid, invalid, aesthetic, personal, judgmental criticism and praise<br></li><li>Adding design topics to project retrospectives</li></ul></span></b></span></font></div><div><span class="Apple-style-span" style="font-family: Arial; font-size: 13px; "><b>Course fee: $425</b> if registered and paid by 12/5/2008 $475 after 12/5/2008. Lunch and break refreshments included.</span></div><div><span class="Apple-style-span" style="font-family: Arial; font-size: 13px; "><br></span>Please feel free to contact me with any questions.<br>Registration is through OGI's website: <a href="http://www.cpd.ogi.edu/coursespecific.asp?pam=2427">http://www.cpd.ogi.edu/coursespecific.asp?pam=2427</a><br></div><div><br></div><div><br></div><div>Cheers,</div><div>Rebecca</div><div><br></div><div apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Rebecca Wirfs-Brock</div><div><a href="mailto:rebecca@wirfs-brock.com">rebecca@wirfs-brock.com</a></div><div>website: <a href="http://www.wirfs-brock.com">www.wirfs-brock.com</a></div><div>cell: 503-313-4978</div><div><br></div><div>"A man should learn to detect and watch that gleam of light which flashes across his mind from within, more than the lustre of the firmament of bards and sages. Yet he dismisses without notice his thought, because it is his."--Ralph Waldo Emerson</div><div><br></div><div>Don't you want to take responsibility for your design?</div><div><br></div></div><br></div></span><br class="Apple-interchange-newline"> </div><br></div></body></html>