Category: IT Project Management

Dodgy software releases and a house brick…

Posted on by The Information Badger in Information Technology, IT Project Management, Processes and Practices, Software, Systems Integration

The Badger’s first thought on hearing of the recent global IT outage was that the cause  would be a cyber-attack or a messed-up change of some kind. It turned out to be the latter, which triggered a smile because the advances in tools, techniques, processes, and professionalism over the last three decades, hasn’t made it impossible to release software that causes havoc! The outage is a reminder that there’s some fragility in the underbelly of our computerised world, that complexity always comes with risk, and that individuals and enterprises should never have all their eggs in one basket.

The Badger was reminded of his involvement in stabilising and completing a troublesome software project a few decades ago. The software was installed in the client’s premises and being extensively tested on computers that were connected to specialist equipment and other systems. The project team was focused on the defect fix, build, and release cycles needed to support the testing, which was  producing a continuous stream of faults, many more than anticipated. The fix/build/release team, under enormous and intransigent internal and client pressure, struggled to make inroads to the growing defect backlog, and to produce timely update releases. Costs escalated, shortcuts were taken, release quality suffered, and the client was angry that new releases fixed some defects but introduced new ones! The team were demoralised, defensive, and disgruntled. Team spirit had evaporated, and financial incentives were making little difference.

The situation was improved by two things. The first was the injection of hard-nosed,  technically-savvy, leadership that kept all stakeholders at bay and also demanded rigour, quality, and process professionalism from the team. The second was to use a house brick to rebuild team spirit! Every Friday, a team member was allocated the brick for having made a mistake of some kind. The brick sat on their desk until it was reallocated the following Friday (if someone else had made a mistake). No one wanted to be a recipient of the brick! Rigour, process diligence, and fix to release quality improved. The brick also triggered good-natured banter across the team whose morale, motivation, and cohesiveness improved dramatically. On project completion the brick was mounted on a plinth and presented – amidst raucous merriment – for posterity to the person who’d received it the most! No one ever took offence at being awarded the brick, but would that be the case today? Doubtful.

Those whose change caused the recent global IT outage were probably a team of good people operating under relentless pressure from their stakeholders. Lessons, of course, must be learned, but deriding them for a mistake that exposed a global IT fragility would be a mistake. You never know, deploying a humble house brick might help them ensure they don’t make the same mistake again…

People – they are always a challenge…

Posted on by The Information Badger in Business, Education, Human Resources, Information Technology, IT Project Management, Leadership & Management, Recruitment

How would you answer if someone at the start of their IT-sector career asked you ‘What’s the most challenging thing you’ve encountered throughout your career?’  Your answer might be something personal like, for example, a family, financial, or health matter, or it might be something purely professional like a task that proved especially testing, getting the right people into the right roles to deliver project or business objectives, or coping with change during rapid organisational transformation or growth. You will have your own answer, but what’s the Badger’s? Well, it’s one word, and that word is ‘people’.

In the Badger’s experience, people are crucial for success, but they are a never-ending challenge! Why? Because people have unique backgrounds, experiences, thought processes, perspectives, fallibilities, strengths and motivations that make them a melting pot of unpredictability and surprises! An illustration from the Badger’s first role as a project manager is pertinent. A graduate programmer, a lady two years out of University, had been recruited by the Badger’s employer. Her CV looked good, and she’d done well during the recruitment process. The Badger’s line manager charged him with using her to fill a vacant programming role on his project team. She seemed like a good fit, and she appeared to have settled in well by the end of her first week with the team. Within a month, however, the project team were mutinous! Her work was poor, she had not completed any task, her attitude was surly and self-centred, and her timekeeping was appalling.

Chats with the Badger to encourage improvement and explore whether there were any hidden underlying personal problems proved fruitless. Formal HR processes came into play, during which it became clear that this person wasn’t interested in programming, being part of a team, or a career with the company. Employment with any company, she ultimately admitted, was simply her way of obtaining money for expensive holidays! She was exited from the company. The Badger learned that there’s more to people than is visible, that they are complex, have values that might differ from your own, and that they can take up lots of valuable management time!

