Focus on goal, not on tasks.

By -

Hi, I had a problem with plan my life. Why? I did a lot of tasks every day, but I still stand in the same place. I change my mindset and it is working now. I change a lot of tasks to goal. This method can be used in Scrum, so I want to share you my think.

Difference

I am starting from show you my definitions of task and goal.

The goal for me is the result, which I want to get. For example: I would like to write the application for team cup foosball using Django.

The task for me is the piece of way to get the goal. For example: Watch tutorial for creating an application using Django or prepare use cases for application.

Why goal is better?

Goal has a value. We should focus on a goal, because when we get that we get a value. Of course, sometimes our tasks have the values too, but the core of value is in goal. The value for a lot of tasks is our goal. Example: I want to watch tutorial for creating an application using Django, because I would like to write the application for team cup foosball. Yes, it have the same advantage in this case, but the goal has another else.

The second reason, why I like goals, is that I can change my tasks during getting the goal. A lot of times I change my mind, during getting the goal. This is a natural process, because we have more knowledge after each task. Sometimes, when I do automatically my tasks, I forgot to think about why I did it. I didn't stop and think about my solution. I had the tasks and I focused on the tasks. This is not agile. Now, I every day focus on my goal. I can measure where am I, because I know what I want on the final state. Of course I prepare some tasks to do. I have a global vision how will I do it, but this task and my vision are evolving over time. Sometimes my goal is changed too, because my knowledge is better. Sometimes I think that I don't want it anymore. When I do the tasks, I get the information about it later than I focus on the goal.

Sometimes task is better

The tasks is better when you delegate something to other people. This is easier, when you tell him what you want. This can be working with a small group of people, because you should spend a time with each person. Your time is limited, so you shouldn't waste it. Sometimes we must make a task for other people, because we know that domain of the problem is very complex and complicated. If you know that person doesn't manage with a goal, you should help him with tasks. This is a topic for another post, but I hope you understand me.

Summary

Focus on the goal is more flexible and this way is more agile. I see a value of this way and I am using it every day. Such as I mentioned the tasks is easier to delegate to the other person (often with less knowledge of the domain). You should remember that when you are delegating the task that you should support the person who do it.

Comments

Post a Comment

Popular posts from this blog

Why TDD is bad practice?

By -
Image
Did you listen that TDD is bad? What do you think about it? I have my opinion about it! TDD is bad because... We don't have time to write tests first - I think this is a good point. I sometimes don't have time for that. Why? Because I need to do quickly fix on our code and deploy it. In this case I don't have time to create test after wrote production code too. The even worse case is when we have tested this part of our code and test after change doesn't work. I don't like this, because I must read tests and thinking about repair tests for new logic. I really don't like this. I would like to create new test and remove old every time when I have that situation. What's wrong with the test first on this case? Nothing, because if you have time to write tests after create code, you have time to create test before it. Don't you think so? We know how will implement it, but we don't know how testing it - I think a lot of developers have this problem,
Read more >>

How correctly imitate dependencies?

By -
Image
This is continuous of my previous post about why we should imitate our dependencies. I did it not long ago. I though about how do it properly and when I can say that it is correct. Start from test and real dependencies I am starting from the tests. I wrote the simple tests which, I though, are correct. That was my learned about dependencies. I had the good situation that I had some prepared tests before. During the writing test I got a knowledge. A lot of time, I verified what the system return. After it, I got the full automated tests for my dependency. Now, I am sure that dependency works like I think. Like my test use it. I think this is a very good advantage. Extract the interface for communicating The implementation to communicate is implemented and tested. Our test, if you implement it like functionality test, not code test, should show us, how we want to use our dependency. We know what parameters we use, what methods. We know what we want. That is a place where we must extr
Read more >>

Software development using Angular 5 with Spring Boot

By -
Image
Hi everyone. My last the bigger post is about configuration Spring Boot and Angular 5 . After that instruction we have integrated both technology on one app. If you created it you know that development is very hard in this case. We must waiting for build a client and it isn't effective. We can use webpack-dev-server to speed up this process, so this post is just about it. Angular and webpack-dev-server I think I have to explain webpack and webpack-dev-server. The first tools let pack our angular app to one or more files. This files is bundles. It is for improve speed of our app. Why? Because one page application need all files on start by assumption. The better way is load it using only one connection and one file, because establishing connection taking time. This is a few information about webpack, but what is webpack-dev-server? This is the tool. It serve our that files which webpack compiled, but it working on memory, so we have quick result on our browser. This is a amazing
Read more >>