Its all about me...

Who am I?

I am a software engineer and working in Cybersoft as Manager Web Applications. Cybersoft is an IT-Enabler Software Solutions Developer with rapidly growing business in North and South America. The company is headquartered in Houston Texas (USA) with an offshore software development facility in Lahore, Pakistan.

I like playing squash, cricket, and most of all i love to swim. i also like reading books, actually i am crazy of books. my favourite writers are MUMTAZ MUFTI, ASHFAQ AHMED, FYODOR DOSTOEVSKY, LEO TOLSTY and much more... Every time a child says "I don't believe in fairies," there is a little
fairy somewhere that falls down dead and ......................I don't believe in fairies.

my favourite poets are Keats, Faiz, Ghalib, Hardy, and hmmmmmmmmmmmmmmmmm .... much more... well-somehow, my mind goes blank as I am suppose to write about myself. Anyhow my name is Waqas Javed ....



these are some informations about me.... (what the hell...)

Date of Birth: 1978 August 12
My Favorite Dishes: Chicken, Rice, Pizza, and all vegetables..
My favorite drink: Coca-Cola
My Ideals: Holy Prophet Mohammed (PBUH), Jesus Christ, Buddha
My Favourite Politicians: Nelson Mandaila, John F. Cannedy, Quiad-e-Azam, Napolean
Marital Status: single. (akayla)
Body Type: Normal
Body Type: Sometimes, I smoke...

Black Belt in Taekwondo & National Universal Gold Medallist

Neither I deceive any one nor I want to be deceived

I love honest, sincere and straight forward people

Email: waqasj@gmail.com
Height: 175 cm
Weight: 149 lbs
Qualification: Masters in Computer Sciences
Health: Excellent.... (By the grace of Almighty)
My Favorite Singers: Pink Floyed, Carpenters, Kishor Kumar, Rafi, Lata, Lional Richie etc
Nature: I don't feel comfortable when there are a lot of people around me. I enjoy with some of my friends or my family members
My Favorite Poets: Faiz, Ghalib, Keats, Parveen Shakir etc
My Favorite Writers: Fyodor Dostoevsky, Mumtaz Mufti, Leo Tolsty etc
My Favorite Movies: Sattyam Shivam Sundaram, The Last of The Mohicans, Cut Throat Iceland, Pakeeza, Sharabi, Sholay
My Star : Leo
My Favorite Songs: koi nawan laara laa ke mainoon roll jaa, Tere Bina Zindagi Se Koi, Koi Hamdam na raha, ye dil deewaana, jeewan ki bagia mehkai gee, kee haal sunawan dil daa, na tum hamain jaano, o basanti pavan pagal na jaa re na jaa, Enigma, Frozen, L L Lies, If You Go Away.. and many many more.
My Favorite Novels: Crime and Punishment, The Idiot, Brothers Karamazov, Ali Pur Kaa Aili, Raja Gidh and many more.
My Hobbies I like to watch movies, reading books (literature, poetry), enjoy the outdoors like camping, fishing , water skiing, surfing, traveling and riding You must understand the whole of life, not just one little part of it. That is why you must read, that is why you must look at the skies, that is why you must sing, and dance, and write poems, and suffer, and understand, for all that is life "I have a primary responsibility to myself: to make myself into the best person I can possibly be. Then, and only then, will I have something worthwhile to share."

I never found the companion that was so companionable as solitude. We are for the most part more lonely when we go abroad among men than when we stay in our chambers. A man thinking or working is always alone, let him be where he will.

To be continued....

AWESOME....

You've been on my mind and heart. I see you struggling and planning, worrying and sweating, crying and running, at a furious pace. You're trying to move that mountain by yourself again, huh?

God asks that we cast all our cares on Him because He cares. Think about what your worrying says to God when you refuse to give things over to Him.
When you worry about money, you're telling Him that He is unable to provide for His creatures ... that although He has riches beyond belief in Heaven, He is too stingy to share them with you.

When you worry that no one understands you, you're telling Him that although He has been with you since before you were formed in the womb, and has carved you into the palm of His hand, He doesn't know you.

When you worry that you will not have enough food, you're telling Him that although He rained down bread from Heaven in the desert to feed His children, you are the one He's forgotten.
When you worry that your enemies will have victory over you, you're telling God that although He has given you spiritual battlegear to defend yourself, that despite His track record of being a giant slayer, Red Sea divider, lion mouth closer and a furnace cooler, He can't handle your co-worker, your neighbor or a former friend.

When you worry that your children have decided to follow the world instead of your example, you're telling God that He doesn't keep His promises.... That despite the fact that you have raised them up in the way they should go, they'll stray because basically, He lied.

When you worry because the doctors told you that children are impossible, that a cure is impossible, that healing is impossible, you're telling Him that this world controls your fate. You're saying that prayer time with Him is nearly something to pass the time. You're saying that although He can raise the dead, make a virgin conceive, open the womb of a woman well past eighty, heal a 12 year issue of blood, make the blind see and the lame walk, He can't help you.
When you worry that no one will love you, that you'll be lonely for the rest of your life, you're telling Him that His love is insufficient ... that He couldn't possibly love you enough to ward away loneliness. You're saying that although He has promised life more abundantly, He was lying .... that despite the fact that He started off saying that it is not good that we be alone, He's changed His mind.

When you worry and refuse to give the problem over to Him, you're telling Him that although He could create the world, He can't handle what's going on in your world, so you will. You are saying that He won't work things out, that obstacles cannot be overcome, that mountains can't be climbed, that healing cannot occur, that what is lost will not be found, that joy does not come in the morning, that He is not the God of a second chance, that the promised land has been swallowed up by the desert, that you have discovered the height, depth and width of His love and found it to fall short of your needs.

Think about all that you're saying to the one who loves you the most and who has all power, really think about it. Then open you hands and release what you've been holding onto. Bow down on your knees and ask Him to forgive you for doubting Him. Walk away with a peaceful heart and note the footsteps that go before you to make the crooked places straight, a way in the wilderness, and later springing forth in the desert.

"Stand in a stream with waters around your ankles. The waters that pass by you at that moment, you will never see again. So it is with the misery that has challenged your life ... let it go, let it pass away."

AS CHILDREN

AS CHILDREN
Contributed by Maria Hanna
Nov 15, 2007

A friend once told me, "I am a skeptic; Unless I have scientific evidence, I cannot believe in God." Then she started stating passages from the Bible that she cannot scientifically comprehend.
Let's move to a lighter scene with little children running around their dad happily teasing him, "daddy! daddy!" They do believe the man to be their father. They never ask, or even think of asking, for scientific proofs for their sonship to him. Even if their dad provides them with facts, their innocent, immature thinking will not grasp it.
They may consider such facts to be nonsense. It is not until they grow up that they understand.
In the same context, God has illuminated us with evidence of His existence through His amazingly created nature, the design of the universe, and man, as well as through His care and love to every one of us demonstrated in countless ways if we care to notice them. When Jesus tried to enrich souls with spiritual facts about Heaven, miracles, and Life after death, infant physical minds could not comprehend His message.
What is the easiest reaction? To consider such facts nonsense. One day when we "grow up" and our spiritual identity develops, we will declare such facts true - much the same as the little children do.

8 e-mail mistakes that make you look bad

1. Failing to follow e-mail etiquette. I believe in the old adage, "You catch more flies with honey than with vinegar." There's no point in belaboring the etiquette issue. We all know we should be polite. But here are a few points to consider:

• Don't write when you're angry. Wait 24 hours. Calm down. Be reasonable. Have someone else edit your e-mail.

• Don't use sarcasm. You may think you're clever, but the recipient will be put off.

• DON'T USE ALL UPPERCASE! That's the e-mail equivalent of yelling. Your recipient won't be appreciative. Go easy on the exclamation marks, too. Overuse dulls their effectiveness.

• Use clear subject lines. That will help people decide whether to read the e-mail now or later. We're all busy. Your correspondent will appreciate your thoughtfulness.

• Keep it short. If your e-mail is more than two paragraphs, maybe you should use the telephone.

• Change the subject line if you change the topic of a thread.

• Unless the recipient has previously agreed, don't forward poems, jokes, virus warnings and other things. You're just wasting valuable time and bandwidth.

2. Thinking you are anonymous. If you are sending nasty missives, you might think no one will be able to figure out that the e-mail came from you. After all, you set up a phony Web address. Think again. E-mail contains invisible information about the sender.

That information is in the header. All major e-mail programs can display header information. Here's how:

• In Microsoft Outlook, double click the e-mail. Then click View > Options.

• In Microsoft Outlook Express, click the e-mail. Then click File > Properties and select the Details tab.

• In Eudora, double click the message. Then click the Blah Blah button.

• In Netscape, click the message to open it. Then click View > Message Source to display the header.

The sender's revealing information is in the sections that begin with "Received:." There may be several of these, depending on the number of computers the e-mail traversed. The originating computer is in the bottom "Received:."

That section will have an Internet Protocol (IP) number, such as 124.213.45.11. It can be traced on a number of Web sites. I use InterNIC (www.internic.net). The number is probably assigned to the sender's Internet service provider, rather than the sender. But the ISP will be able to identify the sender using that number. Remember the header if you're tempted to send an anonymous e-mail. You may be less anonymous than you think.

3. Sending e-mail to the wrong person. Today's e-mail programs want to make it easy to send e-mail. This means that when you start typing the address of a recipient to whom you have previously sent mail, the "To:" field may already be populated. Be careful. Always double-check the recipient is the intended one.

In addition, if you're writing something ugly about Joe Smith, you'll have Joe's name on your mind. Don't send it to him. I once knew an intern at a newspaper who did just that. He didn't like his supervisor and said so in graphic terms in an e-mail. Then he accidentally sent the e-mail to his supervisor. (The intern kept his position, but the atmosphere was cold, to say the least. And there was no job offer at summer's end.)

4. Using one e-mail address for everything. I have four different e-mail addresses: private, public, one I use for online mailing lists, and another for when I go shopping online. These addresses attract mail for those specific areas.
I can have as many as I want, because I host my own e-mail server. But if you are using an Internet service provider, you still can do this. Most providers will give you a half-dozen e-mail accounts. You can also use addresses on the Web for personal accounts. Both Hotmail and Yahoo! are good. You can reach those accounts from anywhere, assuming you have Web access.

5. Forgetting to check all of your e-mail accounts. Checking all these accounts can be a chore, especially from home. So I use ePrompter (www.eprompter.com), which can check 16 different password- protected accounts. Best of all, ePrompter is free. There are other programs that will do this for a fee, including Active Email Monitor (www.emailmon.com).

6. Clicking "Send" too fast. Reread every e-mail before you send it! I actually get e-mails from job applicants with misspellings and missing words. They all go to the same place: the garbage. This is a pet peeve. I'm not going to hire someone who is careless.

Even if you're not looking for a job, you want to be careful. People will judge you subconsciously on mistakes. None of us is perfect. But you can catch 99% of these problems by rereading the text.

And don't depend on the spell-checker. It will catch misspellings. But if you use "four" instead of "for," or "your" for "you're," it won't tell you. It also is not likely to catch any missing words in a sentence that you inadvertently failed to include. So take a minute and reread your text. Don't look like an ignoramus.

7. Forgetting the attachment. This seems obvious, but I can't tell you how many times I've received an e-mail with a missing attachment. Since we all do it occasionally, it shouldn't be a huge deal.

However, if you consistently make this mistake, people (perhaps important people) may think you're losing your marbles. They might even hesitate to do business with you in the future. When you get ready to send your e-mail, think: "What am I forgetting?"

8. Using your ISP's domain and not your own. Make your company look big. If you use a Web account or an ISP's name for your business, you're not going to look professional. You can buy a domain name separately for $20-$30 per year from a company such as VeriSign (www.netsol.com), or as part of a package from a Web hosting and e-mail service such as that offered by Microsoft Small Business. Assuming someone else hasn't already grabbed it, you can have your company in the domain name.

Let's say you run The BoolaBoola Co. If you use an ISP's address, you would have something like JoeBoolaBoola@SomeISP.com. But if you buy your own domain name, it could be Joe@TheBoolaBoolaCo.com. That's much more likely to impress your customers.

E-mail is almost like talking. We use it so much that we don't really think about it. But there are rules and courtesies, just as there are with talking. And there are other considerations involved in communicating by written word only.

Giving them some additional thought could make your e-mail experience more satisfying and your recipients much happier.

Optimizing Your Asp.Net Pages for Faster Loading and Better Performance

By: John Belthoff

John Belthoff is an avid web developer who writes about Asp.Net in his spare time. He owns a Windows Asp.Net Web Hosting Company: www.hostsstation.com where you can contact him about hosting your website/blog or just to learn more.

If you read the internet and all of the websites dedicated to Asp.Net you will inevitably read about the wonders of the DataGrid, DataList, and Repeater controls. While each of these has its place, if you are only displaying data there is a much faster and more efficient means to do so.

Let's say you have a page that displays articles based on a query string. Take my article pages for instance. Each article is stored in a database and displayed on the page based on the unique id of the article as stored in the database.

A normal asp page execution procedure goes something like this. The code queries the database based on the Article I.D. and then brings back that information to the page where you display it in the fashion that you would like. This is a fairly straight forward approach with asp and is done all the time.

So how do we speed up our asp.net pages?

Number 1: Use Asp.Net Caching!

This is a no-brainer, and I won't go into the brilliance or details of asp.net caching here because at the time of this writing Google has 2,780,000 articles on the topic. Basically instead of querying the database each time the page is loaded you only query the database once and load that result into the system cache. Subsequent calls to load the page retrieve the data from the cache as opposed to the database which gives you an instant and considerable performance boost. You can then set the cache for how long the cache should store the information as well as many other features. If you are not using the cache, you should be whenever possible!

Number 2: If possible, do NOT use the standard Asp.Net controls.

That's right. The standard asp.net controls are designed for rapid development and not page performance. They allow you to design pages that grab and display data very quickly but their actual performance suffers because of the extra overhead which is there for ease and speed of development time and not page execution speed.

Instead, create either a User Control or even better yet a Web Custom Control which is by far the fastest performance wise and really quite easy to create and use.

Number 3: Use an SqlDataReader or even better yet use a set based command for Sql Server data retrieval and simply execute that one command against the database.

An asp.net SqlDataReader is a fast forward only datareader that closes the connection after it reads the last set of results. Now for my article pages we are only returning 1 particular result. In this case we would opt for the set based command. If you had more than 1 result returned, in your table of contents for instance, you would use the SqlDataReader because you are returning multiple results.

Set based commands are stored procedures that bring back data through parameters as opposed to a result set which then in turn needs to be looped through to obtain your data. So instead of writing your stored procedure like the following which brings back 1 result set:

Select Title, Body, Author

From Articles

Where ArtID = 215

We can write it using a set based command like this.

Create Procedure mysp_GetArticle

@Title varchar(200) Output,

@Body varchar(8000) Output,

@Author varchar(500) Output

As

Select @Title = Title, @Body = Body, @Author = Author

From Articles

Where ArtID = 215

GO

The above query will return only the three parameters called for and not a result or record set so you don't have to then walk through the returned record set that has only 1 result in it anyway. This second little process of work decreases your performance so do not use it if you can. Combine this technique with the asp.net cache.

Number 4: Use Classes and ArrayLists as opposed to returning an SqlDataReader.

Create a class and then if there are more than one set of results store those results into individual instantiations of that class. Finally store each of those classes into an ArrayList. You can then store only that ArrayList into the asp.net cache. So instead of getting the results back from a SqlDataReader when loading your page you get them from the ArrayList which is stored in the cache. Nice huh?

Finally... you want to incorporate all of these techniques into your final results which would be performed in the following manner and sequence.

On the first time the page loads, query the database and return all of your data storing it into individual classes. Then store each of those classes into an ArrayList. If you only have one single result you may store only the class into the cache. Then take your ArrayList and store it into the cache.