The fact that people were the Badger’s most challenging thing throughout his career is not surprising when life is dynamic, circumstances change, and individuals are always adapting to new personal and professional situations. The Badger always rose to the challenge, because people from the most junior to the most senior matter if you want to succeed. With the relentless progress of automation and AI, it’s easy to think that dealing with people is becoming less relevant. Not so! AI may change everything, but it’s people who are crucial to harnessing its potential to making a difference. People will always be a challenge, but knowing more about what makes them tick will be essential for handling the challenges of the foreseeable future…

Work-life balance and an unexpected call from the CEO…

Posted on by The Information Badger in IT Project Management, Leadership & Management, Life, Project Management, Wellbeing

Summer beckons and many will be looking forward to a break from work to enjoy a holiday. Modern technology, however, means that it takes an iron will not to occasionally check work email when relaxing on the beach or quaffing beer in a bar in the evening. Completely detaching from work while on holiday is really important because it benefits your mental and physical wellbeing, and it makes you more focused, creative, and productive on returning to work. A refreshed mind, for example, generates better ideas, is more objective and productive, and is more creative when problem-solving.

The Badger normally took a two-week summer vacation throughout his career. One year, however, after leading a major fixed-price, IT system delivery to completion, his employer approved a three-week break to enable his batteries to fully recharge! The project had been challenging for the whole team from the outset. Everyone had done a magnificent job and were exhausted. The Badger’s three-week break proved to be seminal. It was the first time that he truly detached from every aspect of work while on holiday. The break fully revived his mental sharpness, physical energy, and motivation, and it produced much greater awareness that work-life balance is important no matter what role you fulfil at work.

The Badger returned to work afterwards refreshed, focused, and determined to establish a better work-life balance. On his first day back, while liberally applying the delete key to his email backlog, the company Chief Executive called unexpectedly. Caught off-guard, the Badger’s initial surprise and immediate pang of anxiety quickly dissipated. The CEO wanted the Badger, a delivery practitioner, to join the company’s overall leadership team to oversee all projects across the company. The CEO sensed the Badger’s hesitation and made three points. Firstly, that it was a good career move and also what the company needed. Secondly, that the role would broaden the Badger’s leadership skills, his perspective of how the company operated, and that it would  sharpen the overall leadership team and improve decision-making with company-wide impact. The third was that delivery actually produced the company’s profits, and so home-grown delivery leadership talent was preferable for the role rather than  recruiting externally.

The Badger mentioned his greater appreciation of work-life balance. The CEO chuckled and noted that while every person is different, the reality was that intelligent, focused individuals who want job satisfaction and success find a balance that enables them to achieve these objectives. The Badger took on the role, never looked back, and learned over the years that the CEO was right. Successful careers are built primarily on hard work and getting the job done, and finding the right work-life dynamic that works for the individual and their personal circumstances…

A first-time Project Manager and scrutiny…

Posted on by The Information Badger in Delivery, Information Technology, IT Project Management, Leadership & Management, Processes and Practices, Project Management, Risk, Training

In times or yore, a young Badger was appointed to lead a new project developing software for an important client. It was his first time as a Project Manager! After six months, however, the Badger seriously doubted his suitability for the role. The initial enthusiasm, excitement, personal glow and motivation from knowing that your boss believes you have what it takes to be a Project Manager had been replaced by gloomy self-doubt. The project was on track, the team members was working well, and the client was happy, so what was the problem? Put simply, the Badger felt bogged-down with – in his view – unnecessary company bureaucracy and intrusion that encroached more and more on the time to lead the project.

