Perspective is a very powerful term exist while you are thinking about anything. I am currently working little as a programmer and more as project manager. From my journey in IT industry so far, I came across many roles like designer, developer, manager, hardware engineer, IT manager, system administrator etc., I noticed that, Whatever role you working as, You wears that particular hat while you are thinking about given matter. For each role you see a matter from different perspective and your brain respond it accordingly.

In past, I was working for British Telecom company called Iqara, which is now known as You Tele. At that time, I was serving as Flash Experience Engineer. My duty at that time was to create presentation for CEO about their operations in India. He need to show the presentation to British Telecom board about what progress they are doing in India from the money they invested in the new broadband company. I had to include some photographs of company, data center etc., in to the presentation. For some reason, pictures were not ready and I was always worried that, deadline is near by and they are not giving me pictures. How I would able to finish the project on time? Whenever, I contact my reporting officer, He was telling me – “Ashvin, use some dummy boxes right now and start working on picture effects”. And I was thinking like, How can I give effects without having real photographs. He might be thinking, why this guy is always asking a single question – “Where are the photographs?”. That’s the difference between perspective about a project between project manager and developer or designer.

Currently, I am working at a FlashBrain as Project Manager. Project release as a manager is a different thing and it’s different thing as a programmer. Project manager thinks that release should be there on deadline. He agree that, It’s not always possible to have perfect planned release on planned date. But, release should be there with some modules not implemented or with some known issues. For Project Manager, His commitment to the client is important about timings. Even client agree that release may not contain everything planned. If there is one or two day delay is there with a release as per plan that is even okay for a client. But if, Project Manager is giving commitments to the client about releases and client don’t see a release after more than 2 false commitments, Client starts thinking about – “Are they serious about their commitments? or Are they even working on my project?”. While projects are outsourced to remote locations (That’s the case for FlashBrain, We provide outsourcing services for Flash development projects), this is the biggest threat.

If we imagine the same thing as a developer perspective, There are two kind of developers. One who are perfectionists and another type is who believes in finishing the work and they are not much serious about quality of the work. For both kind of developers, there are advantages and drawbacks associated with them. Perfectionists are good for a company in long run, As whatever they do is perfect. But the drawback is, they will take more time to implement the solution and which might even more than the deadline. Other type of programmers, who mostly finish all the tasks on time but in a long run, He or other programmer may need to do rework on that in later stages of the project.

In FlashBrain, Our 95% of Flash Developers are perfectionists. While, they are working on some project, they want to have it perfect. They give priority to quality of work instead of deliver it on given date. Of course, they get permission for that from Project Manager and respective Clients. Our developers always tries to minimize known issues and bugs ratio from the work done by them. So for sometimes releases are not ready on given date. Project Manager wish that even with some known issues, Project Release can help him to maintain his commitments given to the Client.

In our last management meeting, We were thinking to if its possible to come up with some process which can keep everybody happy – Client, Project Manager, Developers and of course quality of the work. At FlashBrain, We believe in trying every possible solution to make sure the path we are choosing is most optimized in every aspect if feasible. The first solution we are trying currently is, Do a quick review of the work being done by team twice in a day. It doesn’t matter if the quick review is just for 30 seconds or 5 minutes. It’s all about to make sure that team is on correct path. If not, We have two chances in a day to cure it. This means, We can see what is going on with release twice in a day. If one particular module is taking more time than expected, due to whatever reason – Project Manager or Client can take decision on that as soon as possible and this practice will help to keep the distance between planned release and actual release.

If our current solution will help us to improve release qualities, I will share more about that or other solutions that we might try in future.