Same old, Same old

[tractor]

....

This tulipe really gets on my nerves. It seems that every field of work has to have buzzwords, 'methodologies' and the one that really pisses me off; 'best practices' bloody hell, nothing is a 'best practice', you have practices that worked somewhere for somebody and might work for someone else in some other context, but nothing is a 'best practice' because firstly you don't know; there might be better practice somewhere that you don't know about yet, and secondly, the success or failure of any practice is context dependent.

Are we all idiots to need these protocols, processes and handbooks? My impression from the best projects I've worked on, but also the best sports teams I've played in is that if you put together a bunch of smart people who want to work together, and combine them with someone who can advise if things get difficult and can arrange the basics like workplaces etc, the 'process' and the 'strategy' and the 'methodology' all fall into place, and better still, a manner of working emerges that suits the context a hundred times better than some 'industry standard' or 'best practice'.

Most methodologies are frameworks of common sense practice, complicated by unnecessary BS that sells bloated training courses. I always remember the first role I had where Prince was involved. The PM always said that if we actually followed it, we would never deliver anything. I tend to agree.

They key point is though, that if they did practice what they preach, everything would be ready for day 1!

[Mich the Tester]

Most methodologies are frameworks of common sense practice, complicated by unnecessary BS that sells bloated training courses. I always remember the first role I had where Prince was involved. The PM always said that if we actually followed it, we would never deliver anything. I tend to agree.

Unnecessary BS put forward by some official sounding 'International Board' that's actually just a front for someone making a tulipload of money out of selling certification.

Which leads me to an idea. We just need an official sounding name.

International Board of Systems Engineering Quality. Sound about right?

[tractor]

Unnecessary BS put forward by some official sounding 'International Board' that's actually just a front for someone making a tulipload of money out of selling certification.

Which leads me to an idea. We just need an official sounding name.

International Board of Systems Engineering Quality. Sound about right?

So you want to be called SEQs?

There is a whole multi billion industry built around this stuff. Additionally, understanding how the certification process works between Boards, Examiners, training providers is an absolute bag of *****. No one wants to just provide exams, they all want to package it up with bloated expensive training. They should split out the training/exam providers for a start.

[Mich the Tester]

So you want to be called SEQs?

Very observant of you. Yes!

[Scrag Meister]

First week's timesheet approved, invoice raised and emailed onward.

[ctdctd]

Day 7 draws to an end - 14% through contract and about 30 minutes of work (internal training)

One department says they haven't got the references the other department say they forwarded on Friday.

At least it's nice and warm.

[original PM]

This tulipe really gets on my nerves. It seems that every field of work has to have buzzwords, 'methodologies' and the one that really pisses me off; 'best practices' bloody hell, nothing is a 'best practice', you have practices that worked somewhere for somebody and might work for someone else in some other context, but nothing is a 'best practice' because firstly you don't know; there might be better practice somewhere that you don't know about yet, and secondly, the success or failure of any practice is context dependent.

Are we all idiots to need these protocols, processes and handbooks? My impression from the best projects I've worked on, but also the best sports teams I've played in is that if you put together a bunch of smart people who want to work together, and combine them with someone who can advise if things get difficult and can arrange the basics like workplaces etc, the 'process' and the 'strategy' and the 'methodology' all fall into place, and better still, a manner of working emerges that suits the context a hundred times better than some 'industry standard' or 'best practice'.

As is becoming more and more apparent where I am - delivery of targets is second to su<king the bosses co<k and stroking his ego.

It is just about lies, excuses and making as much money as you can.

[Mich the Tester]

Day 7 draws to an end - 14% through contract and about 30 minutes of work (internal training)

One department says they haven't got the references the other department say they forwarded on Friday.

At least it's nice and warm.

...and compliant with ISO umpty thousand and wotsit, conforming to 'international best practises' and your SOX will match sweater 2.0.

[d000hg]

It's a bit pedantic to say we shouldn't use 'best practices' because there might be a better practice to be found. That's why BPs evolve.

[ctdctd]

Gave up on day 8 and we've mutually decided I can restart on Monday when they will have everything ready for me .
.
.
.
.
.
.
.
.
won't they?

So eight invoiceable days and three days me time

Sounds like a good relaxing working pattern to me

P.S. Sorry Scrag Meister, I seem to have stolen your thread!