Need a job advice please

[electroRF]

hi,

I started off my own project at work, behind the scenes.
I'm working on an application which will enhance our capabilities.

I keep having this feeling that if I not release a version of this quick enough then someone else will come up with this project and i'll be left with nothing.

On the other hand, if I'll expose this project while the application is not ready, I'm afraid that someone else might take over.

What do you think I should do in such case?

Should I release a preliminary version and let the teammates work with that, even though it only has 2 features at the moment?

Or shall I wait? or declare the project without releasing any version this week?

Thank you guys.

 

[Nigel Goodwin]

I would suggest you're probably heading for getting sacked, haven't you already been refused permission to do this?.

 

[electroRF]

Hi Nigel,

I tried lifting another project, in which I was dependent on other team members, which did not cooperate, and therefore I let this project go and started off with a new project which I'm dependent only on myself.

no one knows about it yet (as it's not ready yet), but there shouldn't be a permission issue for that project.

 

[Nigel Goodwin]

So having been refused permission for one project, you then decide to start another without asking for permission.

I don't think this is going to end well.

 

[Mr RB]

I agree.

At the risk of sounding Dickensian; a bosses job is to make decisions, an employees job is to do whatever the boss says...

 

[ClydeCrashKop]

Under normal circumstances, what you do on company time belongs to the company.

 

[picbits]

As above - in the UK (at least), any work you do on company time belongs to that company.

 

[Mikebits]

Doing your own thing on company time is not a good idea.