Member Avatar for gk2010

Hi all,

I am hoping that the DaniWeb community might be willing to assist me in my research efforts.

I am a researcher based in University College Cork (Ireland) and I am involved in a research study on the subject of software development in global virtual teams. As part of this study I am conducting a questionnaire.

Coordination is often reported as being particularly challenging for global virtual teams engaged in software development. This questionnaire seeks to gather data relating to coordination issues in global virtual software development teams.

As experienced practitioners in software development, I would very much welcome your participation in the questionnaire. The questionnaire is directed towards any individual who has worked on a software development project as a global virtual team member. Your candid and thoughtful reply would greatly assist the evaluation. The questionnaire should take no more than ten minutes to complete. Your response will be treated as strictly confidential.

Here is the link to the survey:

Thanks again for your help.

Sincerely,

GK2010

  • 3 Contributors
  • 3 Replies
  • 310 Views
  • 8 Months Discussion Span
  • Latest Post Latest Post by jwenting

Dani AI

Generated

This thread is an older request for help with a questionnaire about coordination in global virtual software teams (original poster ; asked to see the instrument; warned about reviving old threads). Left as an archival item, it still provides an opportunity to capture a concise, practical checklist for both researchers and practitioners who land here years later.

Common coordination problems in distributed development include time‑zone mismatch, asynchronous handovers, unclear responsibilities, knowledge silos, fragile integration, and reduced conversational richness. Practical, low‑overhead mitigations that work across toolsets: agree on a single source of truth (backlog + architecture docs), codify handover and response-time norms, keep a small daily or twice-weekly overlap window for sync, use CI and automated tests to lower integration risk, standardize branch/review workflows, appoint a rotating coordinator or boundary spanner, and capture decisions in a brief decision log so newcomers can catch up asynchronously.

Notes for researchers designing similar surveys: pilot the instrument, combine validated scales (e.g., trust, coordination) with targeted open text questions, state inclusion criteria clearly, report ethics/consent and data-handling upfront, and say whether results will be shared. When posting in public forums, include a short study summary, estimated time commitment, and one clear follow-up post with outcomes — that reduces perceptions of spam and improves response quality.

A brief archival note to the thread participants: thanks to for the outreach, to for the interest, and to for the moderation reminder. If anyone updates or republishes similar work, a short follow-up here summarizing methods and key findings would make this thread genuinely useful to future readers.

Recommended Answers

All 3 Replies

Member Avatar for gk2010

Hi all,

Just a quick message to thank those of you who have completed my survey. Your responses have really helped with my research.

The survey is still open so if any of you have ever worked in a virtual team and have ten minutes to spare you would be doing me a huge favour.

Thanks a million,

GK2010.

Member Avatar for heinijan

Hi GK2010

I am writing a Bachelor Thesis about virtual teams. For that reason I would be interested in your questionnaire. Is it possible to have a look at it?

Kind regards

Edited by Ezzaral because: Snipped email. Keep it on site.
commented: zombie master +0
Member Avatar for jwenting

do your own homework, kiddo, and don't resurrect long dead spam threads.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.