When you are developing/debugging a provider hosted (high-trust app for SharePoint) in Visual Studio, the remote web application is hosted in IIS Express on the machine where Visual Studio is installed. So the remote web application computer doesn't have an IIS Manager where you can create the certificate. For this reason, you use the IIS on the SharePoint test server to create the certificate
So each of team member should use self-signed certificate of their own development server (see how to do it). As long as team members share SAME naming conventions for e.g. certificate name, IssuerID and Client Signing password, you can easily develop/debug apps and work like a team using TFS/version control.
ClientID is something to be taken care by Visual Studio itself, so don't worry about it.
<add key="ClientId" value="463e7dff-b7cd-4f48-b846-8c5ce67f5efd" />
<add key="ClientSigningCertificatePath" value="C:\cert\SomeCertficate.pfx" />
<add key="ClientSigningCertificatePassword" value="SomePassword" />
<add key="IssuerId" value="Some-GUID" />