Developing with users. That is one strategy I am trying out now. But these are internal users.
There is no best way to be honest. Sometimes you just have to say, I am not here today. Or I am not here for two hours. But there can always be outside calls or meetings in between. Sometimes it is worth while to recognize the power users and learn them how to do things themselves. This will pay back eventually.
Also make sure you move enough and have time to reflect. And don't be shy to move things of your back upon others. A lot of people are willing to help.
You can follow some methodology, but in the end they are too inflexible or just not right for your situation. So oh well, just reflect day to day and you will learn the patterns.
E.g. Monday is for me meeting day. People come back from the weekend and have new ideas, so I need to talk with them and integrate it.
Wednesday is usually the day to reflect on how things go and to spew out designs and documentation.
Thursday is helping out users day, I sit with them and help them with their problems. This is very insightful. I make tickets for them and write down their problems. Sometimes we code together.
Friday is relax day, I can build a new feature and present it, people don't like to work on fridays, so I can do some hobbying.
Saturday is for deep serious work, nobody works then, so nobody is bothering you. I have Tuesday free.
But this pattern changes often. Sometimes it is just busy. You just have to ride the storm.
There is no best way to be honest. Sometimes you just have to say, I am not here today. Or I am not here for two hours. But there can always be outside calls or meetings in between. Sometimes it is worth while to recognize the power users and learn them how to do things themselves. This will pay back eventually.
Also make sure you move enough and have time to reflect. And don't be shy to move things of your back upon others. A lot of people are willing to help.
You can follow some methodology, but in the end they are too inflexible or just not right for your situation. So oh well, just reflect day to day and you will learn the patterns.
E.g. Monday is for me meeting day. People come back from the weekend and have new ideas, so I need to talk with them and integrate it.
Wednesday is usually the day to reflect on how things go and to spew out designs and documentation.
Thursday is helping out users day, I sit with them and help them with their problems. This is very insightful. I make tickets for them and write down their problems. Sometimes we code together.
Friday is relax day, I can build a new feature and present it, people don't like to work on fridays, so I can do some hobbying.
Saturday is for deep serious work, nobody works then, so nobody is bothering you. I have Tuesday free.
But this pattern changes often. Sometimes it is just busy. You just have to ride the storm.