Next create a Web Custom Control and pass the cached ArrayList to the custom control and loop out your data using the HtmlTextWriter which is very fast. Remember each subsequent call to load the page will be called from the cache which stores your ArraList of classes or your single class.

Certainly it takes a significant amount of additional coding to do it in this fashion, especially when you take proper error handling into consideration, but if you follow this approach your pages will be screeching fast, you will immediately notice the difference, and your asp.net pages will execute in the proper sequence - Data handling in the Page_Load function and the html display in the Page_Render function. Further, you will be glad you did and so will your visitors.

Happy Programming!

The Waterfalls And Rapids Of IT Projects

By: Vernon Riley

Vernon Riley is a senior consultant who understands both project management and technology. He has 20 years experience of major IT projects, and the difficulties of delivering complex projects. He can be contacted via Kutchka

Even when a good governance structure is in place the structure of an IT project is more important than is often assumed. The structure can make estimating difficult, and make it impossible to deliver whilst retaining the confidence of the management and external stakeholders. Yet the structure is often assumed without proper debate - either with the customer or with the project team.

Many organisations and project managers still like to use the so called 'waterfall' method of controlling IT projects, because they believe it gives them greater commercial control, and allows fixed cost projects. This method splits up the total project into a series of logical steps : - Work out what items should be done - Estimate what these will cost. - Agree these definitions and costs. - Undertake formal design. - Build the items. - Test the items. - Deploy and use the items.

The waterfall method can appear to offer a clear logical path from inception through to completion. The commercial control supposedly occurs because the facts are determined before agreement is reached, thereby allowing the following steps to be controlled within an agreed financial framework.

If the project uses 'well known' technology or is very similar to previous projects then the waterfall method can be successfully used. Where there is a substantial part that is new, or uncertain some serious issues exist with this approach.

In some cases the proportion of the total project costs and time that need to be spent before sufficiently precise estimates are generated can be substantial. Clients and suppliers can disagree whether this should this be free or paid for. In many cases a messy compromise is arrived at where the costs of the business analysis and estimation will be paid for ( or at least negotiated about ) after it is decided whether the project is to be accepted.

In other cases it isn't certain that people are good at thinking through complex systems with sufficient accuracy to make the design 'fit for purpose', prior to some good 'proofs of concept'.

Quite apart from the difficulty of identifying the 'facts'; the fixing of features up front can lead to an 80/20 split where 80% of the costs produce 20% of the benefits and vice versa. This should give most clients cause for concern.

There can also be significant change in the business requirements during a project of 2 or 3 years duration. This has encouraged the move to Rapid Application Development ( RAD )

Good estimates are difficult It is difficult to produce good estimates. Increasing the granularity can lead to estimating safety margins being accumulated ( if say the minimum estimating unit is 1 day - then something that took 1 hour would be recorded as 1 day giving a 7 hour accumulation per task of this length).

Estimates need to be distinguished from use of historical data to give timings. But the latter need to be very carefully annotated and used to ensure they are being used properly.

Perhaps the thought that 'estimation should be democratically controlled, and execution involve authoritarian methods rather than as often happens the other way around'; is one of the most useful maxims here.

Acceptance of the facts It is very difficult to know the extent to which the ultimate customer actually has bought into the design and estimates being produced. There may in fact be no acceptance other than of 'that is the way our supplier chooses to do things' giving the opportunity for later disputes.

In some projects it can be very difficult to establish who is entitled to sign off documents as correct on behalf of the organisation. This makes any approach other than time and materials problematic.

Rapid Application Development ( RAD )

Rapid development techniques are now accepted in many cases. These methods involve using a number of iterative prototypes are built to give the customer greater control over the finished result. Thus the analysis, design, build and test sequences of the whole project is split into a number of successive cycles.

There are, however, unanswered questions about the range of IT projects for which RAD is suitable, and issues about whether all of the suggested elements of RAD are as important as one another. For instance some approaches time box 3 to 6 week periods, whilst others simply allow incremental delivery over a number of months. Yet others regard the complete incorporation of automated unit testing into the coding ( build ) stage as perhaps the most important contribution.

There are numerous variations on RAD, including pairing - where two programmers work together with one writing tests and the other writing code to satisfy those tests. There is still a real need however to prioritise the efforts.

Some of the serious criticisms of RAD are that it can allow scope creep, lack of rigour, and cost overruns. It can be particularly difficult to stop 'gold plating' on particular easily understood elements (e.g. the user interface) at the expense of underlying functions that are more complex and less easily explained or understood by business people ( when the latter are involved in the assessment of each iteration ).

Here again, therefore, we encounter evidence that the structure of the project can have substantial impact on the viability of the development.

There are a number of problems therefore with both traditional and RAD methods of controlling custom and or complex IT projects. Many projects would be improved if expert help and more time were spent restructuring the project at the start to help the IT supplier clarify the design choices and the IT client clarify the business requirements. Whilst this does involve an explicit acceptance that money will be spent 'investigating' and 'researching'; this is actually nothing more than bringing present good practice out into the open.

Do You Want To Discover The Truth About Your Projects ?

By: Vernon Riley

He different types of project review each has their own characteristics and benefits. For any review however it is important to decide what the overall purpose is, and who should gain what from the output. This step is missed out in many cases and the design of the review is not given sufficient attention. Standard methodologies for carrying out project reviews can be helpful, but must be supplemented by intelligent thought! In the author's experience a review should consider both the project management standards and the subject matter of the project. Mistakes in either or both of these can lead to disaster, and it can take considerable skill and knowledge to uncover the truth.

If you are responsible for a project's success then you need the truth, and you are responsible for setting the principles and scope that will govern how effective the review will be in uncovering that truth. In particular you need to pick the reviewer so that you understand what bias is likely to be reflected in the results. Bias can arise from background, review methodology or political interests; and may not be intentional.

Bias due to interests
the review may be commissioned, designed or just operated by people who wish to prove certain results and disprove others. It may be that some wish to prove a particular methodology works, and therefore the review concentrates on the extent to which that methodology has been completely and fully employed. This may be completely different from assessing whether the project itself is likely to succeed or fail. The Prince2 manual for instance has a comprehensive health check. This will check for the complete use of Prince2 but the questions are mostly of the 'is there...item X' type, and there are very few questions asking about the quality of any of the items whose existence is being checked. Jobs and career progress may be at stake and informal alliances may be formed to ensure that the "correct results" are obtained by the review.

Bias due to role
The UK government OGC gateway review is an externally focused health check, which concentrates on the extent to which the project is still required and could deliver the benefits sought by stakeholders. It is also quite reasonably designed to protect a purchaser (because the UK government almost always has this role), rather than the creator or supplier of the project. This affects the questions and can lead to a situation in which the project is affirmed as meeting all the criteria for the purchaser but is doomed as a result of events being suffered by the supplier (e.g. commercial losses, staff turnover etc.)

Bias due to reviewer's background
There can be subtle issues arising from the background of those carrying out the project review. Some reviewers will be much more technologists than project managers, whilst others will be the reverse. Although it makes competent practitioners much harder to find there is a good case for insisting on both sets of skills.

Bias due to distance
Reviews are sometimes undertaken by those who inhabit a management world of reports. If they then communicate with project managers and others who are somewhat distant from the actual tasks then the overall effect may be that the blind are leading the blind. Remember that real people, somewhere, should be actually doing the work to deliver the tasks required by the project. A competent reviewer needs to find them, understand them and discover what they think. This necessitates not only people and managerial skills but also some understanding of the skills employed by the project staff.

Checklists
These are useful for ensuring appropriate coverage but it is equally important that the reviewer can think freely and explore the implications of the information that the project team give. This information is normally messy and ill organized. Coherent results pointing in a single direction are unlikely and the reviewer needs to be able to cope with

So what should the balance be?
Project Management skills in medium or large projects are certainly critical as the need to be organized is a critical success factor. 'Ready aim fire' expresses the simple truth that without those competent to first aim the project team members in the correct direction there is little chance of the target being hit. It is important that clear business justification and rules for project control are created and maintained during the life of the project. Appropriate risk management and planning are also vital to enable the overall project to achieve its intended results.

