Page 309 - Software and Systems Requirements Engineering in Practice
P. 309

U
                                                 T
                                               B
                                             R
                                              I
                                                     2
                                                       E
                                                     ç
                                                  E
                                                   D
                                            T
                                  R
                                   ç
                                 E
                              P
                                T
                                          I
                                           S



                                                        Q
                                                                        N
                                                                         E
                                                                       I
                                                                     N
                                                                      G
                                                                             N
                                                                              G
                                                                             I
                                                                          E
                                                                            R
                                                                    %
                                                            E
                                                             M
                                                           R
                                                         U
                                                          I
                                                                  S
                                                                   ç
                                                                 T
                                                               E
                                                                N
                            H
        ç ç                # # H A P T E R ç       ç ç  $ $ I S T R I B U T E D ç 2 E Q U I R E M E N T S ç % N G I N E E R I N G ç ç
                             A
                         4HERE ARE COMPETITIVE SITUATIONS WHERE THE CENTRAL TEAM MAY BE
                      LOOKING FOR THE hLOWEST COSTv SUPPLIER OR EVALUATIONS OF THE SUPPLIERS
                      COMPETENCIES   &OR  DISTRIBUTED  DEVELOPMENT   WE  HAVE  FOUND  THAT  A
                      REMOTE DEVELOPMENT ORGANIZATION WORKING IN A DOMAIN FOR THE FIRST
                      TIME HAS A DIFFICULT TIME GENERATING A REALISTIC ESTIMATE OF THE COST AND
                      SCHEDULE TO DEVELOP THE REQUESTED FUNCTIONALITY  4HUS  WE RECOMMEND
                      THAT THE CENTRAL ORGANIZATION DO THEIR OWN COST ESTIMATES AS THEY WOULD
                      IF THEY WERE DEVELOPING THE FEATURES USING THEIR EXPERIENCE WITH PAST
                      SIMILAR PROJECTS  4HESE INTERNAL ESTIMATES CAN BE USED TO hVALIDATEv THE
                      ESTIMATES  RECEIVED  FROM  THE  SUPPLIERS   )N  SUCH  SITUATIONS   WE  HAVE
                      OBSERVED  THAT  THE  hLOWEST COSTv  SUPPLIER  MAY  INDEED  BE  THE  hMOST
                      NAÆVEv  SUPPLIER  !S  DOMAIN  EXPERTISE  REQUIRES  THE  LONGEST  LEARNING
                      CURVE FOR A NEW SUPPLIER  SELECTIONS OF VENDORS SHOULD BE PRIMARILY
                      DRIVEN BY DOMAIN EXPERIENCE OR THE ABILITY TO LEARN A NEW OR RELATED
                      DOMAIN  #OST AND SCHEDULE ESTIMATION METHODS CAN BE FOUND IN ;*ONES
                          =  #OST AND SCHEDULE ESTIMATION METHODS FOR GLOBALLY DISTRIBUTED
                      PROJECTS CAN BE FOUND IN ;3ANGWAN ET AL      =
                     õ 4IPSõFORõ$ISTRIBUTEDõ2EQUIREMENTSõ%NGINEERING
                      4HE  FOLLOWING  TIPS  ARE  SUGGESTED  FOR  DISTRIBUTED  REQUIREMENTS
                      ENGINEERING
                          v  0LAN YOUR DISTRIBUTED PROJECTS FOR THE LONG TERM TO BE ABLE TO
                             REALIZE ANY COST SAVINGS AFTER DOMAIN COMPETENCE IS DEVELOPED
                             AT THE LOW COST SITES
                          v  3TAFF  YOUR  2%  TEAM  WITH  SOME  MEMBERS  OF  THE  REMOTE
                             DEVELOPMENT TEAMS  WHO HAVE TEMPORARILY RELOCATED TO WORK
                             AT  THE  CENTRAL  SITE   4HESE  TEAM  MEMBERS  WILL  BECOME  THE
                             DOMAIN EXPERTS AT THE REMOTE SITES
                          v  "EGIN A NEW PROJECT WITH A NEW REMOTE TEAM USING A PROCESS
                             LIKE  THE  EXTENDED  WORKBENCH  MODEL   AND  THEN  MIGRATE  TO
                             MORE  OF  A  SYSTEM  OF  SYSTEMS  MODEL  AS  THE  DOMAIN  AND
                             TECHNICAL KNOW HOW OF THE REMOTE TEAMS IS DEVELOPED
                          v  -ONITOR YOUR TRAVEL COSTS AS AN EARLY INDICATOR THAT A PROBLEM
                             MAY BE DEVELOPING ACROSS TWO SITES
                          v  %XCHANGE STAFF AS SHORT  OR LONG TERM DELEGATES BETWEEN THE
                             CENTRAL AND REMOTE SITES
                          v  "RING  THE  DISTRIBUTED  2%S  TOGETHER  PERIODICALLY  FOR  2%
                             WORKSHOPS AND REVIEWS AND ENCOURAGE PERSONAL NETWORKING
                             AMONG THEM TO BUILD A hVIRTUAL 2% TEAM v
                          v  4O COMBAT JET LAG  COLLOCATE THE DISTRIBUTED 2% TEAM FOR THREE
                             WEEKS  AT  A  TIME   AND  THEN  ALLOW  THEM  TWO  WEEKS  AT  THEIR
   304   305   306   307   308   309   310   311   312   313   314