Projects are the tricky things to accomplish. To save you some time, here are 6 tips for what NOT TO DO. Good luck!
If teammates ask you what you are doing with your project and want to know if they can help you, do not answer them, blank them…
It’s a lot better for shaping your project if nobody in the team or the customer knows what you’re doing. Then they cannot interfere with you and help you to accomplish your goals. Even if you need help, the same rule applies: speaking is silver, silence is gold.
Why should you regularly provide updates about the progress of the project? “It’s done when I say it’s done”. It is much more fun if the end result is a complete surprise for the customer! Interviews provide you with the risk that the customer will change their mind in the meantime, which will give you more work and change the end result. By not informing the customer now, you increase the chance that he will be dissatisfied after presenting the final result.
Good is never good enough. Therefore, just aim for your project to meet the bare requirements. Only the obsessed in your organisation and the customers will care, and if you let them get involved they will just delay you by going over small details that can only be a bit better. Whether it’s fit for use is not important…
Just take projects that are really fun to run. Feasibility and yield, what does that matter? If you only do fun projects, you will have a great time at work. Therefore, take a critical look at the fun factor of projects and consider it the most important argument for entering or rejecting a project.
Keep your ass covered. By doing whatever you are doing, you will be able to document every piece of code that you type and document each post you send. Of course, you should be able to prove that if something fails it was not your fault. Documenting everything makes sure you have irrefutable proof that you were not responsible for any mistakes. Tip: find a scapegoat, you can point your guilty finger at someone else, preferably someone who hasn’t documented every keystroke.
At the start of the project, you make a plan. This plan needs to stay the same throughout the entire project, whether it’s a month or two years! Never change your plan. It does not make sense to keep track of schedule changes and add them to your planning. With a little luck, when something fails because your schedule is not up to date, you can tell your customer that the delay is because it wasn’t planned so isn’t your fault.
Congratulations! If you’ve followed all of these tips, your project has been a gigantic failure and you’ll probably be fired! (If that was your aim, well done!) Are you curious about how to successfully complete a project? Feel free to contact us about our consulting services.
By Richard De Boer
Knowledge24: The Future of AI with ServiceNow By Ramond Keesmekers, Head of Technology and Misha…
Our Head of Education, Nektaria Kriketou, was lucky enough to jet to Las Vegas for…
Pink Elephant EMEA is pleased to confirm its team is returning to exhibit at SITS…
The benefits of studying ITIL 4 Foundation First, let's talk about the benefits ITIL 4…
On National Chocolate Cake day, we discover the connection between the sweet treat and ITSM.…
By Shaz Akhtar, Pink Elephant Associate In the evolving world of IT Service Management (ITSM),…
Integrating AI into ITSM with Pink Elephant and Freshworks Artificial Intelligence (AI) continues to redefine…
Inventory tracker software and how to optimise its use What is inventory tracker software? Inventory…
We have a number of exciting opportunities to join our growing team. If you are looking for a company where career-minded professionals can achieve success while bringing their best self and qualities to work each day, Pink Elephant may be the company for you!
Find your role.