So what tools\/ingredients do you need to facilitate global team collaboration<\/a>?\u00a0<\/p>\n 1. A documented process that answers ‘how do we work’<\/strong><\/p>\n I believe this is the starting point of any global collaboration. Before the train starts driving, everybody involved needs to understand ‘how we work’. This process needs to be both documented and supported by everybody. The process also needs to be reviewed and improved continuously. It would be useful to have an online process building tool for this, which I have not found so far. Word documents also serve the purpose here.<\/p>\n 2. Project management tool<\/strong><\/p>\n An online tool that enables the team to manage everything within a project. Such tool should include separate elements for: 3. Skype or another video conferencing tool<\/strong><\/p>\n This may seem obvious but many people without experience in offshoring are not so used to skype. It’s crucial to stimulate human interaction, so the (group) video functionality of skype helps there. The team needs to see each other regularly for both bonding and project discussions.<\/p>\n 4. Time registration + reporting<\/strong><\/p>\n People sit far away so it is hard to understand what specifically they are doing. Time registration can help us out. Programmers can register the time spent on certain tasks\/bugs\/projects in an online tool, which can be reported once per week to the onshore project leader. It is also useful to have a weekly analysis of the time spent, so the people understand how and why time is spent from both sides.<\/p>\n 5. A version control system<\/strong><\/p>\n The most commonly used tools here are subversion<\/a> or CVS<\/a>. Usually, this is installed on a webserver, and people from each team commit code to the system at the end of their working day. Another, which integrates for example with Redmine, is GIT<\/a>.<\/p>\n 6. A coding standard<\/strong><\/p>\n Although this may seem logical, many companies are reluctant to have coding standards, let alone follow them. With different people in different locations working on one project or system, it’s crucial that everybody knows ‘this is how we expect you to develop software code’. The coding standard needs to be clear to everybody and it’s helpful to check the code regularly to ensure that people stick to the standard.<\/p>\n 7. An overview of responsibilities<\/strong><\/p>\n Who’s doing what? Who is accountable for what? Even if people are working in different companies, it is helpful to create function profiles that give an overview of what is expected of each person.<\/p>\n \u00a08. A performance measurement system<\/strong><\/p>\n If you are building long term cooperation with an offshore team<\/a>, it’s important to give them feedback on their performance. The best is to treat them like they are your own employees. Examples are ‘asks questions when requirements are not clear’, ‘communicates ideas for better solutions’, ‘is proactive’, ‘makes deadlines’. You can rate those on a scale of 1-10. It’s also useful to ask the offshore team to give you feedback on certain factors (e.g. provides clear task specifications, communicates expectations clearly, assists in technical problems). It is helpful to use an online survey tool (e.g. SurveyMonkey<\/a>, Typeform<\/a>, etc.) or use some custom-built system for this.<\/p>\n With such tools and systems in place, the work is facilitated. Behavior gets structured, feedback is given and the team gets a feeling of ‘control’. And still, there is a lot of space for human behavior to deviate from the expected behavior. Maybe you have some tools or methods that you can add to this list?<\/p>\n Meanwhile, you want to read about some effective tools for Agile project management here<\/a>.<\/p>\n![\"\"](\"https:\/\/www.bridge-global.com\/blog\/\/wp-content\/uploads\/2012\/04\/IMG_0708-300x200.jpg\" "\\"IMG_0708\\"")
<\/a><\/p>\n
\na. Storing requirements documents
\nb. Managing tasks
\nc. A bug tracker
\nd. A planning module to plan and track progress
\nSome popular project management tools are: Redmine <\/a>and Jira<\/a>. More simple bug trackers include Bugzilla <\/a>and Mantis<\/a>.<\/p>\n
![\"\"](\"https:\/\/www.bridge-global.com\/blog\/wp-content\/uploads\/2012\/04\/Capture.png\")
<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"