Date: 01-08-2020

 ENHANCES COMPANY IMAGE & REPUTATION - A SAFER WORK ENVIRONMENT

ATTRACTS BETTER TALENT & ALSO PROMOTES THE COMPANY BRAND . SAFETY
DEMONSTRATES A BUSINESS IS SOCIALLY RESPONSABLE . SAFE WORK ENVIRON-
MENT ENABLES A BUSINESS TO RETAIN CLIENTS . CUSTOMERS ARE KEEN TO
WORK WITH FIRMS THAT FOLLOW PROPER SAFETY MEASURES .

 ABSENTEEISM REDUCED - EMPLOYEESS WANT TO WORK IN SAFE ENVIRON-

MENT . THERE ARE MORE HAPPY EMPLOYEES AS THEY WANT TO GO HOME SAFE.
ABSENTIEESM DROPS WHEN EFFECTIVE SAFETY PROGRAMS ARE IN PLACE .

Q.B. WHAT ARE THE ROLE OF MANAGER IN SAFETY MANAGEMENT ?

ANS. SAFETY MANAGER RESPONSIBLITIS INCLUDES :

 DEVELOPING AND EXECUTING HEALTH AND SAFETY PLANS IN THE WORKPLACE
ACCORDING TO LEGAL GUIDELINES .
 PREPARING AND ENFORCING POLICIES TO ESTABLISH A CULTURE OF HEALTH
AND AFETY .
 EVALUETING PRACTICES , PROCEDURE AND FACILITIES TO ASSESS RISK AND
ADHERANCE TO THE LAW .

JOB BRIEF : WE ARE LOOKING FOR RELIABLE SAFETY MANAGER TO ENSURE EVERYONE IN
THE COMPANY COMPLIES WITH HEALTH AND SAFTY LAWS . YOU WILL ALSO BE RESPONSIBLE
FOR ESTABLISHING POLICIES THAT WILL CREATE AND MAITAIN A SAFE WORKPLACE . AS A
SAFETY MANAGER YOU MUST HAVE EXCELLENT ATTENTION TO DETAIL TO IDENTIFY HAZARDS.
YOU WILL ALSO BE ABLE TO DISCOVER OPPORTUNITIES FOR IMPROVING CONDITION AND
EXECUTE VARIOUS SAFETY PROGRAMS . THE ABILITY TO COMUNICATE GUIDELINES TO MULTI-
DISCIPLINARY WORKFORCE IS ESSENTIAL .THE GOAL IS TO ENSURE THE WORKPLACE MEETSALL
LEGAL EXPECTATIONS AND ACTIVELY SUPPORTS OCCUPATIONAL HEALTH AND SAFETY .

RESPONSIBLITITIES :

 DEVELOP AND EXECUTE HEALTH AND SAFETY PLANS IN THE WORKPLACE

ACCORDING TO LEGAL GUIDELINES .
 PREPARE AND EENFORCE POLICIES TO ESTABLISH A CULTURE OF HEALTH
AND SAFETY .
 EVALUATE PRACTICES , PROCEDURES AND FACILITIES TO ASSESS RISK AND
ADHERANCE TO THE LAW .
 CONDUCT TRAINING AND PRESENTATIONS FOR HEALTH AND SAFETY MATTERS
AND ACCIDENTS PREVENTIONS .
 Date: 01-08-2020

 MONITOR COMPLIANCE TO POLICIES AND LAWS BY INSPECTING EMPLOYEES

AND OPERATIONS .
 INSPECT EQUIPMENT AND MACHINARY TO OBSERVE POSSIBLE UNSAFE CONDI-
TIONS .
 INVESTIGATE ACCIDENTS OR INCIDENTS TO DISCOVER CAUSES AND HANDLE
WORKER’S COMPENATION CLAIMS .
 RECOMEND SOLUTIONS TO ISSUES , IMPROVEMENT OPPORTUNITIES OR NEW
PREVENTION MEASURE .
 REPORT ON HEALTH AND SAFETY AWARENESS , ISSUES AND STATISTICS .

