Of Year after year, and the coronavirus is still with us. Wasn’t it a coincidence that last year we experienced a situation almost similar to today? It seems that we haven’t learned from past mistakes and our approach hasn’t improved much. But the topic of the pandemic would be for another article. I mention it because I see a kind of contrast in it with how we try to work here at Enehan. In the following paragraphs, I will logically focus mainly on the Delivery “gang” – a team of about 50 people working on complex deliveries of Salesforce projects.
Project Lesson Learned
Things go wrong on a project, it happens and will happen. We overseas chinese database are only human, after all. But if unwanted things happen again, it is clear that something is wrong. How do we prevent mistakes from happening again?
However, individual error leads to deeper training and better adoption of existing materials.
You are probably right to think that an analysis at the end of a project is great, but it is too late. Just like the coronavirus, a project in poor condition has certain symptoms. And it is desirable to have something that allows us to identify these symptoms at a time when it is time to apply the right treatment to “heal” the project. One of the tools for early detection of “symptoms” is regular project statuses. They always provide a general overview of how the project looks in terms of timing, keeping the promised scope of delivery, cost level and how the team itself is doing. During the discussion, we are able to capture a lot and direct it in the right direction. However, we must maintain a certain level of perspective, objectivity and self-criticism of the people on the project who give us that project status.
Project Review
It is not always humanly possible to see something that we are b2b digital marketing methods in japan a part of, which is why another activity that we call “Project Review” has proven to be effective for us. What is it about? Selected senior people outside the project participate in a regular project day for a certain period of time, are on statuses, talk to people, and go through the project disk. In no case do we want to point the finger at anyone for doing something wrong. The main goal is to identify the already mentioned unhealthy project symptoms, catch them early and give suggestions for correction. “Project Review” should take place shortly after the project has started, because we are able to catch most of the errors right at the beginning. The length of this phase is proportional to the size and complexity of the project.
Project of Review
A large number of future problems can be prevented even before the project begins. We are talking about the time when the offer is submitted and together with the customer we are just defining and setting the details of the project. At this stage, we adhere to the proverb – “measure twice, cut once” and try to notice signals that could lead to problematic moments. For example, it could be an ambiguous division of duties and responsibilities between the supplier (us) and the customer, or a situation where the customer himself does not yet know exactly what he wants, or is internally inconsistent. All of this needs to be taken into account and the parameters and functioning of the project defined accordingly before its actual excavation.
In conclusion, I would like to add that a poorly functioning project thailand data or unfulfilled expectations are not the goal of any of the stakeholders.
So let’s look forward, let’s be self-critical, let’s be humble. Only in this way can we move forward.