Skip to main content

Multitasking in Scrum teams

Let me invite you to perform the following exercise taken from Essential Scrum (Kenneth S. Rubin). Grab a piece of paper and a pencil, draw two identical tables as shown in the figure below, and complete them with two different strategies: row-at-a-time (a, 1, i, b, 2, ii, c, 3, iii, ...) and column-at-at-time (a, b, ..., j, 1, 2, ..., 10, i, ii, ..., x). Don't forget to time yourself!
The average results are 35 seconds for the row-at-a-time table, and 16 seconds for the column-at-a-time table. In addition, the first table has more chances to have errors.

The first table represents multitasking, where we are continuously switching from one task (column) to another, while the second table is single tasking (we don't start with the next column until we have completed the previous one).

The meaning of this experiment is that working on too many items at the same time involves a high level of over-head. Similarly, working on too few items at the same time is also wasteful, leading to idle workers and less value being delivered during the sprint. Finding the balance is not always easy, and it requires several sprints in order to determine the optimal workload for each team member.

The same applies at a project level. In this chart taken from the same book (extremely recommended for people interested in Agile and Scrum frameworks), we can see how the team members' performance decreases when they are involved in more than three projects at the same time.
When we are working on two projects, the time that we spend doing value-adding work is often the highest. The reason is that we can get blocked on one project but we still can switch to the other one.

However, with more than two projects our productivity falls because you cannot be fully committed to so many teams, and commitment (and not involvement) is one of the keys to success on Scrum teams. In the figure below we can see the difference between committed team members and involved ones.



Popular posts from this blog

How to disable cookies on Google Analytics so that you don't need a consent banner

The integration of Google Analytics into a website or blog is not GDPR-compliant by default . You must first obtain explicit consent of the end-users to store cookies, describing in your privacy policy how you intend to use collected personal data. This is the reason why most websites nowadays display an annoying (but necessary) consent banner. If you fail to do so or if you only ask for implicit consent, you are at risk of being fined. However, it is possible to disable cookies on Google Analytics (GA) respecting end-users privacy, so that you don't need to ask for consent. The downside is that you will not be able to distinguish the type of user (unique vs new vs returning) and you will miss some session insights. If these details are not relevant for you, here is how you do it. Disable Google Analytics cookies on a custom website If you have a custom website with full access to the source code, you can simply insert the script below between the <head>  and </head>...

How to convert a PWA into an Android app in 5 minutes

In early 2021 I developed a memory game called Kobadoo  as a PWA (Progressive Web App) using ReactJS. It works pretty well as a browser game and gets decent traffic, but I wanted to reach more potential users by making it available on the official mobile app marketplaces. Since I didn't want to spend any time coding a native app, the easiest solution I found was to convert the PWA into a TWA (Trusted Web Activities) app. It barely takes 5 minutes to do it. TWA essentially allows you to easily create an Android app ( .apk file) that displays a full-screen browser view of your PWA. The user experience is almost identical to a web app and the views from the TWA will count as traffic on your web app. This means that if you have ads on your PWA, they will still work (and generate revenue) from the TWA. Another advantage is that every update you make on the PWA will be immediately reflected on the TWA without the need to submit a new version on Google Play. Here's how I convert...

How to change a post thumbnail in Blogger

If you have ever published a post on Blogger with more than one image on it, you might know that the featured image  (also called post thumbnail ) that is displayed in your blog's landing page is always the first image in the post. Blogger does not provide an editor tool to change this thumbnail. However, there is a workaround that will enable you to set the image you want. Find the Image URL. You can do this by right-clicking on an image of your choice from your browser and selecting Copy image address . Note that it can be any image that is publicly available on the Internet, not only from your post. Changing your post HTML code. From Blogger editor tool, click on the pencil, then select HTML view . Add the following line at the very start of your HTML code: <img src=" https://www.example.com/image.png " style="display:none;"/> where the URL in red is the one you copied in step 1. Click on Publish . That's it! The chosen image will be displayed as ...