REQUIRMENTS :
 PROVEN EXPERIENCE AS SAFETY MANAGER .
 DEEP UNDERSTANDING OF LEGAL HEALTH AND SAFETY GUIDELINES .
 ABILITY IN PRODUCING REPORTS AND DEVELOPING RELEVANT POLICIES .
 GOOD KNOWLEDGE OF DATA ANALYSIS AND RISK ASSESMENTS .
 EXCELLENT ORGANIZATIONAL AND MOTIVATIONAL SKILLS .
 OUTSTANDING ATTENTION TO DETAIL AND OBSERVATIONAL ABILITIES .
 BSC/BA IN SAFETY MANAGEMENT OR RELEVANT FIELD IS PREFERED .
 VALID QUALIFICATION IN OCCUPATIONAL HEALTH AND SAFETY .

Q. C. WHAT ARE THE MAIN CAUSES OF ACCIDENTS IN CONSTRUCTION ?

ANS. THE OCCUPATIONAL SAFETY AND HEALTH ADMINISTRATION ( OSHA ) REPORTS THAT
THERE WERE 3945 WORKER FATALITIES IN PRIVATE INDUSTRY IN 2012 . OF THAT NUMBER ,
775 OR 19.6 % WERE IN CONSTRUCTION . THERE ARE MANY CAUSES OF AN ACCIDENT ON A
CONSTRUCTION SITE . THE TOP CAUSES OF CONSTRUCTION WORKER DEATHS ON THE JOB
WERE FALLS , FOLLOWED BY STRUCT BY OBJECT , ELECTROCUTION , AND CAUGHT -IN/
BETWEEN. THESE “ FATAL FOUR “ WERE RESPONSIBLE FOR NEARLY THREE OUT OF FIVE OF
THE CONSTRUCTION WORKER DEATHS. MANY ACCIDENTS MAY BE ATTRIBUTED TO SOME TYPE
OF NEGLIGENCE AND MAY INVOLV UNSAFEE WORK SITE CONDITIONS , INPROPER USE OF
TOOLS AND OR EQUIPMENT , AND LACK OF PROTECTIVE SAFEGURDS . SOME EXAMPLES OF
CONSTRUCTION SITE ACCIDENTS ARE MORE COMMON THAN OTHERS . BELOW IS A LIST OF
THE MORE COMMON ONES STARTING WITH THE FATAL FOUR .

1. FALLS . FALLS ACCOUNTED FOR 278 OUT OF 775 ( 36% ) TOTAL DEATHS IN CONSTRUC-
TION IN 2012 , ACCORDING TO OSHA . AN INJURY OF THIS TYPE MAY OCCUR WHEN
A WORKER NEAR AN OPEN – SIDED FLOOR STEPS BACKWARD OR SIDEWAYS WITH-
OUT LOOKING . FALLING HAZARDS ALSO COMMONLY OCCUR ON STAIRWELLS WITH
NO GURDRAILS . SINCE HIGH ELEVATIONS OFTEN PLAY A ROLE IN THESE FALLS , THE
REULTS CAN BE CATASTROPIC TO WORKERS WHO SUSTAIN SERIOUS INJURIES . THE
 Date: 01-08-2020

MAIN CAUSE OF DEATH IN CONSTRUCTION OCCURS WHERE INADEQUATE OR NO FALL

PROTECTION IS PROVIDED .

2. STRUCK BY OBJECT . SEVENTY –EIGHT CONTRUCTION WORKERS DIED AS A RESULT OF

BEING STRUCK BY AN OBJECT IN 2012 . A NUMBER OF THESE DEATHS MAY HAVE
BEEN PREVENTED IF THE WORKERS HAD UNDERGONE PROPER TRAINING AND USED
EQUIPMENT AND MACHINERY PROPERLY . EMPLOYEES MUST REMEMBER TO USE
PARKING BREAKS ON NONMOVING VEHICLES , REVERSE VEHICLES ALARMS , TOOL
GURDS , PERONAL PROTECTION EQUIPMENT ,DEBRIS NETS , CATCH PLATFORMS AND
MORE .

3. ELECTROCUTIONS . IN 2012 , 66 WORKERS ( 9% ) WERE SERIOUSLY INJURED OR KILLED BY

ELECTROCUTION . ELECTROCUTION IS WHEN A PERSON , TOOL OR PIECE OF EQUIPMEENT
COMES INTO CONTACT WITH POWER LINES OR EXPOSED ELECTRICAL SOURCES . SOME-
TIMES , THESE TYPES OF ACCIDENTS OCCUR BECAUSE WORKERS ARE SIMPLY UNAWARE
OF ALL ENERGIZED POWER SOURCES , FROM OVERHEAD AND UNDERGROUND POWER
LINES TO DAMAGED RECEPTACLES AND CONNECTORS . AS AN EXAMPLE , A CONSTRUC-
TION WORKER CARRYING A METAL LADDER MAY STRIKE AN OVERHEAD POWER LINE .

4. CAUGHT / IN BETWEEN . ALTHOUGH IT SEEMS OBVIOUS TO NEVER STAND BETWEEN

A PIECE OF HEAVY EQUIPMENT AND AN IMMOVABLE OBJECT , SOMETIMES WORKERS
CONCENTRATING ON THEIR JOBS FIND THEMSELVES IN UNEXPECTED DANGER . CAUGHT
IN/ BETWEEN ACCIDENTS ARE WHEN A WORKER’S BODY PART IS CAUGHT , CRUSHED ,
SQUEEZED , COMPRESSED OR PINCHED BETWEEN TWO OR MORE OBJECTS . EXAMPLES
INCLUDE CAVE –INS OR COLLAPSING MATERIALS , BODY PARTS CAUGHT IN THE MOVING
PARTS OF AN UNGURDED PIECE OF MACHINARY , EQUIPMENTS ROLLOVER

Q.D . WHAT’S MEANT BY QUALITY OF WORK IN RESPECT OF CIVIL

ENGINEERING ?

ANS. IN CONSTRUCTION INDUSTRY QUALITY IS THE PERFORMANCE OF THE TASKS WHICH

ENSURE THAT CONSTRUCTION IS PERFORMED ACCORDING TO PLANS AND PECIFICATIONS,
ON TIME , WITHIN A DEFINED BUDGET , AND SAFE WORK ENVIRONMENT . QUALITY IN
CONSTRUCTION SHOULDN’T BE ONLY ABOUT TAKING CONCRETE CUBES , OPENING/
CLOSING NCRs OR ADDING PAPER WORK AND BUREAUCRACY FOR THE ALREADY BUSY
ENGINEERS SITE . IT SHOULD BE ABOUT PROPER PLANNING , BUDGETING , RISK ANALYSIS
AND BUILDING EXCELLENT RELATIONSHIP WITH THE CLIENT’S REPRESENTATIVES ON A
DAILY BASIS . SO IN CONSTRUCTION INDUSTRY YOU ACTUALLY HAVE TO BUILD IT “ RIGHT
FIRST TIME “........BUT HOW DO THAT .......NORMALLY PEOPLE ARE CONFUSED BETWEEN
QUALITY ASSURANCE AND QUALITY CONTROL , THOUGH THEY ARE CLOSELY REALATED
BUT FUNDAMENTALLY DIFFERENT PROCESSES WITH DIFFERENT GOALS AND PURPOSES .
 Date: 01-08-2020

QUALITY ASSURANCE :-

 QA MAKES SURE THAT WE ARE DOING THE “ RIGHT THINGS THE RIGHT WAY “.
 QA FOCUSES ON BUILDING IN QUALITY AND HENCE “ PREVENTING DEFECTS “.
 QA DEALS WITH PROCESS .
 QA IS FOR ENTIRE LIFE CYCLE .
 QA IS A PREVENTIVE PROCESS .
 QA IS A STAFF FUNCTION .

QUALITY CONTROL :

 QC MAKES SURE THE RESULTS OF “ WHAT WE HAVE DONE ARE WHAT WE

