More often, there will be some problem that
necessitates a short or nonexistent lunch break for at least some of the team (normally
the leader, either internal or external), and panicked debugging to ?¬?nd out why the
darned thing doesn??™t work. It??™s all part of the fun, and just goes to prove that DSM is
part of the real world, not some utopian fantasy.
338 DSM DEFINITION PROCESS
By the time of the meeting, at least some of the team are rapidly becoming DSM
experts. The idea has clicked, and they are churning out new bits of generators or
extensions to the modeling language at an astonishing rate. Nothing is more
guaranteed to bring sweat to the brow of a DSM consultant giving his introductory
spiel to senior management than to see a team member on ?¬?re, making changes to the
modeling language and generators that had just been made to compile successfully
?¬?ve minutes earlier. And nothing is more gratifying than to be able to say ???and you
saw that when we pressed that new button, the whole user interface changed to
Swedish??”and that??™s functionality that Fred there added from scratch while we??™ve
been sitting in this meeting.???
13.4 DEFINING THE DSM SOLUTION
After the proof of concept, the team building the solution can see that DSM is indeed
applicable in their domain. Often this may come as something of a shock to some team
members, who perhaps have turned a blind eye to the inef?¬?ciencies of previous
practice and were certain that nothing major could be achieved.
Pages:
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635