Extreme Sprints represent an iterative and incremental approach for building the solution. During these short iterations, typically 2 weeks long, the team prioritizes user stories, both functional and non-functional, which represent the highest value to the Customer. Functionalities are developed, tested and demonstrated by the team, and the result of each Sprint is a complete, fully functional API and platform feature set that could be moved into production.

Activities

Outputs

Each activity performed within the Sprint cycle has a defined role
See also Best Practices for running effective Sprints

Sprint Planning

Review the priority items for the coming Sprint and review both 'What' is to be delivered in terms of business value and 'How' it will be delivered from a technical perspective.

Sprint Execution

Building the API including both development and testing to produce production ready code.
See also Forming an API Test Strategy - where to start

Review

Demonstrate the work accomplished in the Sprint and add items to the backlog reflecting the feedback received

Retrospective

Look back at the Sprint and identify what went well and what did not. Add items to the backlog to address areas for improvement and leverage what worked well.
See also The "Starfish Method" for Retrospectives