In order for every team member to use their own set of tools, the team and stakeholders need to define the properties and qualities of the artifacts they require. As long as the artifacts provide the required properties and can be used in following processes seamlessly, it is not important how the artifacts are created. The artifacts need to be accessible for interested stakeholders via a single point of access.

An artifact is the result of a work process. It may be used directly by a stakeholder or may be the input for another process. Properties of artifacts especially include the format of an artifact. For instance a user manual for a product may be a large PDF or a website with multiple HTML 5 pages.

Companies may define a set of tools that they support while not prohibiting to use other tools. This would help team members without prior knowledge or team members who are indifferent of which tool to use for a particular job to get started quickly.