EXPECTED “ .
 QC FOCUSES ON TESTING FOR QUALITY AND HENCE “ DETECTING DEFECTS “
 QC DEALS WITH PRODUCT .
 QC IS FOR TESTING PART .
 QC IS CORRECTIVE PROCESS .
 QC IS LINE FUNCTION .

Q.E. WHAT ARE THE DIFFERENT QUALITY OF ASSURANCE TECHNIQUE ?

ANS.
1. INVOVE A QA TEAM STARTING WITH DISCOVERY PHASE :
IN MOST CASES , THE QA TEAM ENTERS GAME ONLY AFTER SOME FUNCTIONALITY
IS DEVELOPED AND NEEDS TO BE TESTED . AS A RESULT , TESTER REPORT A LOT OF
BUGS THAT COULD HAVE BEEN PREVENTED WITH PRPER PLANNING . BUT IT IS A
GOOD IDEA TO INVOLVE A TEAM OF VARIOUS PROFESSIONALS IN THE DISCOVERY
PHASE . THAT WAY , EVERY ONE HAS A CHANCE TO IMPROVE THE DEVELOPMENT
PLAN FROM THEIR EXPERTISE PERSPECTIVE . A PROJECT MANAGER PLANS SPRINTS
AND BUDGET , A DEVELOPER OFFERS MORE EFFICIENT TECHNICAL SOLUTIONS , A
DESIGNER BRINGS FRESH IDEAS ABOUT USER EXPERIENCE AND CURRENT TRENDS
IN UI , AND FINALLY , A QUALITY ASSURANCE ENGINEER INTRODUCES A MORE
COMPLEX VIEW OF THE DEVELOPMENT PROCESS BASED ON HIS EXPERIENCE IN
TESTING VARIOUS APPLICATIONS . HE CAN FORSEE AND PREVENT CERTAIN PROBLEMS
IN APP USAGE OR ISSUES WITH INTEGRATION AND COMPATIBLE OF DIFFERENT SER
VICES ETC. CHANGING ANYTHING IN DESIGN OR TECHNICAL IMPLEMENTATION AT
THE PLANNING STAGE ISN’T PAINFUL . BUT WHEN PROBLEMS ARE DISCOVERED IN
THE READY PRODUCT , CHANGES CAN END UP COSTING QUITE A BIT . BY PARTICIPA
TING IN PROJECT DISCUSSIONS AND PLANNING , A QA TEAM CAN BETTER UNDER
STAND THE SCOPE OF THE PROJECT AND FORSEE AND REDUCE POSSIBLE RISKS .
THE RESULTS OF THIS PHASE ARE DETAILED REQUIRMENTS AND AN EXACT ROAD-
MAP FOR THE WHOLE DEVELOPMENT .
 Date: 01-08-2020

2. PLAN AND RECORD YOUR TESTING PROCESS :

SOMETIMES , IT SEEMS LIKE PLANNING THE TESTING PROCESS IS A COMPLETE WASTE
OF TIME. A QA TEAM MAY THINK THEY CAN QUICKLY TEST A PRODUCT’S FUNCTION
ALITY AND INTERFACE INTUITIVELY OR ON THE GO . BUT EVEN SO , PLANNING IS ONE
OF MAIN QUALITY CONTROL BEST PRACTICES , ESPECIALLY WHEN IT COMES TO COM-
PLEX PROJECTS . THE QUALITY CONTROL PROCESS SHOULD START WITH WRITING
TESTING DOCUMENTATION . THIS DOCUMENTATION IS OFTEN A CHECK LIST OF WHAT
REQUIRS TESTING . THE DOCUMENT ALSO LISTS OUT THE TOOLS NEEDED TO RUN
PROPER TESTS , REQUIRED DEVICES AND ENVIRONMENTS , AND ACCEPTANCE CRITERIA
THAT DEFINE WHETHER THE FINAL PRODUCT CORRESPONDS WITH CUSTOMER’S
INITIAL GOAL . PROPER PLANNING ALLOWS THE QA ENGINEER TO PREPARE FOR THE

TESTING PROCESS . FINDING OUT THAT SOME TESTING DEVICE IS MISSING AT THE
START OF A TEST AUTOMATICALLY MEANS THAT A TSET HAS FAILED . IF THAT
HAPPENS , YOU WILL HAVE TO WAIT UNTIL THE REQUIRED DEVICE IS RECCIVED
( WHICH CAN TAKE SEVERAL DAYS ). MEAN WHILE , THE NUMBER OF UNTESTED
FEATURES AND BUGS GROWS . LATER THE QA ENGINEER CAN CHECK THE TESTS
HE HAS FINISHED AND MAINTAIN CONTROL OVER THE PROCESS . TESTING DOCUMEN-
TATION IS ALSO VERY HELPFUL FOR NEW MEMBERS JOINING THE TEAM . THEY CAN
QUICKLY JUMP INTO THE QUALITY ASSURANCE PROCESS .

3. TEST DRIVEN DEVELOPMENT :

TEST DRIVEN DEVELOPMENT IS A TYPE OF AGILE SOFTWARE DEVELOPMENT METHO
DOLOGY THAT’S BECOME ONE OF THE MAIN PRINCIPLE OF EXTREME PROGRAMMING .
IN ORDER TO ACHIEVE THE HIGHEST QUALITY PRODUCT , EXTREAME PROGRAMMING
VALUES FREQUENT RELEASEES IN SHORT DEVELOPMENT CYCLES , EXTENSIVE CODE
REVIEW ( OFTEN ACHIEVED THROUGH PAIR PROGRAMMING ) AND UNIT TEST THAT
COVER ALL THE CODE . BUT, TEST DRIVEN DEVELOPMENT IS ALSO USED AS A SEPERATE
APPROACH PRODUCING THE HIGHEST QUALITY CODE IN THE SHORTEST AMOUT OF
TIME . ADDING OR CHANGING FUNCTIONALITY STARTS WITH WRITING A TEST THAT
COVERS THE DESIRED CHANGE . AFTER THAT , CODE IS WRITTEN TO PASS THE INITIAL
TEST . IT IS CONSIDERED A GOOD PRACTICE WHEN A DEVELOPER WRITES TESTS FOR
HIS OWN CODE . WHEN HE DOES THAT , HE UNDERSTANDS REQUIRMENTS FOR A
NEW FUNCTIONALITY AND DEVELOPS IT TO PASS THE TEST . SO LETS DISPEL THE MYTH:
SOFTWARE TESTING BEGINS BEFORE ACTUAL PROGRAMMING , A DEVELOPER IS LURED
INTO TO WRITE THE TEST TO FIT EXISTING CODE , NOT VICE VERSA .

4. OBLIGATORY CODE RIVEW FOR EVERY INGLE FEATURE :

ACCORDING TO QUALITY ASSURANCE METHODS , DEVELOPMENT FOR EACH NEW
FEATURE SHOULD START IN A SINGLE BRANCH. THIS APPROACH ENABLES TO
FOLLOW CHANGES AND TEST THEM LOCALLY . BEIDES , THE DEVELOPMENT TEAM
CAN USE THESE CODE REVIEWS TO ENSURE EVERYTHING WORKS AS IT SHOULD
WITHOUT BREAKING THE READY FUNCTIONALITY . WHEN THE FEATURE IS PROGRA-
MMED , IT SHOULD GO THROUGH AN OBLIGATORY CODE REVIEW CONDUCTED BY
 Date: 01-08-2020

ANOTHER MEMBER OF A TEAM . CODE REVIEW HAS ONE CLEAR AIM : TO FIND ANY
WEAKNESSES THAT COULD HAVE BEEN OVERLOOKED DURING INITIAL DEVELOPMENT
TO IMPROVE OVERALL CODE QUALITY . INVOLVING SOMEONE ELSE IN CHECKING
YOU ARE QUESTIONING YOUR EXPERIENCE AND SKILLS . A VIEW FROM ANOTHER
PERSPECTIVE IS BENEFICIAL . IT ALLOWS YOU TO DISCOVER OBVIOUS WEAKNESSES
YOU OVERLOOKED IN THE CODE AS YOU FOCUSSED ON SOLVING AN IMPORTANT
PROBLEM . BESIDES , THIS APPROACH WILL ENABLE YOUR COMPANY TO DEVELOP
AND ADHERE TO ITS UNIQUE CODING STANDARD . AS A RESULT , THE CODE BECOMES
WELL STRUCTRED AND UNDERSTANDABLE FOR ALL TEAM NUMBERS .

