Page 306 - Software and Systems Requirements Engineering in Practice

ç ç 3 O F T W A R E ç ç 3 Y S T E M S ç 2 E Q U I R E M E N T S ç % N G I N E E R I N G ç ) N ç 0 R A C T I C E

WORLD CAN VIEW AND EDIT THE REQUIREMENTS IN THE DATABASE USING A
USER INTERFACE OF THE WEB BROWSER CLIENT TYPE
3CRUM TEAMS WILL LIKELY CONDUCT DAILY STAND UP MEETINGS TO HELP
COORDINATE THE ACTIVITIES WITHIN THE TEAM 4HESE SHORT MEETINGS
TYPICALLY ADDRESS THE THREE QUESTIONS 7HAT HAVE YOU DONE 7HAT
DO YOU PLAN TO DO !ND IS THERE ANYTHING STANDING IN THE WAY OF
MAKING PROGRESS &OR GLOBAL DEVELOPMENT WE RECOMMEND A WEEKLY
COORDINATION TELECONFERENCE FACILITATED BY THE PRODUCT OR PROJECT
MANAGER WITH A REPRESENTATIVE FROM EACH COMPONENT DEVELOPMENT
TEAM CALLED A hSCRUM OF SCRUMS v 4HE AUDIO PORTION OF THE WEEKLY
TELECONFERENCE CAN BE AUGMENTED WITH A DESKTOP SHARING TOOL SO THAT
PRESENTATION CHARTS DIAGRAMS OR DOCUMENTS COULD BE VIEWED BY ALL
THE PARTICIPANTS
7E RECOMMEND USING VIDEOCONFERENCES FOR hSPECIALv MEETINGS
4HESE WOULD INCLUDE ITERATION KICKOFF MEETINGS REVIEW MEETINGS OR
MEETINGS WHERE TECHNICAL DOCUMENTATION IS EXCHANGED OR DISCUSSED
BETWEEN THE CENTRAL TEAM AND A REMOTE TEAM 3INCE THE VIDEOCONFERENCE
EQUIPMENT IS USUALLY A SHARED RESOURCE THESE MEETINGS WOULD LIKELY
BE SCHEDULED IN ADVANCE )N CONTRAST THE WEEKLY TELECONFERENCE
WOULD BE SCHEDULED FOR THE SAME TIME SLOT EACH WORKWEEK )F STAFF
MEMBERS ARE NOT AT THEIR WORKPLACE DURING THE FIXED TIME SLOT THEY
CAN CALL INTO THE TELECONFERENCE 7HEN PARTICIPANTS ARE NOT AVAILABLE
DUE TO VACATION OR ILLNESS THEY SHOULD ASSIGN A PROXY TO PARTICIPATE IN
THE WEEKLY SCRUM OF SCRUMS MEETING
!LTHOUGH WE PREFER THAT SOME MEMBERS OF THE CENTRAL TEAM BE
PRESENT AT THE ITERATION KICKOFF MEETING AT THE REMOTE SITES CLEARLY FOR
LARGE PROJECTS WITH MANY REMOTE TEAMS THIS IS NOT POSSIBLE )N THIS
CASE WE RECOMMEND THAT VIDEOCONFERENCING BE USED 7E ALSO
RECOMMEND THAT WHENEVER POSSIBLE CENTRAL TEAM MEMBERS VISIT
SOME OF THE REMOTE SITES TO REVIEW THE SPRINT DELIVERABLES !GAIN THIS
IS PROBABLY NOT POSSIBLE FOR EVERY SPRINT FOR EVERY SITE BUT WE HAVE
OBSERVED THAT PERIODIC CONTACT BETWEEN THE REMOTE AND CENTRAL TEAMS
IS VALUABLE FOR MOTIVATING ALL THE TEAM MEMBERS
-ANY OF THE COMMUNICATIONS BETWEEN THE CENTRAL AND REMOTE
TEAMS WILL NECESSARILY BE IN THE FORM OF E MAIL 4HIS IS PARTICULARLY
LIKELY BETWEEN SITES FOR EXAMPLE IN THE 5 3 AND )NDIA WHEN ONE
TEAM IS LIKELY TO BE WORKING WHILE THE OTHER TEAM IS SLEEPING )T IS
SUGGESTED THAT A SECURE INTRANET AND VIRTUAL PRIVATE NETWORKS BE SET
UP FOR SUCH E MAILS AND DEVELOPMENT TOOLS 4HIS WILL PROVIDE SOME
DEGREE OF PROTECTION FOR YOUR PROPRIETARY PROJECT COMMUNICATIONS
AND ARTIFACTS
7E RECOMMEND THAT A COLLABORATION WEB SITE E G WIKI BE SET UP
FOR ALL TEAM MEMBERS TO VIEW DECISIONS MADE ON THE PROJECT STORE
KEY DOCUMENTS AND SUPPORT ASYNCHRONOUS DISCUSSIONS E G
FORUMS 4HIS COLLABORATION SITE SHOULD ALSO CONTAIN THE TOOL SET THAT
WILL BE USED ON THE PROJECT AND RELEVANT TRAINING INFORMATION
!LTHOUGH WE HAVE NO PROBLEM WITH DIFFERING PROCESSES USED AT