�ݺ�ߣ

Editor's Notes

• #2: Acquaintance with auditory. Agenda + timing (1 Hour)+ QA (during presentation, however we have 5 min per slide)Short introduction about presentation This presentation will be useful either team and managers. Let us formalize what is “distributing team” - a team of people using technology to work on the same stuff but from the different places.Why we do distributing, it is much easier to have a local team – a least we need to have access to all talented people in the world, not only in your local area, in additional of course to reduce costs and reduce time-to-marker@Question to auditory – how many of you are working in distributed team? So you are those talented guys I have mentioned before 
• #3: What is distributed team, what is measure of “distributed ” Everyone who is away from the main base location feels just as much a part of the team.50 foot rule - teams on separate floors (more than 25 m apart) actually talk less than a distributed teamDistributed with different hours - 9 time zones in Russia and 4 time zones in USA
• #4: Depending on the country, there will be a social order within the workplace that should be respected and followed. Do your best to understand that prior to your first engagement with any member of that team. It will definitely set the standard for your working relationship going forward. If you are able to exhibit that knowledge, new teams will appreciate your understanding of how their team works.Example 1 : Japanese never say word “NO”, they will be “dancing” around this word however don’t say it.Example 2 : Joke:- Manager USA: Today is dead lineDeveloper RU: Yes. (Means I know it.)Developer USA : Yes (Means I will be on time with all might tasks)
• #5: Working day schedule. Tries to stick and understand work day time frame, it is very important in distribution with different hours. When you in “energizer” mode, the can be a early morning and person/people can just sleepy.Talking about vacations, illness and etc.Types of communications – preferences : mail vs voiceWorking habits. NO ONE WORKS 8 Hours per day and you should understand this. Any person browsing @/youtube/rssetc it is part of IT culture. You shouldn’t ruined it. However need to understand how to work with it.
• #6: Any new person in team/project is a dark house, even he has “senior-bla-bla” title, you should work with him like with junior team member but in very polite form– check, check and check again. His level of trust equal to zero. Any side (team/manager/BA/product owner) should to merit trust. So please don’t be a disappointed and angry when some starts work with you like with child. Just show enough maturity to increase trust level.
• #7: Any success starts from the people. Each team member should understand that he works not only with “logo image” from Skype with name Brian or Vasya, there is another person on other side, with own thought, character and “cockroaches” in his head. + Birthdays + Holidays@This SEC it is like on-site visit, so after this presentation you will know me as Anatolii (capital A) Manko (capital M), but not like anatolii_(underscore)manko@(at)epam.com. Please feel the power of in person meets.@Question to auditory – How many of use ever visited customer on-site or host clients in own offices ? How it effected you relationships with customers or team?
• #8: You need to know you stakeholders “in the face”. It is really important to understand how is big boss and decision makers or contact point.You should know this on the begging, it will safe a lot of time to ask right questions to right people.@Example - Rules of two confirmation and one “no objections”.Example: you have been included in the internal meeting in the middle of the discussion a lot of talks, no understanding about final decision and results.
• #9: If no one talks about the problem that it does not existIn case you send an email about any issue/urgent case, make sure that some one has started investigation. You need to receive reply that notification that some one has started. @Example TRF – two teams , two sets of functionality, crash – no one doesn’t do anything cause it is not their part.
• #10: Distribution projects increase communication complexity. There is a huge risk of misunderstanding. There should be a black boxes or not important parts in the project.Debuting countless hours to make decision. Do not start anything before you understand why you do this.@TRF example – Books (accounting) – what is that, what for. In case we would know about this before start implementation we wouldn’t create a lot of useless functionality.
• #11: @Question : Let us take a 1 min to look at this slide and try to remember how many issues could be solved in case these three items would be assigned to task/story.Every task should be 1) assigned 2) Estimated 3) Has acceptance criteria.Don’t forked about - task decomposition and WBS.
• #12: Always translate any verbal agreement to written artifacts. It is very important, language issue & culture issues, rush and technical talk background.Follow-ups, minutes of meetings, etc.@Example - Rules of two confirmation and one objections.
• #13: It is much better to score many small wins frequently, than one big one once.Ban news first!
• #14: Project it is a boat where all participants are crew  Some one is captain, some is navigator others are rowers and sailors. However success of the trip is lie on each member. As fast each team member will understand this as fast your boat will sail.@Managers/customers – try to introduce your business to team. Involve team in your ideas and plans, they need to understand direction and final point. Your team needs to feel like a team but not a workers.@Team, your success is a project success, try to work on project like it is your own business. It will 100% work and your customer will feel this and be loyal to you as well. ??????Employees proud to work with such names – Paypal, Sephora, Sotheby’s (refer to http://www.epam.com/company/customers.html)
• #15:  It is best to award large projects to offshore teams and divide those into small achievable milestones so your team is not insecure about where they will be earning from tomorrow. Small projects drag when awarded to offshore teams. While someone in the US will prefer a small job to the long tedious projects, the work culture of the developing world usually includes preferring mid to long term projects while short projects will very likely be dragged in hope of getting more work and increased scope.
• #16: Don’t be short of a good word or two when you talk to your team. A scheduled team huddle puts you in the midst of the team even if you are not there physically. The workers may not talk to you directly but they will listen and anyone who has ever done anything that can be referred to as ‘work’ knows appreciation lifts the spirits and makes you want to do even better next time.