Are the trail of documents and images that result from the interactions taking place in your git repository. These range from issues and pull-request to discussions and code submissions. Most organizations have a wealth of Artifacts and may not even realize it.
Have descriptions regarding architecture decisions & additional implementation details not documented anywhere else.
While having it in the repository is better than nothing, docs in repositories are not discoverable or searchable.
Contains product specifications and implementation estimates that becomes lost/forgotten after project life cycle.
Information can be scattered across multiple repos, multiple organizations.
Needs Work (3/10)
Some docs in place varing in quality:
Needs Work (3/10)
A preliminary standard has been defined in one repo, adoption needed across the org.
Decent (5/10)
Healthy artifacts container in: core-platform, sphinx, & ML-Data.
Organization Grade: (11/30) 33% F+
Good (9/10)
Defined standard applied across all repos.
Good (8/10)
Some artifacts in place varying in quality:
Good (9/10)
Defined standard applied across all repos.
Organization Grade: (26/30) 86% B