Aakash's profileAakash's spacePhotosBlogListsMore  |  Tools Help |
|
July 18 Leadership and OwnershipAakash, from his experiences, shares some of the thnings which project leaders might want to consider when working on their projects:
1) Give them freedom
When you have selected your team members and you trust their skills, give them freedom of work - Let them work in their own way. Don't push anyone for any specific things and don't interfere in the decisions your team member can take well.
For example, if you are an owner of a software company and you have hired a very talented software developer for a complicated software project -- let him take software related decisions. Don't question too much because that will make him feel that you don't trust his skills and knowledge.
This will result in the decrease of efficiency of his work. You can still guide him if he is doing anything wrong.
By giving such freedom, you will not lose the control of the project, but you will earn the respect from your team and they would gain a feeling that you trust their skills. This will result in a huge improvement in efficiency of their work and the overall progress of the project.
2) Let them feel it's their project, not just yours!
It is quite important that each team member (at least the main members) feel that the project they are working on is their own. If you start interfering too much (especially if you are not more experienced/knowladgable in their area), your team members will start feeling that you own the project. Then they will just work for their own benefit (for example salary) and will not care about the success of the project. It can be really dangerous.
3) Set up norms
To make sure that everything runs smoothly, it is a good idea to define "fair" team norms at the starting of the project. In this way, all your team members will clearly know what are the expectations from them. Norms list will guide them while they are under pressure or when they are uncertain about deciding something.
Hopefully this ideas will help someone efficiently run their team projects. Comments on this blog post are very welcome. :) July 16 I am oldWhen I looked at a computer/laptop company's website today, I started feeling really old.
I remember the days when I used to program in VB6 in my old computer.
 My computer's configuration was:
533 MHz Pentium 2 processor with 32 MB RAM and 4GB Hard-disk drive space.
Let's compare that with the laptops available today (for a bit cheaper price):
2.1 GHz (times 2), Core duo processor. But with 800 MHz FSB (Bus speed!) compared with 533 MHz processor speed!!
4 GB DDR2 Memory (working at 667 MHz), which means today's laptop could just load all data from my old computer in its memory! Motherboard also has 3 MB of cache. I didn't even know that there is something like "cache memory" in this world!
And the hard-disk of about 250 GB (SATA) which is no way near 4GB old hard-disk I had, which also used to make a lot of noise.
 Also it is important to note that today's laptops come with dedicated graphics memory and graphics processor! Hmm, in my days, I just had DOS based games like Prince, which I don't think would require dedicated graphics processor!
 Well, I don't know what this comparision means to you, but I feel really old now! |
|
|
