Looking back at projects I have been a part of in my work life there are some that have been successful right away, some that have needed more time to be successful, and some projects, well they haven’t really been all that successful looking back at them. Thinking about why some are successes right away and some never get there I believe that one of the main reasons that separates these projects is time. Not necessarily time to do actual development, but an actual time commitment from the business side of an organization, time to plan and time to actually think, reflect and make changes as the projects where moving along.
Tech Is Easy, People Are Not
I am of the believe that tech is easy, while people are hard. It is a lot faster to change an application or some code, than to change the behavior of an actual human being. And this is why I believe time is one of the most important things to early on in a project make into a priority. If we want to be successful the project needs time from actual business users. They need to be a part of making the specifications, and they need to help test, iterate, use and dream about what a solution can be and grow into. And they need time to adapt to whatever is being made as change can be scary and without enough time people might resist it. This may sound easy, but if someone from the business does not get a percentage of their time allocated specifically to use on a project they very quickly become “busy” and down prioritize helping out on a solution that is actually being created to help them in their job moving forward.
Reflection Is Under Appreciated
My favorite part of doing scrum is the retrospective. It is made so the scrum team can have time to sit down and reflect on what went well, what can be improved and look for things that they perhaps isn’t doing at all. I believe we all need to spend more time reflecting, but we need time to do it. In a stressful work day we too rarely sit down and think about how the last meeting we organized went. Did everyone understand why they where there? Was I clear enough in my communication? Did we all really agree on what to do when the meeting was over? If we reflect more on things I believe we also see behavior/patterns throughout our day that can be discussed the next time you reflect, either alone or together with others. We see the world in a wider view than just our own, hectic life one meeting, or task, at a time. Reflecting is all about having time to see where we can further improve.
Failing Is Necessary
We need time to fail. Failures can be though, both for an individual, a team and an organization, and it might feel like a disappointment and a waste of time if things doesn’t work out. But if you never fail, have you really pushed yourself to your limits? Have you really learned absolutely everything you could from an experience? If you fail, what can you learn from it? Do a mini retrospective and see what you and others think about it. Failing is hard, but we need time to do it in order to not be afraid of experimenting and see how far we can go.
Everyone Needs to Be Able to Talk to Everyone Involved
Communication takes a lot of time. Making sure all stakeholders are updated about the progress. Making sure everyone on the team knows about changes to the end product. Making sure a problem can be solved quickly by running a question through the correct person who knows the answer. The more people involved in a communication chain the longer it will take to get a message across, or an answer to a question. It can also turn into a game of whispers where the original question/answer gets lost in the chain. By allowing everyone to talk to everyone you basically get more time since you can cut directly to the source of an answer. Not every decision needs to be taken in a scheduled meeting. Five minutes by the coffee machine with the correct person might be all another person needs to keep working, but if we always have to scheduled a meeting two weeks in advance things will take time. And there is probably better stuff to use that time for.
Time is important. Both at work and in our private lives. And time management is really hard! My experience is that if you want to succeed make sure both you, and others involved, have enough dedicated time to use on what you are working on. If dedicated time is not given it is to easy to say that you are “too busy” to help out when others ask. So make time to plan, reflect and fail. Plan to have time to reflect and fail, and reflect and fail in order to further improve!