Reply to: You're a consultant

[d000hg]

Bung it on the risk and issue log

And don't forget to schedule a requirements workshop.

[pjclarke]

you got renewed?

I did, several times. In fact I was there long after the big project for which Logica had been engaged had been delivered and they had been thanked for their services and shown the door. Nice gig, 30 mins from home, which when home is in the Peak District, is pretty rare ...

[vetran]

In my early days as an 'independent', sitting in a 'design meeting' at ClientCo, the other attendees are all from (i)Logica.

Lead Logica Bot: 'We have to do what is in the client's best interest on this one'
Me: 'So when would you guys not do what was in the client's best interest?
<awkward pause>
Lead Logica Bot: 'so, moving on ...'

you got renewed?

[pjclarke]

In my early days as an 'independent', sitting in a 'design meeting' at ClientCo, the other attendees are all from (i)Logica.

Lead Logica Bot: 'We have to do what is in the client's best interest on this one'
Me: 'So when would you guys not do what was in the client's best interest?
<awkward pause>
Lead Logica Bot: 'so, moving on ...'

[suityou01]

Two points to Scooter.


Sent from my iMinion using Tapatalk

[scooterscot]

Einstein had a saying.


Sent from my iMinion using Tapatalk

Yes. Doing the same thing over and over again and expecting a different result is madness. Or something to that effect.

[Mich the Tester]

I got asked to help with ''improvements'', what they actually meant was making more work where there wasn't any need and making things even more complicated and obscure than the beginning.

Make lots of documents with lots of lists that have to be maintained in different places, and then you can ensure there is no time left for decent testing!

[scooterscot]

The key is to not overstate the probability of downstream risk, but play up consequences of the risk occurring..

That's the trick. But like was said earlier by 'doodab' sometimes you just need to give up on some. They can't all be saved. There's always going to be "we've being doing it this way for years" sort, nearly every failed business in the UK has the result of this attitude. Those that don't change die or have deep pockets to buy their way out of the mess or are a government project and the taxpayer picks up the tab.

[suityou01]

Einstein had a saying.


Sent from my iMinion using Tapatalk

[norrahe]

Ah yes, they have that here too, and they even call it 'best practise'. When things go wrong, they insist that best practise should be followed next time around, in other words, do the same thing, but do it harder.

I got asked to help with ''improvements'', what they actually meant was making more work where there wasn't any need and making things even more complicated and obscure than the beginning.

[Mich the Tester]

It's also known as ''but we've always done it that way''

Ah yes, they have that here too, and they even call it 'best practise'. When things go wrong, they insist that best practise should be followed next time around, in other words, do the same thing, but do it harder.

[norrahe]

These two words are each, on their own, quite harmless, but when combined in that order they annoy me quite a lot.

It's also known as ''but we've always done it that way''

[speling bee]

Where I am is pretty entertaining. They have a big project, with a waterfall methodology. And BA. And a test team. Guess what, it's on time, on budget and the quality is good.

My project has me. It needs a bit of time from a software architect, a touch up from a BA, a smidgeon of testing.

Of course any resource requests from me cannot be bet as there aren't any free resources.

Then I find out that I am now fielding front line support requests as well as being a BA/Coder/architect/tester. Fair enough and I fully understand that "it goes with the territory".

"When will it be ready suity?"

"That's anyone's guess really"

"Wha????"

"Goes with the territory".

Make a space for me on the bench will ya.

Suuuuiiiiityyyy!

[speling bee]

This is the trusted advisor deal. You need to carefully establish credibility. The key is to not overstate the probability of downstream risk, but play up consequences of the risk occurring. So the likelihood of the release going wrong, even though you've taken every chance in the book is still quite low, but if it does go wrong ... You may go out of business ....

My other tip, document in Crayon, keep it very very simple, no long words or intricate diagrams. You know they are children, so don't overload them. They will actually thank you for this.

Can you stop raising the tone please?

[suityou01]

Where I am is pretty entertaining. They have a big project, with a waterfall methodology. And BA. And a test team. Guess what, it's on time, on budget and the quality is good.

My project has me. It needs a bit of time from a software architect, a touch up from a BA, a smidgeon of testing.

Of course any resource requests from me cannot be bet as there aren't any free resources.

Then I find out that I am now fielding front line support requests as well as being a BA/Coder/architect/tester. Fair enough and I fully understand that "it goes with the territory".

"When will it be ready suity?"

"That's anyone's guess really"

"Wha????"

"Goes with the territory".

Make a space for me on the bench will ya.