5. DO NOT NEGLECT INTEGRATION TESTING :

A FEATURE MAY BE TESTED IN ISOLATION AND PERFORM SEAMLESSLY , BUT AFTER

MERGING IT WITH THE REST OF THE PRODUCT , IT MAY BREAK EVERYTHING . THAT’S
WHY INTEGRATION TEST ARE SOMTHING YOU SHOULD NEVER NEGLECT .
IT IS ALSO IMPORTANT TO CONDUCT ENVIRONMENT TESTS . A FEATURE MAY WORK
SEAMLESSLY IN THE TESTING ENVIRONMENT , BUT MINOR OR MAJOR BUGS MAY
APPEAR WHEN MOVING TO PRODUCTION . INTEGRATION TESTING IS ESPECIALLY
VALUABLE WHEN TWO SEPERATE TEAMS ARE WORKING ON FRONTED AND BACK-
END DEVELOPMENT . SOMETIMES , PUTTING THIS PARTS TOGETHER RESULTS IN AN
ERROR . THE REASON FOR THIS ERROR COULD PROVE QUITE MINOR AND TOTALLY
UNPREDICTABLE . FOR , EXAMPLE , DIFFERENT DATE FORMATS USED BY FRONTED AND
BACKEND DEVELOPMENT TEAMS TO A LACK OF COMMUNICATION MAY CAUSE A
HIDDEN ERROR YOU CAN’T SAY A FEATURE IS READY UNTIL’S IT BEEN TESTED AS A
PART OF THE WHOLE PRODUCT .

6. AUTOMATE WHEN POSSIBLE :

USUALLY , EVERY FEATURE SHOULD BE TESTED MORE THAN ONCE . IDEALLY , A TEST
SHOULD BE CONDUCTED WHENEVER SOMETHING IS CHANGED OR ADDED . AUTO-
MATED TESTING CAN HEPL YOU AVOID MONOTONOUS MANUAL WORK , ESPECIALLY
WHEN IT COMES TO REGRESSION TESTS , WHICH SHOULD BE REPEATED FREQUENTLY .
IN THIS CASE , YOU PROGRAM SOFTWARE TO AUTOMATICALLY PERFORM THE ACTI-
ONS NEEDED TO PROVE THE QUALITY OF THE DEVELOPED PRODUCT . AUTOMATED
TESTS HAVE A LOT OF ADVANTAGES , LIKE AN ABILITY TO TEST SEVERAL PRODUCT
AT THE SAME TIME ON DIFFERENT DEVICES , AN ABILITY TO TEST OUTSIDE OF
WORKING HOURS EXTREAMLY PRECISE TEST RESULTS , AND MORE KNOW, HOWEVER ,
THAT PREPARING AUTOMATED TESTS DOES TAKE MORE TIME THAN MANUAL
TESTING AND THIS REQUIRS SPECIFIC AUTOMATION TESTING TOOLS , MOST OF WHICH
ARE PAID . SO , MAKE SURE THAT YOU AUTOMATE ONLY IF IT IS REALLY WORTH IT .
USUALLY , IF A SINGLE TEST CASE NEEDS TO BE EXECUTED MORE THAN TWICE , IT IS A
GOOD CANDIDATE FOR AUTOMATION . CAREFUL PLANNING OF TESTING PROCESS
WILL ENABLE YOU TO MAKE THE MOST OUT OF TEST AUTOMATION .

7. KEEP IN MIND USER EXPERIENCE :

 Date: 01-08-2020

THE QA ENGINEER MUST PRIORITIZE END USER EXPERIENCE OVER PREFERENCES

