Written communication (emails) to Team 1) Emails correspond to Communication Guidelines principles. 2) Clearly describing technical issues, solutions, cause -effect chains and other complex information in the emails. 3) Presenting information and facts in a logical, honest and clear manner.
Written communication (emails, IMs) to Client 1) Writing emails to client in polite manner and avoiding technical jargon, etc. 2) Clearly describing technical issues, solutions, cause -effect chains and other complex information in the emails. 3) Presenting information and facts in a logical, honest and clear manner. 4) Adjusting own communication to the target audience (technical/non-tecnical, cultural context).
Conference calls with Client 1) Driving conversation with client. 2) Actively participating in conference calls.
Project meetings planning outcomes 1) Planning technical meetings and agenda. see upper comment 2) Creating and assigning action items, agreed during technical meeting.
Project meetings (SCRUM meetings etc.) 1) Taking active part in all project-related meetings. 2) Keeping focus of discussion on meeting agenda. 3) Providing valuable contribution into development of shared vision and making group decisions.
Presentation 1) Delivering well organized, informative and take part in DevTalks, Octopus AI comprehensive presentations of technical solutions, methodologies, and approaches. 2) Preparing all needed environment for presentation delivery. 3) Responding to unexpected questions skillfully.
Attitude
Initiative 1) Suggesting ideas to resolve existing issues. 2) Providing suggestions on improving current processes or creating something new without being told to, but agreed with senior staff.
Self-improvement 1) Showing permanent drive for self-improvement (reading books, blogs, articles, attending internal trainings, etc). 2) Setting personal example of self-improvement and focusing on excellence. 3) Following recommendations, provided by uppermanagement/ mentor, and/or self-improvement plan.
Result-orientation responsibility 1) Accepting ownership of and responsibility for own work. 2) Accomplishing the assigned tasks in compliance with a schedule. Escalating appropriate issues to upper management. 3) Sticking to priorities defined by uppermanagement. 4) Being focused on achieving positive outcome rather than on process. 5) Demonstrating flexibility and willingness to align personal work capacity to meet project goals. 6) Responding to requests timely and effectively.
Business-orientation: 1) Working with clients, identifying their needs, setting and managing client expectations. 2) Acquiring good knowledge of client domain and suggesting opportunities, which may help to satisfy client's business need. 3) Continuously seeking for client feedback, adapting of provided services and solutions to meet client needs. 4) Keeping reasonable balance between technical attractiveness of proposed solutions and client business needs.
Team work
Knowledge sharing 1) Sharing professional knowledge to team members (as outcomes from trainings, seminars, preparation to certification, books etc.). 2) Adding professional knowledge to project space (Confluence, wiki etc.).
Cooperation and collaboration 1) Working collaboratively rather than competitively. 2) Dealing honestly and fairly with others, showing consideration and respect, even in conflict situations. 3) Meeting commitments to other team members.
Leadership
Team motivation 1) Recognizing publicly achievements of team members. 2) Inspiring co-workers to attain goals and pursue excellence. 3) Guiding staff to achieve tasks, goals, processes and performance standards.
Mentoring 1) Creating mentorship plan approved with upper management. 2) Defining and assigning training tasks to mentees. 3) Recommending ways for improvement and training materials. 4) Reviewing work and providing regular reasonable feedback to mentees.
