| Concern | Mitigation Using VCS | |---------|----------------------| | – “I’m not a programmer, can I still use Git?” | Use GUI tools (GitKraken, Sourcetree, GitHub Desktop) and adopt simple conventions (one commit per change, descriptive messages). Provide a short onboarding video for the team. | | Large video files – “Git is for code, not 2 GB videos.” | Store binary assets with Git‑LFS or a dedicated Data Version Control (DVC) system that tracks file pointers while the heavy files reside in cloud storage (Google Drive, AWS S3). | | Security – “Will my private health advice become public?” | Keep the repository private on a trusted service, enforce two‑factor authentication, and restrict branch‑protect rules to authorized reviewers only. | | Internet bandwidth – “My team has spotty connection.” | Enable offline commits; changes can be pushed when connectivity returns. The central repository can be self‑hosted on a local server for teams with restricted internet. |