OF THE CUSTOMER OR VIEW OF THE DESIGNER . A GOOD QA ENGINEER FORGETS
THE LATEST TRENDS AND INSTEAD FOCUSES ON THE EXPERIENCE SOFTWARE USERS
SHOULD RECEIVE . TO UNDERSTAND WHAT THE USER EXPECTS FROM APPLICATION ,
IT IS IMPORTANT TO BUILD A BUYER PERSONA IN THE DISCOVERY STAGE . A BUYER
PERSONA IS A DETAILED DESCRIPTION OF YOUR IDEAL USER AND THEIR HABITS AND
PREFERANCES . THIS INFORMATION WILL HELP YOU BUILD A PRODUCT YOUR TARGET
AUDIENCE WILL APPRECIATE . WHEN IT COMES TO TESTING , A QA PROFFESIONAL
SHOULD WALK THROUGH THE WHOLE APPLICATION FROM THE POINT OF VIEW OF

THE END USER . FOR EXAMPLE , IF THE PRODUCTS TARGET AUDIENCE IS ELDERLY
PEPOLE , IT IS IMPORTANT TO PAY ATTENTION TO BUTTONS SIZE AND TEXT READ-
ABILITY . IMAGINE WEATHER YOUR GRANDMA WOULD BE ACQUAINTED WITH ALL
GESTURES REQUIRED IN AN APPLICATION . MAYBE , IT WOULD BE BETTER TO GIVE UP
ALL SWIPES AND MAKE THE INTERFACE AS SIMPLE AS POSSIBLE ?

8. ASK QUESTIONS :
SOMETIMES WE AVOID ASKING QUESTIONS BECAUSE WE’RE AFRAID OF LOOKING
STUPID . BUT IN SOFTWARE DEVELOPMENT AND QUALITY ASSURANCE PROCESS ,
THERE’S NO ROOM FOR BEING SHY OR TOO SELF CONCIOUS . COMMUNICATION
IS THE KEY TO A SUCESSFUL PRODUCT . A QA ENGINEER SHOULD COMMUNICATE
WITH THE REST OF THE TEAM , AND THE ENTIRE TEAM ( AND NOT JUST THE PM )
SHOULD COMUNICATE WITH THE CLIENT . THE MORE OFTEN YOU COMUNICATE ,
FLOWS FREELY , ALL QUETIONS ARE ANSWERED IMMEDIATELY AND THERE IS TIMELY
FEEDBACK . AS A RESULT , THE CLIENT AND THE DEVELOPMENT TEAM MOVE TOGETHER
TOWARDS THE END GOAL MUCH MORE EFFICIENTLY AND BYPASS MISUNDERSTAN-
DINGS.
9. KEEP THE WHOLE TEAM UNDER ONE ROOF :
SOMETIMES , A CLIENT WANTS TO SAVE MONEY BY HIRING SEVERAL PROFFESIONALS
WITH DIFFERENT EXPERTISE AND FROM DIFFERENT COUNTRIES AND TIME ZONES TO
WORK ON A SINGLE PROJECT . SUCH AN APPROACH NEGATIVELY AFFECTS COMMUNI
CATION , TASK ASSIGNMENT AND EXECUTION . IF A TEAM MEMBER NEEDS CREDEN-
TIALS FROM COLLEAGUE WHO WORKS IN ANOTHER TIME ZONE , HE MAY HAVE TO
WAIT FOR SEVERAL HOURS . THE WORK IS PAUSED , BUT MONEY KEEPS FLOWING .
INSTEAD OF REDUCING THE BUDGET , THE CLIENT THEN MUST FACE DEADLINE BREAKS
AND UNEXPECTED EXPENES . AND , AS WE ALL KNOW , POOR COMUNICATION RESULTS ,
IN QUALITY ISSUES . THE BEST OUTCOMES OCCUR WHEN THE WHOLE TEAM WORK IN
ONE PLACE . EVEN IF THIS MAY SEEM MORE EXPENSIVE , IN THE LONG RUN , YOU WILL
SAVE A LOT OF TIME MONEY AND BRAIN CELLS .