In those days, all company employees had ‘a counsellor’, an experienced person outside the employee’s immediate chain of command, who acted as both a mentor and an independent performance appraiser. Employees met their counsellor formally twice a year, and one such meeting happened to be around six months after the start of the Badger’s project. At this meeting, the Badger shared his bureaucracy and intrusion misgivings and whether he was suited to a Project Management career path. His counsellor chuckled and said ‘Everyone initially struggles with scrutiny in their first leadership role because no one likes to be scrutinised. First-time project managers often underestimate the scrutiny that goes with the job!’ The counsellor was right. What the Badger labelled as unnecessary company bureaucracy and intrusion was largely the scrutiny that‘s part of good corporate governance and operational control.

The counsellor emphasised that embracing scrutiny was important because it builds trust and provides assurance that nothing is being hidden, whereas resisting it creates suspicion, distrust, and even more scrutiny! As an aside, they observed that the level of company scrutiny experienced can be a qualitative indicator of a company’s health, because the absence of it implies anarchy and ultimately company failure. Overbearing scrutiny of everything all of the time, on the other hand, suggests organisational constipation, risk aversion, stifled creativity, and likely underperformance compared with rivals in the market. The counsellor concluded with ‘As a Project Manager, you are actively managing your client and your team, but you must also actively manage your company scrutineers and their agendas’. Over subsequent years as a Project Manager that is exactly what the Badger did!

The Badger’s IT delivery career eventually took him into a senior, company-wide, delivery and business role that included being a scrutineer! Most of the first-time Project Managers he encountered as a scrutineer were better trained and supported and embraced scrutiny positively. Experiencing them trying to influence and manage the Badger was always fun, because when you’ve been in delivery for decades you know all the Project Manager’s angles and how not to be defected from your agenda!

Leadership; never, never, never give up…

Posted on by The Information Badger in Information Technology, IT Project Management, Leadership & Management, Life, Psychology, Training

In May 1940, Winston Churchill became Prime Minister to lead the nation through World War 2. As this old item on leadership highlights, he was a ‘chubby, stoop-shouldered, funny faced man…and political has-been’ whose career in politics had been patchy. Nevertheless, his leadership proved to be just what the nation needed. On this death, his state funeral on 30th January 1965 was watched on television by over 350 million people around the world.  Televisions and global communication at the time was, of course, rudimentary compared with the norm today. A very young Badger was among that TV audience, watching black and white pictures of the funeral with his parents on an old Bush television with thermionic valve circuitry in the corner of the sitting room.

Little was said, but at one point the Badger’s sombre father leant over from his armchair and said ‘Son, remember Mr Churchill’s words – never, never, never give up. They’ll  stand you in good stead through life’. Those words have never faded in the Badger’s memory, and they came to the fore again last weekend when a visiting cousin asked the following over a family meal – ‘Do you think your career as a leader was due to being born a leader, or due to the training you received?’  The Badger told his cousin, a talented artist, that it was both, and that although much is written about the attributes needed to be successful leaders (just Google the subject), there’s no simple answer to whether leaders are born or trained. Psychologists signal that leaders are born with some relevant attributes but always need training to develop others.

An entertaining discussion unfolded, and we chortled when the Badger’s wife noted that Winston Churchill was evidence that you can’t tell if someone is a leader from just the way they look! The Badger’s cousin was interested not only in the Badger’s view of key leadership attributes gleaned from his experience in the IT industry, but also whether they derived from inherent personality or training. The Badger quickly summarised his view of the most important leadership attributes as integrity, rationality, objectivity, an ability to remain positive with a ‘can do’ attitude in the toughest of circumstances, and a focus and determination to get things done in a way which energises others. The Badger added that he felt these attributes come from personality and normally come to the fore from being exposed to new or challenging experiences in life and at work. If you are never exposed to new things, then you’ll never know if you can be a leader! Training alone never makes a successful leader.

Remembrance Day is a few days away. Churchill’s leadership is an apt reminder that you can be a leader and handle any difficult situation if you have an inherent personality and mindset which has ‘never, never, never give up’ at its heart.

Expect the unexpected; when the unexpected happens, respond rather than react…

Posted on by The Information Badger in Business, Delivery, IT Project Management, Leadership & Management, Project Management, Psychology

The very first Project Management training course the Badger attended early in his IT industry career seemed of questionable merit. It was a residential course for Project Managers drawn from across all the business sectors in which his company  operated. Attendees arrived on a Sunday afternoon and ultimately departed mid-afternoon on the following Wednesday. At the time, it was common for people to be actively performing a Project Manager role before attending any associated training course, and so everyone on the course was already actively managing software and systems projects under a variety of contractual arrangements.

Most of the course sessions focused on the process and practice of managing a delivery/development lifecycle, risk, finances, and the basics of contracts and change control.  The format was rather dry but provided some useful reminders. At the end of the course, however, most attendees questioned whether being away from their projects had been a useful use of their time. There were, however, two overwhelmingly positive points of feedback, namely a) the usefulness of meeting peers and sharing experiences, and b) the closing, hour-long, Q&A session during which a senior business leader answered wide ranging questions from attendees.

Whilst the Badger came away rather ambivalent about this course, it had provided a useful reminder that Project Management is as much about people, as it is about structure, lifecycles, processes and practices. In fact, the primary thing that has stayed with the Badger from the course ever since are the wise words of the senior business leader in the closing Q&A session. When asked to give one piece of advice that everyone present should take on board, they said ‘Expect the unexpected, and when the unexpected happens, respond rather than react’. They explained that no one can avoid the unexpected, that some people are better at dealing with it than others, and that some people react emotionally, feel anger, panic and fear, become agitated, and initiate  knee-jerk moves to action that compound matters and alienate others.  Others respond rather than react. They stay calm, focus on the facts and what they can control, assess the options before progressing a plan of action, and unify and encourage those around them.  The business leader told the audience to remember to respond rather than react.

Throughout his career, the Badger encountered many leaders and managers who had to deal with the completely unexpected. Many reacted rather than responded ! This was a constant reminder that everyone is different, and that being a leader or manager doesn’t provide immunity to the core traits of your personality. Perhaps that first Project Management course was of more value than seemed at the time, because it sowed the seed of awareness that to be a truly successful leader or manager, then you must learn how to respond rather than react to the unexpected…

Are optimists, pessimists, or realists the most successful leaders?

Posted on by The Information Badger in Information Technology, IT Project Management, Leadership, Leadership & Management, Project Management, Psychology, Risk

The Badger was asked many times during his career to engage with delivery and business leaders encountering serious problems delivering a contracted project to requirement, time, and budget. These requests were often initiated by the company’s Chief Executive who simply asked the Badger to ‘chat with those responsible and see if you can help’. They knew the Badger would interpret the request as ‘get stuck in and get the  problems on this contract resolved’. Being aware of the personal traits of the people you deal with, especially those in senior positions, is crucial to interpreting what they really mean when they ask you to do something!

One such ‘how can I help’ conversation with a business leader proved memorable because it spawned a hypothesis that the Badger feels has been validated over the years. Although we knew each other in passing, it was the first time we had met for any substantive conversation. After some initial chit-chat, the business leader quickly focused on describing the delivery, financial, and contractual difficulties of their project. They had, apparently, already spoken to a couple of experienced staff about helping to resolve the difficulties, but neither was, in their eyes, suited to the task. They described one as a cheery but superficial, glass-half-full optimist, and the other as a pedantic, too laid-back, glass-half-empty pessimist. The Badger remembers wondering how he would measure up!

After an hour’s discussion, the business leader asked the Badger to help resolve the project’s problems, adding that ‘you are a realist and you don’t care whether the glass is half full or half empty, only that the glass is a receptacle to be filled with as much liquid as possible’. Their comment spawned a hypothesis in the Badger’s mind, namely that the delivery and business leaders who have the most success, and also the longest careers, are realists. Engagements with many diverse business and delivery leaders over the years have tended to reinforce the hypothesis.

Being a realist means having a personality with a propensity to take measured risks and take measured decisions. It doesn’t mean never demonstrating optimism or pessimism. Those with an optimistic, glass-half-full, leaning tend to be less risk-conscious, while those with a pessimistic, glass-half-empty, leaning tend to have little appetite for risk at all! During COVID-19, for example, glass-half-full characters might have seen themselves as less at risk and taken less precautions, whereas those with a glass-half-empty outlook might never have left their house at all. Realists, on the other hand, would have taken measured risks based on knowing that the virus’s impact mainly depended on age and underlying health.

The Badger’s seen glass-half-full, and glass-half-empty leaders be successful, but it’s the realists who’ve been the most successful and had the longest careers. Is the Badger’s hypothesis sound scientifically? Don’t know, but he’ll stand by it until a proper people expert shoots it down in flames!

Problematic underperformers – the dog must wag the tail!

Posted on by The Information Badger in Business, IT Project Management, Leadership & Management, Project Management, Risk

As the first day of a conference broke up, attendees moved to the venue’s bar to network, gossip, and share thoughts about the day’s sessions. A young project manager, however, sat alone in the venue’s lounge looking as if the world rested on their shoulders. The youngster smiled weakly and raised a hand in recognition as the Badger walked by. ‘Why so glum?’ the Badger asked before sitting down in an adjacent chair. ‘An underperformer is proving to be a problem that’s jeopardising the success of my project’ came the morose response.

The youngster explained that a person on a team on the critical path of the project was seriously underperforming, proving impossible to manage, and putting at risk the timely completion of contractual deliverables. The person had apparently been troublesome from the outset, but their team colleagues were now vocally grumbling because this individual was always late for work, always left on time at the end of the day with their work unfinished, and always blamed others for their poor productivity and low quality output. The individual also complained about everything! Performance management processes were in progress, but the person was using every nuance, ambiguity, and avenue for defence in the system to frustrate their execution. The young project manager asked if the Badger had any thoughts.  

The Badger stated that a rule of thumb which had stood him in good stead throughout his career was that ~10% of individuals on a project were underperformers.  Most were good people who were either in a role unsuited to their talents, or juggling with challenging personal or family situations, or both. Most did not poison a team’s spirit or damage overall output. A small proportion of underperformers, however, were truly work-shy individuals, with poor capability and often obtuse personalities, and somehow they had slipped through in the company recruitment processes. These individuals often distracted management, poisoned morale, and destroyed team spirit and the productivity needed for a team and project to succeed. The Badger said that he’d learned that these individuals must be dealt with by those in leadership positions in line with formal processes, but swiftly and decisively if positive project dynamics were to be preserved.

The youngster whined that diversity, harassment, and anti-discrimination policies made their ability to take swift, decisive, action more difficult. The Badger shook his head and simply reinforced two points, namely that a) their primary responsibility was to deliver to their client on time, to budget, and in line with their contract, and b) that allowing a poison apple to infect the fruit in the whole barrel was a leadership failure!

Later that evening the youngster bought the Badger a drink in the bar and said they’d made some phone calls and removed the problematic individual from the project. ‘I’ve learned’, they said, ‘that leadership involves decisions, judgements, and the dog wagging the tail, not vice-versa!’  Quite!

Walking out of a meeting with a client…

Posted on by The Information Badger in Business, Delivery, Information Technology, IT Project Management, Leadership & Management, Learning, Project Management

‘Meetings, meetings, meetings!’, a delivery leader exclaimed irritably after a session with a client who had given them the verbal hair-dryer treatment about an imminent milestone and its associated payment. ‘They don’t want to pay, even though we’ll have met the milestone in full’, the leader grumbled before berating themselves for not having walked out of the meeting. The Badger smiled. Memories of his own difficult meetings with clients came flooding back.

Notwithstanding the comprehensive training in meetings and negotiations that companies provide, it’s real experience in difficult client meetings that hones your  approach to getting the right outcome. The Badger’s approach developed over the years to have essentially three things at its core. The first was that the client is not always right, and that being in command of irrefutable facts, and using them calmly, consistently, and assertively rather than petulantly and confrontationally, is crucial to getting the desired outcome. The second was mental resilience, to have as much background to the client’s position as possible, and to decide tactics that are unwaveringly focused on the desired outcome, before the start of the meeting. The third was to always have a walking out option in the kitbag as a weapon of last resort, but not for use to assuage personal ego or frustration.

Had the Badger ever walked out of a client meeting, the delivery leader asked? Yes, but rarely. One occasion was some months after a system with a fractious delivery history had become operational with a client’s end-users. The meeting was to a) formalise that the delivery contract’s deliverables had all been delivered, and b) that the client would make the final payment due and close the contract. It should have been a formality, because the client’s staff had already confirmed everything had been delivered to contract and to their satisfaction. Item (a) was indeed confirmed at the meeting, but the client refused, without giving any reason, to pay the outstanding money.

During a break, the Badger and his team agreed we were wasting our time because the client had no intention of paying. After the break, the Badger asked the client to confirm that although no contractual deliverables remained, they would not pay the money due. They confirmed this, and the Badger got up and left followed by his team. The shock on the client’s team faces was palpable. It was not something they’d anticipated!  Payment was received three days later after the Badger’s CEO phoned the chairman of the client’s Board of Directors to complain and threaten litigation if users continued to use the system.  

With a twinkle in their eye, the delivery leader looked at the Badger, grinned broadly, and said ‘I was wise not to have walked out. If I had, the client might have thought I was a petulant, over-sensitive, snowflake with no backbone’.  The Badger laughed aloud…

Upset your client and spoil your career…

Posted on by The Information Badger in Delivery, IT Project Management, Project Management

What’s the saddest thing you’ve see happen o someone you’ve been working with? Bereavement is excluded; the answer must be something the person has inflicted on themselves. A youngster, chatting to the Badger socially, asked this very question the other day. Surprised, the Badger played for time and asked what had prompted the question. They shrugged their shoulders, and simply said that a couple of their project team lacked common sense and sadly seemed oblivious that this was spoiling their career prospects. The conversation was interrupted by someone else, and so the Badger didn’t get to answer their question, but if he had, it would have been along the following lines.

One instance of the saddest thing someone inflicted on themselves comes to mind because it illustrates what can happen when a personality with embedded behaviours gained at one company, proves to be mismatched at another company in a different sector.  The circumstances were as follows. A senior delivery leader was recruited by the Badger’s IT sector employer from a large international defence company to run a major, fixed-price, high-profile IT contract of strategic importance to the client. The printed contract documentation filled numerous lever arch files and the person recruited, who joined the company before contract signature to lead mobilisation and then delivery, insisted on having an A5-size printed copy for their briefcase.  

Grumblings soon emerged as delivery got underway and the individual became the focal point with the client. Tensions within the individual’s team, due to their self-important, patronising, ‘I know best’ personality and an approach to delivery ingrained at their previous employer, also quickly became evident. The team started disengaging from their leader because of their arrogance, failure to listen, and inept people skills. Ever louder grumblings from the client came because the individual reached into their briefcase at the start of every client meeting, theatrically put the A5 copy of the contract on the table, and then referenced or checked it as part of every conversation. Client requests, and those from company executives when the client escalated, not to do this were ignored. A contract is never an irrelevant document, of course, but there’s a time and place for waving it about and it’s not in every meeting! Eventually the client refused to have any dealing with the individual.

Seeing the individual damage their career by failing to recognise that their modus operandi was upsetting the client and damaging the effectiveness of their own team was very sad. They were moved, never ran a delivery again, and never accepted that the spoiling of their career was self-inflicted.  There are always exceptions, of course, but upsetting your client and your team by letting arrogance and self-importance dominate your modus operandi, is almost certainly going to spoil your career. Keep this in mind if you don’t want to spoil your career and be someone else’s saddest thing anecdote…