#ef7e12

How Do We Prioritize Tasks in HEY!, Our Agile Working Model?

 

 Tankut Hasbaş - Allianz Türkiye // Agile Coach

Prioritization is a decision-making process that walks along with us at every moment of life, always reminds us of itself, and we do not love it much.

Whether you're splitting the state budget, building a portfolio of projects, or making a weekend to-do list, there's no one right way to prioritize. Therefore, it is not possible to please everyone with the list you have made. Remember, you are not pizza.

At this point, what needs to be done is not to find the golden formula, but to develop a method, observe the results, and achieve a standard. As a result, we need prioritization because there is a limit to what we can do.

You Know I’m Something of an Agile Myself

Before we talk about prioritization in project management, let's examine team types.

We can consider agile teams in two different ways: according to the speed and continuity of producing output.

Teams in the first group design/deploy a system from scratch, and their output can be considered as a longer run. When they have fulfilled their scope or purpose, they have completed the job.

The second group, on the other hand, constantly tries to improve an existing application or business, or they produce frequently with short-term efforts.

To understand the first type of teams, think of the question "What do you want to be when you grow up?" As it is wrong to make definite judgments about the career path of a child who has not yet started school, in the scope of agile project management, deciding on final designs for the target product in the first steps are just plain wrong.

Let's exemplify the second type of agile teams with the following question: “What am I going to do on the weekend?” On weekends, we usually have time for two types of activities. Things that are "important" to do, that is, things that will make your spouse, child, or yourself happy when done. The other is "things that will support you to achieve your medium term goals" (learning a language, taking private classes, doing sports, etc.).

Here we have shown you HEY! with examples from daily life. While determining the priorities in our sprints, just like in these examples, we look at some variables: while we place urgency or importance on one axis, we measure how well the demand serves the purpose of that team on the other axis.

Image removed.

What are we going to do in the projects?

What follows is for those who want to dig deeper into the subject and learn how things work in HEY!.

We create two different types of backlogs while conducting projects and creating the agile teams: Product and Sprint. The Product Backlog is like the source of a stream, where all the developments of the project are located. Sprint Backlog, on the other hand, is the area where we plan to deal with which works and at what stage. And abracadabra, the moment has come: We will prioritize.

In the product backlog, we first group the user stories and evaluate the compatibility of the epics with the project purpose or the main strategy. The method we will use may be the MoSCoW analysis. That is: Must, Should, Could, and Won't Have. The priority issues, of course, are "Must". While determining this, our focus is sometimes on the customer and sometimes on a stakeholder of the project.

Then comes the question of which tasks will we run first in the next sprint. Here, we evaluate user stories by the MVP** approach and prioritize stories with features that will contribute the most to the result.

Let's draw a 2x2 matrix and define one axis as urgency and the other axis as contribution, with this matrix being kept alive and following the developments from here, a dynamic prioritization method has already been prepared.

Moral of the story: There is not a single true way!

One of the benefits of HEY!, our working model in which life goes on fast, work is done efficiently, and everyone in the team is empowered from A to Z, is constantly trying to strengthen our prioritization ability. Listening to the feedback on the results of the decisions, monitoring the performance of the completed requests, or learning from the missed opportunities or the risks caused by the requests that are not prioritized always show us that there is no single truth and that learning is a never-ending journey.

**MVP: Minimum viable product.

P.S. You can contact us by clicking here to share your experiences and ask questions about the agile working method.

Comments

Image CAPTCHA
Enter the characters shown in the image.