Scrum what? Scrum who?

Why you should follow the SCRUM methodology

We follow the SCRUM methodology at EntityOne, the company I work for, as much as we can. The biggest challenge is that we deliver services (we are a Drupal agency). 

In my opinion it's easier to implement the SCRUM methodology in a company that creates products. That doesn't mean it's impossible.

After obtaining my Scrum Master Certification at the Scrum Alliance we started to implement the SCRUM methodology.

Scrum Master certification
My Scrum Master certification

Sprints

We work in sprints that have a duration of two weeks. When we start a new project we spread it over multiple sprints in planning. After every sprint we make sure we have a deliverable that the project owner or client can test and we can work with their feedback to improve it.

User stories

Every project has multiple user stories. A user story is a deliverable that will be tested by the project owner or client. An example of a user story for a website could be the "Blog" functionality.

Tasks

Every user story consists out of multiple tasks.

For the User story "Blog" functionality for a Drupal 8 website the tasks could be:

  • Create a content type called blog to create blog items
  • Create a view with a list of blog items
  • Create a filtering by month on the list of blog items
  • Theme the blog overview
  • Theme the blog detail

Every task will:

  • Have to be assigned to a team member
  • Have a category (ex. project management, development, configuration, theming, ...)
  • Have a status (ex. todo, in progress, done)

Every team member can see all his/her tasks in our intranet with the category and progress. 

Scrum board

We have a physical scrum board that holds all the stories and their tasks for the active sprint. Every team member hangs his or her tasks in the status the task is in (ex. todo, in progress, done).

Scrum board
Picture of one of our scrum boards in the past.

Daily stand-up

We have a daily stand-up at 9u30. In the daily stand-up every team member gives a small summary of what he or she worked on the day before and what he or she will work on today.

If someone has a problem, for example a bug that is hard to fix or a question on how to optimize/refactor code this is mentioned during the stand-up and solved right after.

The daily stand-up is essential to keep the finger on the pulse of different projects that are in development.

Demo's and retrospective

When a sprint is done every team member shows the team what he or she has been working on. This is also a good time to share tips & tricks or lessons learned during the previous sprint.

After the demo's we have a retrospective exercise. this is important to keep improving the way we work on projects and in team. If you are interested in retrospective exercises, a large list can be found here.

Conclusion

Everyone embraced SCRUM from day one at EntityOne and I can't imagine how it was before we implemented it.

I strongly recommend every company that is into software development (and even other types of companies) to start working based on the SCRUM methodology.

If you have any questions or you're looking for someone to introduce SCRUM into your own company? Feel free to contact me. 

Scrum

Meer leesvoer

I have been working on a Drupal 8 multisite and at some point I had to set up a new site in the structure. The...
Drupal
In this blog post you will learn how to add a theme field preprocess function in your theme.
Theming
In this blog post I show you how to login and logout from a Drupal 8 Back-end from an Ionic app
Drupal
It's quite easy to create a node with REST in Drupal 8, in this blog post I'll show you how to do it.
Drupal