Originally posted by SantaClaus
View Post
- Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
- Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Reply to: Boring work related problem
Collapse
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
- You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
- You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
- If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Logging in...
Previously on "Boring work related problem"
Collapse
-
Originally posted by EternalOptimist View PostYou wanna back orf a little here. Sometimes a bodge is the right answer. The dev might hate it, the PM might be out of a job, but for the business, it might be right.
A project lacking proper management will always fail in the absence of sheer dumb luck.
Leave a comment:
-
Originally posted by TykeMerc View PostAs a PM I need to know the technical score, that's why I get to know the techies as well as their managers/team leads. If the PM is worth his salt then he will want to know what the real situation is so that he can hold a meeting like I described.
Leave a comment:
-
Originally posted by suityou01 View PostI went to the big boss. I explained what trouble the project is in, the bad habits in the design practices (Ie fag packet design approach) and asked if I was here to sort it out, or just bodge and run.
He was clear in that I was an expensive resource, and they were paying the money for the benefit of my experience. He is going to advise the PM of this.
PM will now love me I'm sure. Had to be done IMHO.
Leave a comment:
-
Originally posted by suityou01 View PostI went to the big boss. I explained what trouble the project is in, the bad habits in the design practices (Ie fag packet design approach) and asked if I was here to sort it out, or just bodge and run.
He was clear in that I was an expensive resource, and they were paying the money for the benefit of my experience. He is going to advise the PM of this.
PM will now love me I'm sure. Had to be done IMHO.
Leave a comment:
-
Originally posted by suityou01 View PostI went to the big boss. I explained what trouble the project is in, the bad habits in the design practices (Ie fag packet design approach) and asked if I was here to sort it out, or just bodge and run.
He was clear in that I was an expensive resource, and they were paying the money for the benefit of my experience. He is going to advise the PM of this.
PM will now love me I'm sure. Had to be done IMHO.
Leave a comment:
-
Originally posted by TykeMerc View PostThat's a classic case of weak/ineffective/non-existent Project Management.
As a PM I would get your advice as the technical expert, arrange a meeting with the customer and present the technical and real cost/time cases, I'd probably drag you into the meeting too depending on how good you are at translating tech into English.
The PM needs to make rational recommendations to the customer and customer needs to make a decision. The recommendations should be one of 3 choices with cost estimates and impacts
1. Rewrite
2. Bodge it as requested with risks of failure highlighted and longer term repercussions
3. Close project
That's the approach I would take anyway based on the summary info you've presented.
He was clear in that I was an expensive resource, and they were paying the money for the benefit of my experience. He is going to advise the PM of this.
PM will now love me I'm sure. Had to be done IMHO.
Leave a comment:
-
I think the bodge it and bugger it approach is somewhat limiting when it comes to references. Also does give contractors a bad name.
Leave a comment:
-
I just do what the client asks me to do
I will be long gone before the tulip hits the fan
Leave a comment:
-
That's a classic case of weak/ineffective/non-existent Project Management.
As a PM I would get your advice as the technical expert, arrange a meeting with the customer and present the technical and real cost/time cases, I'd probably drag you into the meeting too depending on how good you are at translating tech into English.
The PM needs to make rational recommendations to the customer and customer needs to make a decision. The recommendations should be one of 3 choices with cost estimates and impacts
1. Rewrite
2. Bodge it as requested with risks of failure highlighted and longer term repercussions
3. Close project
That's the approach I would take anyway based on the summary info you've presented.
Leave a comment:
-
Originally posted by suityou01 View PostCan't do that unfortunately. Metastorm BPM is a workflow engine come screen designer tool (and much more besides but still) and for a given workflow there is only one table. All data entry forms are based on this table. Any twinned tables would not connect to the form.
I can however split the workflow up into multiple processes and design it all properly, but that's kind of where I am now :-(
so the tables need normalizing and they dont have the time ? excel is too good for them
Leave a comment:
-
Originally posted by TazMaN View PostI'm be tempted to put these concerns in an email and ensure that it reaches the appropriate people.
As contractor you can take one of these routes:
1) Do the job you're told to do, and not give a tulipe about anything
2) Provide the benefit of your insight and experience, and advise on the best solution possible. Having said that, budgets are always a factor to consider.
....Provide/offer the benefit of your insight and experience, and provide your advice on possible solutions make sure this advice is documented (even if only via an EMail) and is given to the appropriate people then do the job you're paid to do (and not give a tulipe about anything else).
Edit: Swamp obviously types faster than me!
Leave a comment:
-
Just write an email saying the table cannot handle more columns. Then add the columns anyway.
You're a contractor. Don't get involved in office politics, just invoice for the days you've worked and be happy.
Leave a comment:
-
Originally posted by EternalOptimist View Postyou could 'twin' the tables up. Secondary (new) table with the same PK and new fields
how long have you got if she gets her way ?
I can however split the workflow up into multiple processes and design it all properly, but that's kind of where I am now :-(
Leave a comment:
- Home
- News & Features
- First Timers
- IR35 / S660 / BN66
- Employee Benefit Trusts
- Agency Workers Regulations
- MSC Legislation
- Limited Companies
- Dividends
- Umbrella Company
- VAT / Flat Rate VAT
- Job News & Guides
- Money News & Guides
- Guide to Contracts
- Successful Contracting
- Contracting Overseas
- Contractor Calculators
- MVL
- Contractor Expenses
Advertisers
Contractor Services
CUK News
- Labour’s plan to regulate umbrella companies: a closer look Nov 21 09:24
- When HMRC misses an FTT deadline but still wins another CJRS case Nov 20 09:20
- How 15% employer NICs will sting the umbrella company market Nov 19 09:16
- Contracting Awards 2024 hails 19 firms as best of the best Nov 18 09:13
- How to answer at interview, ‘What’s your greatest weakness?’ Nov 14 09:59
- Business Asset Disposal Relief changes in April 2025: Q&A Nov 13 09:37
- How debt transfer rules will hit umbrella companies in 2026 Nov 12 09:28
- IT contractor demand floundering despite Autumn Budget 2024 Nov 11 09:30
- An IR35 bill of £19m for National Resources Wales may be just the tip of its iceberg Nov 7 09:20
- Micro-entity accounts: Overview, and how to file with HMRC Nov 6 09:27
Leave a comment: