- Understand authority hierarchy and responsibility with reference to Organization Chart
- Collect contact including email, office and mobile phone number of all stakeholder, user representative, specific user, front-end staff and technical user
- Make request during the project kickoff meeting
- Only record in document after getting approval from staff on personal contact information
- Contact only within office hour unless for emergency
- Some staff use extra mobile number for work communication and could be switched off after office hour, stand by contact should be mark down
- Maintain good communication with major stakeholder, especially verbal check for some operation details, exchange view on implementation flow or technical details, and get consent before writing down in document
- Willing to do extra minor tasks that does not affect schedule could help to build trust with user
- Listen to user, consider from their angle, help to analysis for them, think in more details especially for long term consideration, suggest different ways of implementation for choice
- Work all together as a team even including user, and look for solution together could have best result many times for project
- Maintain harmony as far as you could, treat positively even for any negative feedback from user and avoid to become angry. Try to find solution by careful and detailed consideration could win back confidence from client.
- Respect client custom and culture but suggest way for improvement for their best
- Too many user requirement changes could affect project target schedule
- Some issues raised by user may be due to misunderstanding and could be rejected
- Rejected issues could be re-opened again due to situation change or new discovery
- Scope is defined in tender, requirement catalog and functional specification
- Out of scope change should be Change Request which involves extra payment to do but usually user will insist they are within scope.
- Some extra task if not implement will affect the function within the original scope to work, i.e. implied duties in legal sense that vendor still have the responsibility to do even without extra payment.
- Client secret should be well protected and prevent leakage during display, transmit or storage
- Understand user preferences could make project more smooth
Categories:
No responses yet