Agile project management with Scrum
The Scrum method involves the step-by-step development of a product or a service in multiple cycles or iterations. Each interim result forms the starting-point for the next iteration. While this method grants project participants a lot of freedom, they also have to shoulder a lot more responsibility. There is no longer a plan that describes the entire development process from the outset, from A to Z. Instead, team members are themselves responsible for self-managing each iteration of the project, as they analyse the status quo, and then specify and work towards the target.

Teams and roles
A Scrum team has a maximum of 10 members in 3 roles.
- Product Owner:
The product owner determines the product’s functionality, while also representing the interests of customers or stakeholders in the product. - Developer:
Developers are then responsible for the technical implementation of the functional specification. - Scrum Master:
The scrum master is team facilitator and coach, and their job is to ensure team productivity while resolving problems with communication or organisation.
Scrum development process
Applying this method involves completing several iterations, known as sprints. Each sprint consists of four elements:
- Backlog:
The backlog is created and/or adjusted before each sprint and contains all of the functions that are to be implemented in the final product. - Sprint Planning:
In this phase, you record and plan the product functionality that you will be implementing during the sprint and also define the sprint goal. The sprint should not take longer than four weeks to complete. - Daily Scrums:
While working on the product, you hold daily meetings, in which each member presents their current status quo and offers up issues for discussion. - Sprint Review:
During this short review, the team checks and evaluates the iteration results. - Sprint Retrospective:
The last phase involves a meeting to discuss teamwork and how opportunities for improvement can be better utilised.