[PJUG Javamail] December 15 Workshop- Skills for the Agile Designer

[Rebecca Wirfs-Brock]

PJUgers-
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. Skills for the Agile Designer 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.

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.

I need six registered students to hold this class.

Course Overview
Agile designers need to quickly see the essence of a problem, shape
reasonable solutions, and communicate effectively. When things don't
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.

Objectives

At the end of this short course attendees should be able to:
Identify problem frames (types) and use them to ask probing questions  
of their customers
Write and share designer stories to kick off an iteration
Use a common vocabulary for characterizing various aspects of a design
Sort through designs tasks and identify their project impact
Conduct a CRC card modeling session
Recognize when a "wicked" problem crops up and how it affects project  
flow
Effectively discuss issues and come to meaningful agreements
Measure design progress and track technical debt

Course Outline
What makes a designer agile?
Problem Frames: a tool for seeing typical patterns of software tasks
A designer's story: a tool for seeing/communicating what's important
Object Role Stereotypes: a tool for seeing object behaviors
CRC card modeling basics and when a responsibility model can help
Control centers and collaboration styles: a tool for shaping
collaborations where "defensive" behavior is needed and specific
tests are required
Design problem types: A tool for balancing priorities
Handling design criticism: What to do with valid, invalid, aesthetic,  
personal, judgmental criticism and praise
Adding design topics to project retrospectives
Course fee: $425 if registered and paid by 12/5/2008   $475 after  
12/5/2008. Lunch and break refreshments included.

Please feel free to contact me with any questions.
Registration is through OGI's website: http://www.cpd.ogi.edu/coursespecific.asp?pam=2427


Cheers,
Rebecca

Rebecca Wirfs-Brock
rebecca at wirfs-brock.com
website: www.wirfs-brock.com
cell: 503-313-4978

"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

Don't you want to take responsibility for your design?




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pjug.org/pipermail/javamail/attachments/20081203/289a3de1/attachment.html