There are cycles inside the cycles. Information has now been gathered, it’s time to learn from that. Learning needs facilitation. If you just assume that people and organisation will learn, well they will, but things may not be optimal. Not all information is utilized. Wrong things are enforced.
One of the events in scrum is retrospectives. Retrospective is an opportunity for the team to inspect itself and create a plan for improvements to be enacted during the next Sprint. In similar fashion, in cycles there is a need for organised learning/feedback session. Simple steps to take are: 1) Appoint an organiser 2) Organiser reserves time and place 3) Organiser gets people together in to the time and place 4) go at it:
- Inspect what has happened
- Identify what went well and what did not
- Make a plan for implementing improvements and plan on doing things that are going right.
In a cyclic and iterative development method learn phase varies depending on the maturity of the API product. In Protyping phase the API Consumers are different to when the API is in production. Learning can be achieved by gathering feedback or by interviewing API consumers and studying the analytics reports.
Prototyping and Building just enough
Gather requirements from your first pilot consumers and API Developers. Analytics and API Management tool gives indication of possible problems needing attention either in API documentation or in the actual Implementation.
Gather feedback from all API Consumers and API developers. Analyse the API usage and adjust you metrics to see new registrations by developers and how the amount of request develops. Consider the API Lifecycle, publish, deprecate and make plans to retire the old versions of APIs.
Gather new requirements and ideas to the API canvas and start a new round of APIOps® cycles.