|
Hi All,
Working on time critical project, all going well and then management. The last project I worked on escaped management interference and was delivered early and under budget (  ). So when I started on the upgrade I followed the same procedure as before, Test, find fault, tell the developer of the fault (to ensure they hadn't got to far out of the 'zone'), rasie ticket & fault is fixed everybody happy. Then my Boss is told by 'Management' to tell me she had complaints that I was disturbing the software dept. So I stop disturbing the software dept and am asked at the next stand up why I haven't been reporting faults, haven't I found any... So normal service resumes until said management type get involved again. I give up!
|
|
|
|
|
Doesn't your company have a bug tracking system that's available to developers ?
|
|
|
|
|
RickZeeland wrote: Doesn't your company have a bug tracking system that's available to developers ?
Yes, Management. Didn't you read his rant.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
|
So raising a ticket is already considered "bothering development" ? 
|
|
|
|
|
You are as lost as I am, I think this management person is either trying to prove to new overlords they are useful or trying to justify there existence...
|
|
|
|
|
glennPattonWork wrote: she had complaints that I was disturbing the software dept
Then please, please stop preventing everybody from doing their work.
Now that you mention it, it is the same here, we always get interrupted by customer contracts and customer requests and customer this and customer that. Do we really need customers ? They are such a nuisance, keep interfering...
modified 20-Nov-18 7:07am.
|
|
|
|
|
Customers are great, they don't know what they want but they want it NOW! 
|
|
|
|
|
glennPattonWork wrote: they want it NOW!
Wow! How have you managed to beat them down to such reasonable deadlines? Ours usually want it YESTERDAY at the latest. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Years ago, I worked in an office next to a sales person named Thelma, a beautiful blonde older lady who wasn't always there, if you catch my drift.
One Monday she dropped an awesome line.
She had a client on the speaker phone, going over a change order that he wanted to get done as fast as possible.
The conversation went something like this:
Thelma: So, when do you need this done?
Customer: I need this done yesterday!
Thelma: Well, I'm sorry, sir, but we're closed on Sundays!
|
|
|
|
|
Speaking for development, "Please bother us!" 
Like most developers, I'd much rather have someone in the company discover a problem than have a customer scream about it later. The former is far less personally embarrassing and painful. Oh, and yeah, its good for the company too
|
|
|
|
|
I know, I did development for many years before I became a tester. I only really became a tester as it was the only job on offer...  . Seem to be good at it, as I report issues before they get include in a build that is release...
|
|
|
|
|
Yeah, in many companies, its regrettably a difficult relationship between the development and QA teams. It should be entirely collaborative, but can (unfortunately) so easily become adversarial.
I think it most often arises when companies de-value the benefits of QA.
Regrettably, many companies have two cultures: the actual culture and the aspirational culture shared in "feel-good" presentations. In the aspirational culture, the company values QA and factors in time for developers to support it. In the actual culture, it is often the opposite.
Unfortunately, as developers, we often have almost no clear requirements prior to a task. We often find ourselves simultaneously developing both the requirements and the code. As a consequence, we often have nothing concrete to share with QA until after the code is completed.
Comically, we are frequently not allowed any time, even when the code is completed, to write up information/documentation. This leaves QA with inadequate information to do their job. And, perhaps even more worrying, leaves customers in a similar situation.
The problem is sometimes worsened by ill-advised methodologies that require QA to begin testing simultaneous with the process of coding. It is absolutely possible to design tests for something with clear requirements, before coding is completed. It is similarly possible to be "agile" and start coding with unclear requirements. It is not possible to do both. This is simply fallacious thinking.
Sometimes, this leads to friction between the development and QA teams, since we are given competing agendas by the company. This can result in development misdirecting frustration at QA and vice-versa. They are simply both put in a bad situation by their company.
My guess is that sort of disconnect between aspirational and actual company goals, for development and QA, will always exist. Its simply too seductive for companies to chase short term gains at the expense of long term success. Regrettably, team cohesion and morale are the predictable casualties of that approach.
|
|
|
|
|
I only worked for small firms that had a you build it, you test it policy. It is more fun to get the software look at and think if I was a user I would try this... The issue was there was no QA then it started to grow...
|
|
|
|
|
Left one by company entrance (7)
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Scrotum.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
You left your scrotum by the company entrance? Wow, that was a Saturday night... 
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
And the best about it is that it makes me laugh every single time. I'll never grow up.
|
|
|
|
|
Sounds like I see inside Portuguese city balcony (7)
|
|
|
|
|
Could be ... I take it you don't want to do it tomorrow?
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Ah, I know the answer now. Tom's clue made it really easy, and it fits you clue perfectly... Personally I think that qualifies as the correct answer from Tom
|
|
|
|
|
It's only a correct answer if you say the word - but Tom did, so he's up tomorrow. 
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I think you win. The answer is now very obvious after your clue, so it's basically like you answered it... right?
|
|
|
|
|
|
Ok I'm up for tomorrow. Will be after a wine tasting though so it might be a bit messy
left = port
one = i
by company = co
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
