A personal view on Agile, Scrum, IT and other related topics
As Agile Coach it’s a good practise to have a quick and simple reference on your hand to teach and coach your teams. In this post I added my most valuable links and references for Agile Teams and their Coaches. I see these links as part of my (online) Agile Toolkit.
As Scrum Master, it’s expected from you to be a teacher, mentor, coach and change agent in an organization. Videos help to teach the teams and organization about Scrum, Agile and related subjects.
In this edition, I selected videos about personal behavior, motivation and creating a positive working environment. These subjects are important for creating high-performance teams. Other videos are product management and ownership. The last video is about #NoEstimates, an upcoming movement in the Agile world.
Featured / Retrospectives / Scrum
by Johan Moens · Published October 3, 2018 · Last modified October 22, 2021
Maybe you wonder how to boost your Scrum Team in improvement. The Catapult and Defining Nirvana could be the retrospective formats to use. In this article, I combine them into a single format.
Development / Featured / Scrum / Testing
by Johan Moens · Published September 5, 2018 · Last modified January 13, 2019
These days businesses focus more and more on Continues Integration and Continues Deployment in the Agile / DevOps world. The urge of businesses to update their software more often results in more time pressure on testing the software. An answer to this problem is Test-Driven Development (TDD).
In this article I talk about what TDD is and what the method looks like.
Featured / Retrospectives / Scrum
by Johan Moens · Published February 9, 2018 · Last modified January 7, 2021
In this article I’m going to talk about the retrospective format “Fly High”. The retrospective helps the Development Team to think of impediments that block the team to deliver more value for the business.
The Fly High retrospective has three parts. Things that go well, team-level impediments and organisational-level impediments.
Certification Authority Authorisation (CAA) allows a DNS domain name holder to specify one or more Certification Authorities (CAs) authorised to issue certificates for that domain. This way a public Certification Authority can implement addition controls to reduce the risk of unintended certificate mis-issue. Earlier this year a ballot passed to make CAA checking mandatory. Which means that a CA will check the authorisation before issue-ing a certificate.
This article also describes how it works and how to configure this for your domain.
This November the new version of the Scrum Guide was published. In this article I’d like to discuss the biggest changes and comments Jeff Sutherland and Ken Schwaber made in their webcast on this Scrum Guide update. The topics are Uses of Scrum, the Mastery of the Scrum Master role, Daily Scrum changes and Scrum vs DevOps.
Development / Featured / Support
by Johan Moens · Published August 3, 2017 · Last modified January 7, 2021
It’s not easy to rank defects on priority while doing Corrective or Preventive Maintenance. In this how to I set up a guide you can use based on impact, severity and urgency. Also I discuss if it’s worth to fix a defect.
Development / Featured / Support
by Johan Moens · Published July 21, 2017 · Last modified January 7, 2021
These days it’s rare to build a system from scratch. Software maintenance gets more important every day. Let’s take time to talk about the different types of software maintenance. The types of Corrective and Preventive Maintenance are for corrections on the software. Adaptive and Perfective Maintenance are the types for Enhancements on the software.
Everybody knows the problem that a User Story is just too big to handle for a Sprint. Just cutting the User Story in smaller pieces is not the way that most of the time works. SPIDR might come in handy.
Featured / Retrospectives / Scrum
by Johan Moens · Published June 21, 2017 · Last modified September 12, 2023
This article is about the Scrum Retrospective Three Little Pigs and my personal experience with it. How to and the extra benefits of this retrospective. The goal I had with the retrospective, was to look back at the past sprint, but also to talk about what goes well (bricks); what goes well most of the time, but needs improvement to get impediments out of the way on structural basis (sticks); or what subject needs further improvement (straw).
adaptive agile anti authorisation CA certificate change management corrective data defects design design patterns development DNS domain email enhancements factory fun gang of four improvement interface maintenance mocking path patterns perfective preventive product management product owner reinventing retrospectives scrum scrum guide scrum master security server singleton software spike testing unit of work user stories user story wheel