Do you know where to keep your files?
  v15.0 Posted at 3/11/2018 3:41 AM by Tiago Araujo
Creating, uploading, and sharing documents with other people should be done using SharePoint and Microsoft Teams.

In the old days, we used File Shares. Today there are so many places that teams can store documents eg. Dropbox, OneDrive, SharePoint, TFS, and even Microsoft Teams.

The solution should allow collaboration with Developers, Project Managers, and other stakeholders.

You want to be able to quickly store and locate important details such as:

  • Server details (Dev, Test, Production)
  • Changelogs
  • Upcoming features


  • Requirements/Specifications

Additional Information

  • Server settings
Keep Files Bad Example
Figure: Bad example – File Share or your Local C: or emails - they aren’t easy for others to access
Keep Files Bad Example
Figure: Bad example – Sharepoint integrated into TFS is not supported via Visual Studio anymore
Keep Files Bad Example
Figure: Bad example – even though this is using SharePoint - this is using a Team Site with a Document Library - it is better to use Microsoft Teams which uses SharePoint under the covers
Keep Files Good Example
Good example: Use Teams and it will automatically create a Site for the Team (and that includes a document library and Team OneDrive)

Note: 4 important documents should be stored in TFS.​​

For designers, see: Do you know the best Source Control for Designers?

What about usernames and passwords?

Security is very important for any company. You should use KeePass to store usernames and passwords. KeePass keeps all passwords in one database locked by a master key, which should be accessible only by the few people you trust.

Related rules

    Do you feel this rule needs an update?

    If you want to be notified when this rule is updated, please enter your email address: