Technology is taking over the world! All right, that is not exactly true but it is changing how we interact with each other, conduct business, and find out information. Instead of sending a letter in the mail to a friend in Germany, we can instead sit down at our computer, type her out a long email, and send it across the world in less than a second. It does not cost you anything! Teachers are bringing computers and the internet into the classroom so that students learn how to use it as a tool; it is incredibly helpful for conducting primary research on a topic or finding a fast answer to a question.
Information technology and IT services are topics that interests several people. The majority of the world can learn how to use it but a small percentage actually wants to know how it works. The information technology gurus are the ones that make hardware and software systems user friendly for the rest of us. Everything computer and internet related that we use is in thanks to a team of dedicated computer scientists working hard to perfect their IT management services projects for mass consumption.
If you are interested in working in the information technology field, you need to earn a degree at a vocational school or one from a college or university. Most people recommend that you study computer science or computer engineering in order to receive practical hands on knowledge and experience. Not only will these majors teach you valuable skills, they will also allow you to experience this field first hand so that you can determine whether this the area is the one you want to pursue for the rest of your life. As long as you find yourself interested and eager to learn more about the material, you have probably found your calling!
This field is a very good one to be in, especially at the moment. Most small, medium, and large business use IT outsourcing for their needs which means that there are more and more managed service providers opening to meet the demand. If you are ready to be the best IT there is, there are several spots available for you in the job market! Good luck!
Autres pages web:
IT Project Management
Define project goal
Plan Project
Execute Project plan
Close Project
Evaluate IT Project
vendredi 4 décembre 2009
Finding IT Jobs - Effective Information Technology Job Search
This article discusses some best practice job search strategies for the information technology sector. According to a recent survey that studied the best practices for prospective employees obtaining employment with a company, these were the best practices in order of effectiveness:
• Social Networking With Company Employees Is Most Effective
• Submitting Your Resume Directly To The Company Web Site
• Submitting Your Resume With Staffing And Service Companies
The following strategies employ all those practices of social networking, submitting your resume directly to the company web site and leveraging the contacts and relationships recruiters have with company employees. The networking tools such as Linkedin and other such tools are key in your establishing contacts with employees of prospective companies.
Social Networking Sites
LinkedIn, Twitter and Facebook are becoming key with any job search strategy. LinkedIn is a social networking site with 35 million that focus on promoting contacts among business people, job seekers and those with common interests.
IT Staffing Companies
Staffing and service firms business model includes both contract, contract - permanent, and direct opportunities. The clients include fortune 1000 companies in North America across all industries. It is an excellent opportunity for the candidate to work with the company for a defined contract period while gaining industry standard experience and leverage that with new opportunities. A lot of the companies have some health insurance plan that is partial or fully funded. In addition there are training resources, 401K plans, and a multitude of other employee benefits. Submit your resume online with there companies and search current opportunities. Keywords are very important with resumes and any search process keeping that in mind.
Microsoft Partner Search
It takes some effort to do a search on Microsoft partners however do a search from the microsoft solution finder web page and go to the career sites.
Cisco 10,000 Partner Network
This is a new venture Cisco has started linking skilled engineers with their 10,000 partner companies. These companies employ Cisco, Microsoft Engineers, Developers, Sales and Project Managers. The official name is cisco partner talent network.
Top 500 VAR Companies
Autres pages web:
IT Project Management
Define project goal
Plan Project
Execute Project plan
Close Project
Evaluate IT Project
• Social Networking With Company Employees Is Most Effective
• Submitting Your Resume Directly To The Company Web Site
• Submitting Your Resume With Staffing And Service Companies
The following strategies employ all those practices of social networking, submitting your resume directly to the company web site and leveraging the contacts and relationships recruiters have with company employees. The networking tools such as Linkedin and other such tools are key in your establishing contacts with employees of prospective companies.
Social Networking Sites
LinkedIn, Twitter and Facebook are becoming key with any job search strategy. LinkedIn is a social networking site with 35 million that focus on promoting contacts among business people, job seekers and those with common interests.
IT Staffing Companies
Staffing and service firms business model includes both contract, contract - permanent, and direct opportunities. The clients include fortune 1000 companies in North America across all industries. It is an excellent opportunity for the candidate to work with the company for a defined contract period while gaining industry standard experience and leverage that with new opportunities. A lot of the companies have some health insurance plan that is partial or fully funded. In addition there are training resources, 401K plans, and a multitude of other employee benefits. Submit your resume online with there companies and search current opportunities. Keywords are very important with resumes and any search process keeping that in mind.
Microsoft Partner Search
It takes some effort to do a search on Microsoft partners however do a search from the microsoft solution finder web page and go to the career sites.
Cisco 10,000 Partner Network
This is a new venture Cisco has started linking skilled engineers with their 10,000 partner companies. These companies employ Cisco, Microsoft Engineers, Developers, Sales and Project Managers. The official name is cisco partner talent network.
Top 500 VAR Companies
Autres pages web:
IT Project Management
Define project goal
Plan Project
Execute Project plan
Close Project
Evaluate IT Project
Manage Your Business's Information Technology the Easy Way
Many businesses on the East Coast decide to go with a Boston it service provider to audit, procure, build, secure and administrate their information technology. For cost efficiency and professional service in dealing with information technology consultant ,bostoncompanies choose to outsource their IT.The wedge of your business budget pie taken up by in-house information technology can be substantial. By the time you add up employee salaries and benefits, along with training and the cost of the tools needed for performing the job, many Massachusetts companies find that it makes better financial sense to procure the services of a Boston it provider.One of the early steps that many organizations take is to hire an information technology consultant. Boston-area businesses benefit from using a consultant to perform a review of the business's information technology currently being utilized. Also taking into consideration the company's long-term projections and budget goals, the IT consultant will offer up a plan for making your company's information technology run smoothly at the best possible cost to you.Boston it consultants will help you select the hardware and software you need for expedient IT performance. Servers and network hardware are expensive items that are nevertheless necessary for conducting business, so you will want to make sure that the technological items you are buying will actually perform the tasks that you need. Desktop and laptop computers, along with the myriad peripherals that go with them, are vital to the day-to-day operation of your business and will immediately affect your business bottom line. This is why it pays to have expert Boston it consultants, engineers and technicians available to help you sort through the wealth of options to find what will work best for your unique company.Once you have all of the hardware in place, you will also want to think about network security. For access to engineers and technicians who have been certified with the top technology companies and who provide expertise in information technology ,boston businesses turn to Boston it providers for help with this crucial area. If you operate an online storefront, or simply need to make sure that your business partner's information will not be compromised, it is imperative to provide a secure platform upon which to conduct business. Boston it services can handle this aspect of your business for you, giving you and your business associates the peace of mind that everyone wants.Network integration is another topic to discuss with your information technology consultant. Boston IT services can monitor your network round the clock to ensure its stability. This reduces the amount of wasted network down time, saving you money. Boston-based it services can help with every area of your company's information technology system to make it run effectively.
Autres pages web:
IT Project Management
Define project goal
Plan Project
Execute Project plan
Close Project
Evaluate IT Project
Autres pages web:
IT Project Management
Define project goal
Plan Project
Execute Project plan
Close Project
Evaluate IT Project
Information Technology Business Plan For IT Support Contracts
If you are trying to come up with a good Information Technology business plan, you may be wondering about what your focus should be. Usually the top priority is creating a plan that will help you get great clients, so you can effectively manage and grow your business.
Many Information Technology consultants make the mistake of thinking they can just get by on one-shot deals and fly-by-night customers. But in reality, this type of approach just leaves you frazzled and worried about where you will get your next big project or next paycheck. You need to build a stable business based on on-going relationships with long-term clients that will pay you each and every month, and bring you predictable service revenue.
The best plan for developing a strong Information Technology business plan is to insist that every one of your clients sign a support contract. The following 4 tips can help you understand how to build your business plan on the solid foundation of support contracts.
Support Contracts Are Key for the Busy Information Technology Consultant. If you are like most IT consultants, your time is incredibly valuable. When you choose to base your Information Technology business plan on support contracts, you help better manage your time, particularly when you have many clients that all need service at once. When you insist upon support contracts, you maximize your utilization rate while still having enough time to deal with client emergencies when they occur.
Better Manage Emergencies. When you base your business model on support contracts, you can prioritize your clients’ emergencies. When you have a bunch of clients all with emergencies at the same time, you can’t be everywhere at once. You need to narrow down the list of who gets your immediate attention and who will need to wait. Basically, those people that have committed to you long term get the royal treatment and those that do not have to accept that you will get to them when you have the time to spare.
Force Customers and Clients to Make a Decision. You need to base your Information Technology business plan on support contracts in order to force those you are serving to make an important decision – are they "in," or are they "out"? A solid plan based on long-term relationships with clients weeds out those that are just testing the waters and are not serious about working with you long-term.
Manage Expectations. A solid Information Technology business plan based on support contracts also helps you manage your customers’ and clients’ expectations more effectively. Those that have a support contract know they are top priority … and those that don’t know you have clients with support contracts and that they are the ones that will be responded to first.
In this brief article, we discussed 4 tips to help you create a strong Information Technology business plan, so you don’t have to stress out about being everything to everyone. Learn more about how you can attract great, steady, high-paying clients with an Information Technology business plan built around support contracts
Autres pages web:
IT Project Management , Define project goal, Plan Project, Execute Project plan , Close Project , Evaluate IT Project
Many Information Technology consultants make the mistake of thinking they can just get by on one-shot deals and fly-by-night customers. But in reality, this type of approach just leaves you frazzled and worried about where you will get your next big project or next paycheck. You need to build a stable business based on on-going relationships with long-term clients that will pay you each and every month, and bring you predictable service revenue.
The best plan for developing a strong Information Technology business plan is to insist that every one of your clients sign a support contract. The following 4 tips can help you understand how to build your business plan on the solid foundation of support contracts.
Support Contracts Are Key for the Busy Information Technology Consultant. If you are like most IT consultants, your time is incredibly valuable. When you choose to base your Information Technology business plan on support contracts, you help better manage your time, particularly when you have many clients that all need service at once. When you insist upon support contracts, you maximize your utilization rate while still having enough time to deal with client emergencies when they occur.
Better Manage Emergencies. When you base your business model on support contracts, you can prioritize your clients’ emergencies. When you have a bunch of clients all with emergencies at the same time, you can’t be everywhere at once. You need to narrow down the list of who gets your immediate attention and who will need to wait. Basically, those people that have committed to you long term get the royal treatment and those that do not have to accept that you will get to them when you have the time to spare.
Force Customers and Clients to Make a Decision. You need to base your Information Technology business plan on support contracts in order to force those you are serving to make an important decision – are they "in," or are they "out"? A solid plan based on long-term relationships with clients weeds out those that are just testing the waters and are not serious about working with you long-term.
Manage Expectations. A solid Information Technology business plan based on support contracts also helps you manage your customers’ and clients’ expectations more effectively. Those that have a support contract know they are top priority … and those that don’t know you have clients with support contracts and that they are the ones that will be responded to first.
In this brief article, we discussed 4 tips to help you create a strong Information Technology business plan, so you don’t have to stress out about being everything to everyone. Learn more about how you can attract great, steady, high-paying clients with an Information Technology business plan built around support contracts
Autres pages web:
IT Project Management , Define project goal, Plan Project, Execute Project plan , Close Project , Evaluate IT Project
Technology Project Planning
I recently had a bit of a debate with a technology consultant friend who knows I am big on content and detail within project planning and the contracts that support a technology deal. We found ourselves talking about that principle of economics called the law of diminishing marginal returns. His point was that for project owners who are in the midst of planning a new project—gathering requirements, fleshing out specifications, polling user preferences, etc.—the law of diminishing marginal returns sets in much earlier than they realize. The resources spent during the initial planning stages produce some hefty returns. But soon after, spending the same amount of resources again, and the next time after that, will produce smaller and smaller chunks of benefit. When you are caught up in a planning process, it is often difficult to identify the point at which your cost-benefit curve has begun to flatten.
What my friend was saying seemed plausible, and because I did not have any evidence to the contrary, I just accepted his theory. Then I thought of a possible consequence of his theory, and I said, “You’re not going to go out and start spreading this thought around the technology community, are you?”
Threatened evangelist
My fear was this. Here was I, this evangelist of content and detail within every information technology project, and across the table was a fellow who could undermine the past and future progress of my mission by telling folks they actually need less planning and critical thinking for their technology projects and not more. Project owners’ planning and thinking are, after all, what generate the content and detail I crave and have come to respect.
Well, we talked some more, and my friend added some clarification. As it turns out, he was suggesting mainly that project owners not waste time and money planning what cannot be planned effectively at a particular point in time. Made sense. I was still squirming, but now a bit relieved.
Obvious example
You have decided to use a staged or iterative approach for your next project. You will buy some off-the-shelf software and customize it a fair amount. Phase 1 might involve extending a discrete element of existing functionality and then wiring up to a live database for some testing.
In this example, there is really no point to thinking through the details of Phases 2 through 5 or estimating costs within those phases, except in either case at a very high level, because: 1) unless Phase 1 is completed smoothly and with an acceptable cost, you will never get to the subsequent phases; and 2) you have not yet tested your assumptions about costing within Phase 1. Indeed, you probably chose an iterative approach for this project because of your inability to plan your project effectively from start to finish.
Less obvious examples
My friend and I talked some more, and we moved beyond the obvious examples, the ones that are easy to accept. My natural reaction was to resist any further extension of his theory because I knew he would be cutting closer and closer to the bone, threatening the very foundation of my evangelist mission. However, sitting before me was a bright person and a clear thinker, with nearly two decades of experience with technology. I had to listen (nervously). “When the student is ready to learn, the teacher will appear.”
Requirements gathering – A good thing, no doubt, and something the experts have been encouraging us to do more of over the last ten years. “Insufficient requirements development cited as leading cause of project failure.” When it comes to requirements, we have been led to believe that more is not enough. Surely there is a point at which more requirements are not helpful (and may even be detrimental), but the experts have not told us how to determine just when we have turned the corner.
Specifications development – Same story. Develop specifications thoroughly now or risk project failure.
User preferences – Same story. Involve your users in your planning process. Otherwise, “If you build it, they won’t come.”
We have heard so much preaching on these topics that each of us can rattle off a number of clichés for each topic. The advice has been mostly good, but we are hammered with it by speaker after speaker, in article after article.
Reconciliation
As much as I resisted the flow of this discussion with my friend, I have to admit that what he was saying made perfect sense to me. But now I had to find some way to reconcile two divergent concepts: on the one hand, my long-held belief that more project planning and critical thinking should always be one’s aspiration, and on the other, my realization that you truly can have too much of a good thing.
Ultimately, I found the reconciliation I needed with just one insight. It occurred to me that, with all of the speakers and literature out there telling us to engage in more best practices for our technology projects and more often, we have become conditioned to believe that more is not enough—in fact, because of the nature of the beast, more can never be enough. We have been doing more and more, and the incremental improvements we have witnessed, together with the new articles we read, encourage us to keep doing more and more. Of course, our intention is good, but when can we stop doing more? When should we stop doing more?
It’s all relative
I think it all boils down to relativity—your relative sophistication as a technology buyer, and the relative nature of your particular project. If you started heeding the experts’ advice many years ago, your approach to buying technology may be fairly sophisticated by now. You may be doing an appropriate level of planning for your projects, and maybe you occasionally do too much. Other organizations are just now opening their eyes to a better way, perhaps prompted by a recent problematic project.
Second, when enough is enough depends on your particular project. Your goal is to plan effectively and thoroughly for all aspects of your project, but be mindful that your present need or ability to plan certain elements may not yet exist. Further, even if you have the present need and ability to plan a certain aspect of your project, do not overdo it. For example, do not continue to add more and more requirements to your requirements basket as if quantity were your only goal.
On this last point, remind yourself that requirements, specifications, user preferences, and every other item on your project-planning list have at least one thing in common. Once you have thought of them and cemented them into some spreadsheet, they have a way of hanging around for the duration of your planning process, and often through completion of your project. Instead of waiting to whack some of these hangers-on toward the end of a phase or at the end of your project (“backward creep” of scope or deliverables), attempt to prioritize them at an early stage of your project. You will not even open Requirements Container 2 until the high-priority requirements in Container 1 have been exhausted (satisfied or deliberately discarded). A prioritization approach could save you time, dollars and other resources.
Conclusion
For many of us, it may be best not to let go of our conditioned response to project planning and critical thinking—not just yet anyway. The conditioning represents an overall positive motivation, its underlying purpose is producing results, and our technology procurement process, including its planning element, may still have plenty of room for improvement. The more sophisticated technology buyers among us might want to put the brakes on the conditioned response a bit.
Regardless of what camp you are in (and until further notice from the experts!), be at least mindful of the fact that there is such a thing as too much project planning. I, for one, am now a believer.
Autres pages web:
IT Project Management
Define project goal
Plan Project
Execute Project plan
Close Project
Evaluate IT Project
What my friend was saying seemed plausible, and because I did not have any evidence to the contrary, I just accepted his theory. Then I thought of a possible consequence of his theory, and I said, “You’re not going to go out and start spreading this thought around the technology community, are you?”
Threatened evangelist
My fear was this. Here was I, this evangelist of content and detail within every information technology project, and across the table was a fellow who could undermine the past and future progress of my mission by telling folks they actually need less planning and critical thinking for their technology projects and not more. Project owners’ planning and thinking are, after all, what generate the content and detail I crave and have come to respect.
Well, we talked some more, and my friend added some clarification. As it turns out, he was suggesting mainly that project owners not waste time and money planning what cannot be planned effectively at a particular point in time. Made sense. I was still squirming, but now a bit relieved.
Obvious example
You have decided to use a staged or iterative approach for your next project. You will buy some off-the-shelf software and customize it a fair amount. Phase 1 might involve extending a discrete element of existing functionality and then wiring up to a live database for some testing.
In this example, there is really no point to thinking through the details of Phases 2 through 5 or estimating costs within those phases, except in either case at a very high level, because: 1) unless Phase 1 is completed smoothly and with an acceptable cost, you will never get to the subsequent phases; and 2) you have not yet tested your assumptions about costing within Phase 1. Indeed, you probably chose an iterative approach for this project because of your inability to plan your project effectively from start to finish.
Less obvious examples
My friend and I talked some more, and we moved beyond the obvious examples, the ones that are easy to accept. My natural reaction was to resist any further extension of his theory because I knew he would be cutting closer and closer to the bone, threatening the very foundation of my evangelist mission. However, sitting before me was a bright person and a clear thinker, with nearly two decades of experience with technology. I had to listen (nervously). “When the student is ready to learn, the teacher will appear.”
Requirements gathering – A good thing, no doubt, and something the experts have been encouraging us to do more of over the last ten years. “Insufficient requirements development cited as leading cause of project failure.” When it comes to requirements, we have been led to believe that more is not enough. Surely there is a point at which more requirements are not helpful (and may even be detrimental), but the experts have not told us how to determine just when we have turned the corner.
Specifications development – Same story. Develop specifications thoroughly now or risk project failure.
User preferences – Same story. Involve your users in your planning process. Otherwise, “If you build it, they won’t come.”
We have heard so much preaching on these topics that each of us can rattle off a number of clichés for each topic. The advice has been mostly good, but we are hammered with it by speaker after speaker, in article after article.
Reconciliation
As much as I resisted the flow of this discussion with my friend, I have to admit that what he was saying made perfect sense to me. But now I had to find some way to reconcile two divergent concepts: on the one hand, my long-held belief that more project planning and critical thinking should always be one’s aspiration, and on the other, my realization that you truly can have too much of a good thing.
Ultimately, I found the reconciliation I needed with just one insight. It occurred to me that, with all of the speakers and literature out there telling us to engage in more best practices for our technology projects and more often, we have become conditioned to believe that more is not enough—in fact, because of the nature of the beast, more can never be enough. We have been doing more and more, and the incremental improvements we have witnessed, together with the new articles we read, encourage us to keep doing more and more. Of course, our intention is good, but when can we stop doing more? When should we stop doing more?
It’s all relative
I think it all boils down to relativity—your relative sophistication as a technology buyer, and the relative nature of your particular project. If you started heeding the experts’ advice many years ago, your approach to buying technology may be fairly sophisticated by now. You may be doing an appropriate level of planning for your projects, and maybe you occasionally do too much. Other organizations are just now opening their eyes to a better way, perhaps prompted by a recent problematic project.
Second, when enough is enough depends on your particular project. Your goal is to plan effectively and thoroughly for all aspects of your project, but be mindful that your present need or ability to plan certain elements may not yet exist. Further, even if you have the present need and ability to plan a certain aspect of your project, do not overdo it. For example, do not continue to add more and more requirements to your requirements basket as if quantity were your only goal.
On this last point, remind yourself that requirements, specifications, user preferences, and every other item on your project-planning list have at least one thing in common. Once you have thought of them and cemented them into some spreadsheet, they have a way of hanging around for the duration of your planning process, and often through completion of your project. Instead of waiting to whack some of these hangers-on toward the end of a phase or at the end of your project (“backward creep” of scope or deliverables), attempt to prioritize them at an early stage of your project. You will not even open Requirements Container 2 until the high-priority requirements in Container 1 have been exhausted (satisfied or deliberately discarded). A prioritization approach could save you time, dollars and other resources.
Conclusion
For many of us, it may be best not to let go of our conditioned response to project planning and critical thinking—not just yet anyway. The conditioning represents an overall positive motivation, its underlying purpose is producing results, and our technology procurement process, including its planning element, may still have plenty of room for improvement. The more sophisticated technology buyers among us might want to put the brakes on the conditioned response a bit.
Regardless of what camp you are in (and until further notice from the experts!), be at least mindful of the fact that there is such a thing as too much project planning. I, for one, am now a believer.
Autres pages web:
IT Project Management
Define project goal
Plan Project
Execute Project plan
Close Project
Evaluate IT Project
Inscription à :
Articles (Atom)