Showing posts with label project management. Show all posts
Showing posts with label project management. Show all posts

Tuesday, 10 December 2019

Unanimous points scoring for my TOGAF® 9 Combined bout


Catching up with the times
It would be easy to write a motivational post, but that is not really my way of doing things, rather, I will just tell my story.
As I related in my previous blog on passing my PRINCE2 Practitioner certification last Thursday morning, I was suddenly furloughed a month ago and rather than sit at home twiddling my thumbs, I considered going on a PRINCE2 course and when I was booking the course, I was offered a bundled deal to do both PRINCE2 and TOGAF certification which just happened for fall on consecutive weeks.
Like project management, I was first introduced to TOGAF just a few months after recovered from cancer by an ex-colleague. I went as far as buying the study guides and registering on The Open Group website, that was just 9 years ago, but nothing really came of it. I even explored doing the course in South Africa then, I eventually went to India instead to attend courses for Microsoft and Cisco certifications.
Keeping the faith
I suppose what made TOGAF a bit of a chore was the volume of theoretical processes that I thought only a classroom training environment could help ameliorate. The Knowledge Academy for all its poor customer service record does appear to have some really good trainers. Mustafa Ahmed took our TOGAF course and from the first day, I began to have confidence, it could be done.
This was my second week of courses and something seemed to have triggered an immune response in me that by the third day of the course, I was coughing, spluttering and running a fever that I had to return home early without acquiring anything. The trainer sent me an update of what was covered for the day and I was able to return for the fourth and last day of the course.
His advice was to take the test within two weeks of the course, or we’ll begin to forget what we had learnt. I first had to get PRINCE2 done from before I could begin to think of scheduling the TOGAF test.
Brought to the edge
It was an exasperating ordeal to get the Exam Bookings department of The Knowledge Academy to forward me the test voucher, it took 3 emails and 4 phone calls over 8 days to get that resolved. The service is an atrocity that makes an appalling review appear too generous for words.
You’re tested to the point of losing your cool and in my view, the staff care not a jot about the frustrations of their customers. It is a test of patience that one has to pass.
When the voucher arrived, I found I could not get a test window at any of the Prometric Vue test centres up north in Manchester, Liverpool, Leeds or Birmingham. Only one test centre London had availability and so I chose to travel to London to take the test today. The test centre could do with bigger monitor screens.
Tested to the limit
I was caught in a quandary of my preparedness, having acquired the official study guides, the full standard documentation and a pocket guide. Something seemed to be missing until I found a YouTube video TOGAF® Level 2 Exam Questions – Tackling Those Effectively! This in addition to the tips I got on the course meant I could be boxing clever to win this match.
The TOGAF® 9 Combined Part 1 and Part 2 Exam is 40 questions for Part 1 in 60 minutes, immediately followed without results for 8 scenario questions for Part 2 in 90 minutes. I raced through Part 1 reviewing a few thorny questions and was done in just under 33 minutes. Part 2 was harder, the recommended approach is 10 minutes per question, I spent 18 on the first and had squandered 30 minutes without a satisfactory answer for the second. Open book tests don’t mean easy results. You will in some instances be told where to go in the TOGAF standard document, it doesn’t make it any easier.
I tried some and skipped some that I returned to for review, by the end, I had just 3 minutes to spare and passed both Parts. Part 1 presents a bit more difficulty as it relies upon memory and specifics from the TOGAF documentation, Part 2 is about the application of the TOGA methodology and I did much better on that by far.
They helped me do it
On reflection, I marvel at the determination and daring that saw me decide to take two highly process-driven courses with much documentation, standard and theory, just 4 weeks ago and in that time clear both tests that give me certifications in project management and enterprise architecture.
Yet, without the amazing support of Brian my partner and my friends Funmilola and Kola, I probably would not have had either the courage or determination to see this through. They are my cheerleaders, constantly telling me I can do it and do it well. It gave me such great pleasure to share my successes with them.
Now to new challenges and rewarding prospects. There is the minor issue of a holiday in South Africa to plan now. Phew! It’s done.

Thursday, 5 December 2019

On becoming a certified PRINCE2® Practitioner


The tough thing
This morning at 7:40 AM, I clicked the ‘End Test’ button of my PRINCE2 Practitioner 2017 test, responded to a survey about my experience and waited for a few seconds for the test result to show.
It was a somewhat tough test, but I did not think I needed anymore study after all the work I had put in towards passing this test. However, I believe by process and application, I should be able to put my knowledge to good use and by that become an effective project manager.
My projected life
My working life has generally been impacted to various extents by project managers, ones who follow process and procedure and some that care nothing for the orthodoxy, they blag their way with offering the customer the impossible, harass their technical personnel to produce gold from dross and their ultimate goal is rarely to deliver a product or service but to tick boxes.
To say I have little time for such project managers would be an understatement. Whilst, I have not come to blows with any, I have found the unspeakable to say straight to their faces. I know the quality of work I want to deliver, and it would not be shoddy no matter who the project manager is. If you cannot first understand what it takes to deliver before you promise what can be delivered, then you will have to take up the consequences for why tolerances have been stretched and exceeded.
Schooled in hard knocks
My first encounter with formal project management processes was during my postgraduate course some 15 years ago, I took it as my second module, and it was an exercise in stress management and control towards delivery.
We were a team of 5 who had to take up the slack for one of us who was never present, never engaging and never delivering. Yet, he had the effrontery to demand that we make all allowances which could have left us all failing the module. The lecturer decided not to mediate but watch how we handled the tough issues.
We delivered our goals despite the issues, but the biggest lesson I took away from that experience was that I did not want to be a project manager. Our project management module was based on the Project Management Institute (PMI) Project Management Body of Knowledge (PMBOK® Guide).
Not wasting time
Then, just 3 weeks ago, I was notified that I would be furloughed, on knowing this, I decided I would spend the time attending some courses. There is probably a lot I can do on the technical side, but I also need to leverage elements of 30 years of expertise in the coordination of projects, programmes and portfolios.
After taking some advice from a colleague project manager, I looked around for PRINCE2 classroom course and ended up with one provided by The Knowledge Academy. My enquiry led to being offered a deal that allowed the back-to-back courses for PRINCE2 Foundation and Practitioner combined in the first week and the TOGAF 9.2 Part 1 & Part II in the following week.
Getting ready for love
Apart from the preparation for the course, I had access through my PluralSight subscription to the retired PRINCE2 2017 course which I could run and learn from, then I also found the Projex Academy Prince2 Masterclass at cost, which had a rather innovative approach to covering the PRINCE2 syllabus.
The Projex Academy YouTube video PRINCE2 2018 MASTERCLASS Foundation Exam Tips and Hints, gave me the confidence to decide I had done enough to go for the test.
I had passed the paper test for PRINCE2 Foundation at the end of the second day of the course and then had to wait for the exam voucher from my course provider to schedule the PRINCE2 Practitioner test.
What a bother
This was fraught with a few difficulties as it is proctored online giving you the opportunity to run the test from home. However, to have a sterile enough environment to sit for a test for 150 minutes without being disturbed whilst keeping the setting clean enough not to contaminate the examination setting with material that could compromise the integrity of the test looked like an insurmountable problem.
I also could not find test centres to fulfil that need apart from opting for a paper-based test. I needed to find a hot desk office or boardroom. However, to schedule an online proctored test, one needs to find a slot that makes a proctor available for that slot. My solution after much uncertainty was to schedule the slot first, which I got for 5:20 AM, then I booked myself into a hotel. I ensured the room had a table and chair, an executive room or apartment hotel would do the job.
Testing hotel
This meant I would have no distractions and I did not have to do a spring clean of the room to have the setting that meets the requirements for online proctoring. Next, I downloaded the Exam simulator and ensured the setup with fully compatible, my laptop required .NET 3.5 and a Visual C++ distributable for the exam simulation to install. Then a number of tests for the audio, web camera and Internet connection were run. A wired connection is preferred but not compulsory.
Once that was done, I was ready for the test and I went to be bed early, my dreams overrun with PRINCE2 project scenarios. I did no additional revision, but I did tab my official manual, the Principles, Themes, Processes, Appendix A and C along with a few other pages. As the PRINCE2 Practitioner test is an open book exam, but that is as deceptive as it comes. You could easily run out of time rifling through pages looking for the piece of information that helps you answer the question.
The die is cast
When all was set with the capture of my identity document, the online proctor communicated with me by audio, he did not once show his face, but he could see me throughout the duration of the test. I turned my laptop around 360 degrees to show the room, then the table I was working on. Flipped through the official manual showed the blank sheets I would be working on and after typing in my middle name in the chatbox, I put my phone out of reach and started the test.
I wasted a lot of time on the first 10 questions out of 46 but eventually got a good pace, skipping one question until I had finished. By the time I was done, I had about 13 minutes to spare. I did not believe there was much else to review. I ended the test and my result came back as a pass.
Phew!
When I was scheduling my test, I was offered the option to resit the test for 25% of the normal cost for a resit, the offer was valid until 15 minutes before the test. It is not refundable but serves as an insurance policy. I took it, but I will not cry over the loss of it rather than getting to use it to pass if I had failed. It would have knocked my confidence a great deal if I had failed the test, but I was not going to beat myself up for it. I have failed many times before and returned to take the prize.
However, for all the activity that presaged this situation, I am happy that my PRINCE2 Practitioner certification is in the bag. Now on to new things. The support of my partner Brian and best friends Funmi and Kola have been so invaluable, I am blessed to have these wonderful people cheering me on, through the good and the bad. Thank you. Meanwhile, I lament the inglorious step down from queen to prince.


Friday, 16 October 2015

The Project Dilemma Triangle

It is as constant as life itself
I have written about this many times before, my battles with Project Managers who do anything but manage the project.
During my postgraduate course, I took the Project Management module and we were tested not by the methodology, but by the problems with personnel in the sub-group that we were in.
Each person had a deliverable within the project assignment and some received wisdom suggested that we put a time frame on when that task had to be completed after which the task was taken away from the allottee if not completed and given to someone else to complete.
A reality project course
In our team of five, one just did not pull his weight and when we took over his task and completed it, he threatened to report us for ostracism and discrimination. I withstood him at all points of this attempt to blackmail us pointing out his responsibility and apparent lack of consideration for others even if he just wanted to get by rather than excel as the rest of us did.
Meanwhile, our lecturer was watching our exchanges and in the end commended me for handling such a difficult situation calmly, respectfully and decisively. We did not make a distinction for that module, but the biggest lesson I took away from that experience was that I did not want to be a project manager.
A common-sense experience
27 years in the Information Technology profession has taught me a few home truths and it is best illustrated in what I now call The Project Dilemma Triangle.

The angles of the triangle labelled are labelled Good, Fast and Cheap, and from that I have developed a number of truisms. A very commonsensical view of projects without the attendant jargon or obfuscation with meaningless terminology.
Much as I strive to do the very best job I can, I am constrained by time, by cost, sometimes by knowledge I still have acquire and mostly by project managers with unrealistic expectations. The project managers I have worked best with are those who have taken the time to come to understand what I am doing, what I am thinking and what it takes to create a deliverable that works at implementation the very first time.
I battle daily
However, because the time and the cost is usually determined long before understanding what the work entails, the technical resource is in a bind. We are compelled to work within the constraints of the Fast and Cheap to achieve the Project Manager’s goal of the Fast and Good with everyone pretending that the Fast and Cheap will be Good and Fast. It is never the case.
Where Fast is delivering on time and Cheap is doing it on a shoestring with Good being the minimum we can get away with that appears to work, we find that we do never really get it right the first time even if the Project Manager ticks it off as delivered and the technical resource is still left with that ‘delivered’ project, firefighting issues and problems that should never have been there is the time and scope was there to get it right from the get-go.
That sums up my daily work life and the battles I am constantly fighting with Project Managers in The Project Dilemma Triangle.


Sunday, 23 November 2014

Essential Snobbery 101: Emails should not replace proper communication

Breeding annoyance
The times I have been quite noticeably shocked by behaviour and attitude are without count. That I have quite promptly upbraided people is something people who know me appreciate.
The other day, it was an email with the appeal that I be "calm, logical and professional" Some messages are not worth responding to, because there is no arrangement of words that would serve the intent as well as the put-down she deserved.
I decided that she had not, with all our dealings, begun to understand the kind of person that I am. Nothing annoys me more than the lack of courtesy, where people resort to emails in place of the essential conversation and think things are fine that way.
Proper conduct
Sadly, in my view, if you will saddle me with a responsibility, then you should chat to me. That I have acquiesced does not mean I have accepted that responsibility apart from trying to create a situation of, 'can we just get along?'
It is the same thing that informs how I travel and how I like things to be, 'just so'. There is a cost to this, but the truth is whilst some might consider me demanding or complaining. I prefer the absence of conflict borne of the fact that people know what they are supposed to do, so I do not have to ask them to do what should have been properly done.
Human-to-human conversation is still the most effective, courteous and respectful kind of communication; it shows engagement too.
Project management off the books
This is where one must say the project is losing focus, no expectations are set, no inspiration is given, and hence, there is no commitment and targets are not met.
There is the science of project management, and there is an art of project management; many have mastered the former and lack any skill in the latter. In essence, they have to bludgeon rather than encourage and escalate rather than encourage.
That they appear to be out of their depth is no surprise, and that we are to pick up Humpty Dumpty's pieces afterwards is no surprise.
If I have to insinuate myself into this situation, the quest to get things going might inadvertently expose the incompetence of others. That is why I am restraining myself, but it would not be long before knowledge and understanding meet in the realisation of somewhat all too obvious facts.
I am biding my time.

Wednesday, 4 June 2014

The accordion principle of project management

The bellow of the bellows
I have always been fascinated by the music of the accordion, the player playing the treble piano side and the pressing the bass buttons to something that sounds more like folk music than anything else.
More so, the player moves the concertina bellows, something rhythmically whilst playing keys and buttons all learnt by practice because they do not have sight of keys or buttons as they play.
Yet, I have found use for the accordion not so much to play music but in expressing the fear of being squeezed in the concertina folds of a project because other elements of time, resource and cost have not been properly managed and I am pressured to deliver to atrociously contrived ends.
The project squeeze
The project manager decides what music they want to play, the rhythm, the tempo and that is how listeners might get entertained or even dare to dance.
Some projects managers however do play such dastardly music that not only would people cover their ears, they might instead pick up stones to pelt the accordionist.
We the project resources who fall between the bass and treble ends of the accordion are squeezed until our pips squeak if we do not react, respond, advice and escalate when we need to, to ensure we are not completely crushed and carrying the blame for a badly run project.
Play that funky music
I love good music and what document as much as I can is evidence of where I have striven not be part of the bellows to help in deciding how the music is played, to whose hearing and for what purpose.
In the end, as much as the project manager, I want to be involved into making good music too, that is how the discussion went earlier today, whether good music would result is anyone’s guess, but in the cacophony that ensued, maybe some silence is what we need to retune the accordion and try a different tune.
That is the accordion principle of project management.


Thursday, 19 January 2006

Professional reputations in a rotten job

False facts force fiddles
Angst is never an emotion or state of mind one finds oneself grappling with. In professional life, it rarely ever features, since I project myself as an expert and authority in the field where the knowledge goods find a market.
This really became a dilemma when I took on a short term contract to help sort out some problems which were affecting the technical relationship between my employer and their client.
It so transpires that over the last year, they had been discussing the execution of this project such that many questions were asked, some answers were given and we can agree that some of those answers would make a jury take a negative view of evidence before them.
Business lies
Basically, there were misrepresentations which lead to certain conclusions that formed the basis of executing the project.
Businesses embark on projects hopefully as a business improvement or enhancement exercise knowing that every eventual benefit might incur an initial cost in resources, time and money.
In this case, the client already had a ceiling of costs for a project which under nominal circumstances would have had an implementation floor well above the projected and agreed costs.
GF≠C is ideal
For some, that would be a bargain, but we all know that even if your service terms were Good, Fast and Cheap, juxtaposing them would provide different results.
+        Fast and Cheap is usually not Good (Bad)
+        Good and Fast is usually not Cheap (Ideal)
+        Good and Cheap is usually not Fast (Acceptable)
In this case, the project manager having presented the ideal plan had the Sales People pare it down to the acceptable and they all ended up with a bad agreement, I now have to square that up to the ideal.
With the wealth of knowledge and expertise I bring in as well as being a resource to execute the project, a lot can be done, but none of which does well to approach the fundamental implementation floor worthy of any recognition.
My role however was one of either trying to resolve the prevailing problems or a complete re-design of the project, the former had mileage, and the latter was long dead in water.
In resolving the problems, some radical action had to be taken which for posterity would have my name attached till when some sensible assessment of what went wrong initially and that is corrected.
Speak for me - forever
I could speak for myself whilst on the project and in the company, but once I leave, having done what the customer required though that requirement falls way below my professional judgment, it makes one wonder who would speak up for me when another expert reviews the project further down the line.
My concerns for that lead me to consider walking away from the project.
I sought succour from mentors and friends which simply confirmed the notion that it would always be my call.
Weighing the consequences of protecting my professional integrity or probably pride by walking away, or trying to make the best of a bad situation by making myself available as a resource to implement what the customer wants with the best expertise I could offer.
Just not on
In choosing the latter, I had already remonstrated about the issues that were raised in negotiating the terms of the project
+        from the false assertion that they had experts of my calibre who had executed the project not only badly but wrongly;
+        the apparent lack of candour where claim and counter-claim pervaded the atmosphere till the real truth emerged in a forum of all parties;
+        the quest to cover-up the mess by subterfuge rather than owning up to the mistakes made
Those amongst many other little but significant issues have been addressed and would need to be reviewed again as this project hopefully comes to a close.
Egg-spurt needs egg on face
The only annoying bit remains that the in-house expert who has expertly made a hash of this project has not accepted the folly of his actions enough to leave this to the hired expert to first resolve and then handover with the opportunity to learn.
For me, it is a humbling experience which in other circumstances would have seen my walk out, the risk of humiliation looms but is distant from the fact that they all well know that I kicked up a right old fuss.
Once again, I thank my mentors and friends for their advice, soothing words and useful guidance, they are friends, indeed.
This time has been instructive, the people quite challenging and the project, well definitely interesting. Go figure!

Monday, 13 December 2004

A short misery of projects

Preamble
Having just concluded a module on my MSc course pertaining to Project Management, I was given the opportunity to discuss one project that suffered seriously from the interference of politics.
I rose to the occasion with this tome.
The Facts
My ex-boss - Arthus Gratedane - pseudonym - was a rabid political dog, the day was not made if someone somewhere in the organisation had not received the political equivalent of a body slam.
Anyway, in this case we had at the head-quarters of a mainly European company constituted the Infrastructure Programme Management team at just one level below the CIO office and we had opportunities for innovation and improvement of services in the organisation.
We had only recently notched up a success with the implementation of a secure remote access solution which allowed users access to their data and standard applications from any internet connection if they had their secure token.
This created a launch pad to take on many more daring projects.
Then we started with Strauss which was a new desktop environment based on Windows XP, a new domain structure based on Windows 2000 Active Directory Services and Microsoft Exchange 2000 for email.
One particular trait Mr Gratedane had was a complete unwillingness for different teams to interact, especially if they were not teams he himself built. This for us was a kind of advantage, but in general made our work ever more difficult.
This meant our well-intentioned plans met with resistance with the local support teams around the Netherlands. Mr Gratedane solved that problem by advocating the centralisation of administrative services, thus making the core expertise of the regional teams redundant and retaining only box shifters.
We were to conduct an aggressive take-over of all that disparate infrastructure then recruit new staff and handover that infrastructure to the new staff within three weeks; which we did.
Then that gave us the opportunity to railroad the Strauss solution throughout the Netherlands without subjecting the solution to a decent pilot.
What should have been a resounding success was panned and criticised not because of the quality but because of how it was implemented through management aggression and the lack of consideration.
Managers in other departments just resisted anything that was in the interest of the company that came from any team managed by Mr Gratedane, but he had the ear of the executives in everything he did so people left rather than engage him.
When it came to rolling out Strauss to other European countries with Austria being the first, we encountered the fact that we could not sell Strauss to Austria, so the project was changed to the Hydra PC project.
The people in Austria were primed to act, any minor issue was a complete showstopper, it was so frustrating and nerve-racking.
Austria already had an advanced implementation that pre-existed Strauss by at least 6 months and the company could have used that solution quite easily all around Europe, but not on Mr Gratedane's watch.
We ended up implementing a parallel system in Austria with people logging into two environments for services and data, sometimes on two PCs.
Our implementation was a very poor alternative and received even less accolades, however, we, the team had to find ways of interacting with other teams without the knowledge of the boss to help facilitate issues and make things work.
The unfortunate political atmosphere in the company, which thrived on empire building, finger-pointing and atrocious escalations lead to unnecessary waste of resources, ideas, goodwill and productivity.
As an observer it looked like company had more competition between the departments than with their competitors. If that energy had been directed to more positive things, it could have yielded probably 10% to 20% company growth year on year.
The Figures
One must say that Mr Gratedane always got sponsorship for all his projects and all were fully implemented with varying degrees of success.
We probably had more project managers than project executors at one time.
The document churn rivalled that of a newspaper house with presentations about every little detail. [1]
The Failings
What created failing projects even though they were delivered as described and intended were the following
  • The stakeholder, sponsor and senior project manager were the same person
  • Project Managers were pen-pushing administrators [2] who were not allowed to model or method processes despite the fact that they were PRINCE 2 educated or at times certified – things were done on the whim of the sponsor – Mr Gratedane
  • Responsibility and opportunity was taken for everything that went right, no matter how trivial but blame was quickly averted for problems - A typical, its my baby isn't it beautiful? Its our baby smiling, but its your baby crying - syndrome.
  • The perception of risk was minimal except for where there were competing interests within the company, then the quest to excel and deliver at breakneck speed was tempered with a bit of reasoning
  • The executors were hardly part of the assessment, decision or specification process, they were talked down to never communicated with
  • The Human Resource element thrived on motivating staff by threatening their jobs and irrelevance, never by encouraging them to do their best
  • Solutions were always delivered but the expense of goodwill and acceptance
More so, I really felt for the project managers caught in the middle of the megalomania and the chaos. Since I left in July, Mr Gratedane has become the ex-boss of 7 other senior infrastructure personnel.
This is the least palatable face of company politics and I have only reviewed on of the many.
References
Project Victim Support archives – mine.
[1] Alexis' PowerPoints were her shoulder pads...
http://akin.blog-city.com/read/389826.htm
[2] The Pen Pushers Posse Pogrom

Monday, 19 January 2004

Ineptitude unparalleled

A manager for the project-ile
You would be forgiven for thinking one has something against project managers. In fact, one does love project managers. Ones that know what a project is and then manage the project properly.
However, one has had a run of unkind fortune with a crop of the sort that defy commonsense in the face of reality and whose balls are too microscopic for observation with a microscope.
Nevertheless, there is a particularly nice person who happens to be yoked to the labour of project management, whose surname would remind you of that man-eating alligator you saw on National Geographic the other day.
His manager is of the view that he has a record of accomplishment of consistently delivering on projects in his care.
The track to ignominy or less
Indeed, he has a track record of delivering because many of the critical ends to his delivery end up on one's desk.
Being one whose personality of extroversion is too intertwined with one's job and professionalism as to be considered unhealthy, these things are done.
One cannot afford to be besmirched by the glowing incompetence of an individual ready to stitch you up for any of his failings.
You have to that one is only a fraction of the majority that cannot stand to countenance the alligator in a professional capacity – or the lack of it.
My civility tested
On more than one occasion, some emails, which might eventually feature as classics of professional put-downs, are cast as pearls to swine to our dear friend without impact; apart from highlighting his tomfoolery.
"This represents that worst set of data one has ever received in relation to data, please sort it out". Said one.
Another said, "We have to work to avoid situations where brinkmanship rules over procedural and methodical processes".
Yet again, "To now foist that error of judgment on me is completely disingenuous. Please reflect and reconsider your purpose and actions".
In a darts competition that would have been maximum points, considering this was circulated to a readership that would have cringed at the bluntness of expression.
Our friend is so thick-skinned he would have prevented the sinking of the Titanic.
I will tell you what is unacceptable
A number of instances have arisen where tin-pot little managers of no importance than heading departments in persistent vegetative state for the lack of creativity and innovative thinking.
Departments populated by a gene pool so diverse from the people who live down your street, it could give credence to evolution – God forbid!
After debunking some flawed and inadequate planning, the reply arrives – "It is unacceptable … Blah! Blah! Blah!
I will tell you what is unacceptable – It is unacceptable that
  • You commit to customers without knowing the availability of your deliverables
  • You leave out core elements of your project resources and then expect a last minute redress to sort out your mess
  • You escalate issues to solve your problems when you should have communicated effectively well before it became an emergency
  • You think you can demand goodwill having used up all political capital in pursuit of unachievable goals
  • You remain immune to knowledge
Immune to knowledge
Some people are beyond teaching or just cannot learn, when put in charge of projects in which one has deliverables, one falls a victim of unparalleled ineptitude.
Time to see the company shrink – I am stressed!

Tuesday, 13 January 2004

The Pen Pushers Posse Pogrom

The equines of time
Pressure at work emanates from a disconnect between what needs to be done and who can achieve it within the strictures defined outside one's control.
Usually, project managers, the harbingers of the technician's heartache, heartburn and consequent heart attack control the parameters of time that have one as bellows in a accordion.
The compression and extension producing melodious music to the ears of kamikaze management promising what they cannot deliver on the blood of their underlings drowns the cries of pain, as the music is the accompaniment to a frenzied foxtrot.
Beaten at their rotten game with integrity
It ought not to be so, just as brinksmanship is used to force the impossible into reality, a master equestrian can arrest the megalomania of micro-project objectives that titillate the Project Manager and redefine in terms that lay bare the achievable over the downright absurd within your timescales.
Except if 12 hours can be wrung out of eight normal working hours, additional resourcing is required the absence of which simply introduces a temporary setback allowing an opportunity to deliver late based on technical reality rather than project idealisms.
I am no hamster
One being at a point of being pressured unduly by escalations of multiple priorities drawing on one's reserves, the flustered man obtained an open cheque to estimate times to delivery.
So one did, liberally and sensibly, to their chagrin. The equestrian's mastery is in understanding the horse so that it does the bidding of the rider without hesitation, in the manner, one played for time and gained the reprieve that put the blood pressure within the confines of health young man.
One would deliver when one can, if needed faster, the Project Manager would have to shop for a hamster in a wheel.