Hi,
I think that you have to really know the customer before you start
telecommuting, and the customer needs to know you. I have worked for most
of my VPN-customers 5-10 years.
It is ideal to be able to access the customer systems on a short notice
for small fixes, troubleshooting or limited well defined projects.
At the moment I have 6 customers I am doing VPN-work for. 4 of these are
actually situated less than 20 km from our office. Unfortunately 2 of them
have a requirement to use their own hardware, so I have two extra
computers sitting under my desk...
Sometimes I choose to visit the sites anyway, as some (non technical)
things are hard to solve efficiently when not on site.
Best Regards - Misi, RRR AB, http://rrr.se
> Hi Elry,
>
> I was hired in Orange Romania in 1997. At that my opinion was that "IT"
> is the same everywhere. At the bottom, the assumption is true.
> Latter, I discovered that "IT" has a different meaning even inside a
> telecom operator.
>
> I totally agree with 2, 3, 4 and 5
>
> 3 can be overcome by using a dedicated person from TELECO company.
>
> 6 - is just to for those who think that there could be a chance to make
> money.
>
> 1 - definitely you had a bad experience
>
> Daniel
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:[EMAIL PROTECTED] On Behalf Of Elry
> Sent: Wednesday, May 30, 2007 9:59 PM
> To: [email protected]
> Subject: Re: OT: Remedy Developer Telecommuting Experiences
>
> Telecommute opportunities are becoming more common place, but in most
> cases you have to have a good track record with a client or "outsourcer"
> to find them.
>
> Here is my experience with telecommute opportunities
>
> Telecommute opportunities can pose a problem if....
>
> 1) Your connection to the server is too slow; therefore, you are unable
> to code as fast as you can think.
> 2) Project Deliverables are not clear and concise.
> 3) Project Communication is poor.
> 4) Project Management/Technical Lead are poor.
> 5) Scoping of Time Alloted for Project Tasks are poor.
> 6) You only do coding - the monetary compensation can be poor (unless
> you have a special skill/knowledge to impart i.e. ITIL, Telecom etc.)
>
> On the other hand telecommute can be a great experience if...
>
> 1) You have a good connection (this usually means that a Citrix Thin
> Client is being used or you have a Server at the client location that
> you can Remote Connect to to launch the Thick Client (WUT, WAT).
> 2) Project Deliverables are clear and concise - you are doing strictly
> coding or getting requirements/presenting via Webex or JAD Conference.
> 3) You have a strong Project Manager/ Technical Lead - Communication
> skills have to be really good.
> 4) Project Tasks have a proper amount of time alloted to them (this
> usually has to be done by a Technical Project Lead).
>
> Good Luck Bud....
>
> On May 30, 2:10 pm, Kaiser Norm E CIV USAF 96 CS/SCCE
> <[EMAIL PROTECTED]> wrote:
>> All:
>>
>> I was curious if anyone has ever worked a Remedy job that was
>> telecommute? How many such opportunities exist? Are they numerous or
>> rare?
>>
>> Thanks,
>>
>> Norm
>>
>> ______________________________________________________________________
>> _________ UNSUBSCRIBE or access ARSlist Archives
>> atwww.arslist.orgARSlist:"Where the Answers Are"
>
> ________________________________________________________________________
> _______
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
> the Answers Are"
>
> --
>
> *****DISCLAIMER*****
>
> The information contained in this communication is confidential and may be
> legally privileged. It is intended solely for the use of the individual or
> entity to whom it is addressed and others authorized to receive it. If you
> are not the intended recipient you are hereby notified that any
> disclosure, copying, distribution or taking action in reliance of the
> contents of this information is strictly prohibited and may be unlawful.
> Orange Romania S.A. is neither liable for the proper, complete
> transmission of the information contained in this communication nor any
> delay in its receipt.
>
> *****END OF DISCLAIMER*****
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
> the Answers Are"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
