Retrospectives are great! It’s a simple and structured methodology to critically assess the most recent performance in a certain period of time. Developers know it, and good scrum teams keep on improving with retrospectives to become better and better.

According to the Scrum guidelines, a retrospective typically answers the following questions:

• What went well?
• What could be improved?
• What will we commit to improve in the next sprint?

When doing retrospectives on a regular basis (like any good scrum team will do) continuous improvement is part of the process! Of course, things will only improve if actions are taken, but identifying the actions during the retrospective is the key step here.

Finally there is a new kid to the block rethinking content management from the ground up: headless content management systems. In a nutshell a headless CMS separates content from its presentation, primarily enabling content to be re-used across different forms of presentation, e.g. on a website, a mobile app, or a public info screen). As an engineer, this is a dream come true: finally it is possible to implement a consistent look and feel across any presentation as content editors cannot misuse WYSIWYG editors producing HTML garbage.