Defining the API lifecycle in a modular, reusable, and machine readable way that can help others learn about what the API lifecycle could be, as as define their own evolving API lifecycle.
I am really curious if this one can be pulled off across all of a team's APIs, calculating velocity and change, quality, governance, and other elements, then give them a performance score. This one is pretty lofty, but would be fun to explore.
I am really curious if this one can be pulled off across all of a team's APIs, calculating velocity and change, quality, governance, and other elements, then give them a performance score. This one is pretty lofty, but would be fun to explore.