5 Indications that the IT Project is Fake

I got involved with different types of IT projects over the years and got scammed several times and wanted to share this based on experience. If you are in the same field you will agree with this too. Here are the 5 indications that the IT project is fake:

1. Measure the number of errors of the documents being handed to you. Yes, they are not Americans so it is an excuse to write carabao English or is it because they were hired for another reason? Errors(excluding those grammatical errors) in Technical Designs are those that are written to too specific. Instead of just writing: "Return an error if the customer code is not maintained in SAP Master Data"; the pretentious Technical Architect would write: "After obtaining customer code, you must check if the customer code exist in table lfa1". They should not be involving themselves in specifics but should just concentrate on higher level description and the different business scenarios. Giving too specific instructions would lead to more confusions and the programmer would just cut and paste which could lead to a more prolonged test period and you can not blame the programmer since you are invading his territory which he would immediately assume you are in full command which make their job a whole lot easier. Programming entails a lot of careful planning and meticulous design to produce a highly optimized solution. And giving too much information means you are the one who planned it and it is your design and not the programmer. There are a lot instance and I would say a major challenge to describe a certain specification and to hurdle such challenges, creativity and of course your competency is the key. The preparation of Technical Documents and Functional Specifications are more expensive than doing the actual programming or coding so you must realize that being a TA or BA or FA, you can already relax because you are on top of the Software Development Life Cycle, well that is where you are wrong.

2. Measure the competence of your peers. Do this secretly, if all your peers are female, you should begin to suspect something is going on.

3. Frequency of work and how fast it should be done and how many people have the same position like you have. Begin observing how they behave and all your movement must be calculated. The world's resources is scarse.

4. Other than your peers, how does the company's employees behave and the surrounding environment, how was it? Do they start offering other services or want to offer except that they just keep looking at you?

5. There are other circumstances where it is up to you to interpret which can trigger something in you that you think violates certain moral standards, do not ignore it. Your instincts does not lie to you.