That the reviewer also possesses a reasonable level of subject related understanding is also critical so that those who are undertaking the work can be questioned rigorously about the quality and assumptions underlying the work they are undertaking. This isn't about the facility to do the work, but the ability to discuss designs, build dependencies, test conditions and the like in the detail that will establish whether the sequence of work intended is viable.

Reviews can be very important, but deciding who should carry them out, and how they should be undertaken is not simple. The most important determinant of success is your choice of reviewer.

Project Management

1. Build and Maintain Contacts

Contacts are the lifeblood of any successful business. Most people have short memories hence its imperative to keep in touch with prospective clients, business contacts and industry people. You never know who may need you when and for what work.

2. Build a Strong Portfolio

When service buyers see provider portfolios on the freelance websites, apart from the price bid, the profile of the service provider, client referrals, work examples and overall presentation plays a major role in the selection process. Hence, it is important to build a professional portfolio with clearly laid out skill sets, contact information, customer references, academic qualifications, professional qualifications and examples of work done.

3. Define Scope of Work

When you win a project, make sure you clearly discuss the scope and functional features of the project with the client. This leads to healthy client relationships and makes it easier to plan the project execution. If you frequently contact the client with your queries, he might think that you did not understand the project and may become apprehensive working with you.

4. Design System Architecture

After finalization of project scope, design the architecture of the project in the form of a diagram and discuss it with the client so that you need not make too many changes after delivering the project to the client. Make sure you or your team sticks to this design so that the project development does not become haphazard.

5. Project Documents

It is a good practice to store all project related documents and client instructions in one place for quick access and timely action.

6. Time Allocation

- Define Projects Tasks, Sub-Tasks and Allocate Time for each activity so that you can match client deadlines and also monitor the progress of work with respect to pre-decided timelines.

7. Allocate Tasks to Team Members

Keep track of Tasks allocated to team members for quick reporting and monitoring the progress of work.

8. Set Deadlines

Estimate and Set Deadlines on the various project related activities.

9. Monitor Progress of Work

Monitor the progress of work frequently so that you can communicate the same to your clients. Clients expect you to keep in touch with them and intimate them of the state of affairs.

10. Keep Track of Project Costs and Expenses

The primary purpose of business is to earn profits. For this you need to keep track of your expenses and revenue generated from work.

11. Client Communication

Frequently communicate with clients, intimating them of the progress of work. This leads to development of client confidence in your abilities.

12. Deliver the Project

After completion, deliver the project to the client and keep record of the delivery so that you can generate invoices on the client.

13. Raise Invoices on Clients

Raise Invoices on Clients and record of payment receipts for timely reminder to clients and to manage your inflows.

14. Manage Project Change Requests

Often, clients may ask you to change certain parts of a project. As part of efficient customer service, you should record and keep track of such requests and intimate the client upon making the change.

15. Use a System to Manage

Activities– Utilize a software system to manage all these activities. There is plenty of software available that can help you manage one or more of the above activities.

Javascript Certification

http://www.brainbench.com/transcript.jsp?pid=6127671

Test: Javascript Date: 27-May-2006 Score: 3.19 Weights: 100% Javascript Elapsed time: 33 min 16 sec

Javascript Score: 3.19 Percentile: Scored higher than 35% of previous examinees Demonstrates a solid understanding of core concepts within this topic. Appears capable of working on most projects in this area with moderate assistance. May require some initial assistance with advanced concepts, however. Strong Areas Objects Statements Weak Areas Components Controlling Windows, Documents

.Net Certification

http://www.brainbench.com/transcript.jsp?pid=6127671

Test: .NET Framework Date: 27-May-2006 Score: 3.48 Weights: 100% .NET Framework Elapsed time: 21 min 18 sec

.NET Framework Score: 3.48 Percentile: Scored higher than 83% of previous examinees Demonstrates a solid understanding of core concepts within this topic. Appears capable of working on most projects in this area with moderate assistance. May require some initial assistance with advanced concepts, however. Strong Areas Common Language Runtime (CLR) .NET Framework Class Library Assemblies Weak Areas .NET Programming .NET Metadata .NET Architectural Overview