The Nature of Good ‘Project Chemistry’
66% of IT Projects Fail
Only one in three software projects will turn out to be successful. According to Standish Group’s 2015 Chaos report, 66% of technology projects (based on the analysis of 50,000 projects worldwide) end in partial or total failure. More surprisingly, these statistics have been the same for the last five years, the report shows. Furthermore, 17% of large IT projects go so badly that they can threaten the very existence of a company.
On Average, Large It Projects Run 45% over Budget and 7% over Time, While Delivering 56% Less Value than Predicted
Despite such failures, huge sums continue to be invested in IT projects and written off. For example the cost of project failure across the European Union was ┚¬142 billion in 2004.
It Projects Always Come with an Element of Risk, but There Are Huge Gains to Be Had If We Can Just Avoid Some of the Factors That Contribute Frequently to Project Failure
What makes a IT project successful, though?
According to the Standish Group, a successful project is on time, on budget and has satisfactory results (value, user and sponsor satisfaction, and meets target requirements). Other measures of success are widely known and accepted as true such as getting requirements right, providing effective leadership, and having full support and engagement from sponsors and users. Without these, it’s unlikely that any project would succeed.
But there’s more to success than what is widely known and, apparently, rarely followed. To reduce the risk of failure for your tech project, here are six key actions to take on the road to success.
1. Executive Vision and Involvement
Without a Executive Senior Sponsor Its Easy for Projects to Fail with the Organizational Resistance That Accompanies Large Change
Executive involvement is a primary variable in predicting the success of an IT project. Having a leadership team aligned across an organization articulating the purpose, value, and rationale for a project goes a long way towards getting stakeholders and end-users pulling the proverbial rope in the same direction.
2. Have a clear view of scope and timetable
Oftentimes, a tech project flops because its developers fail to plan and rush forward with an idea. However, some project managers plan so meticulously that they end up falling behind and lose momentum. The best approach is somewhere in between.
Interviewing team members, documenting requirements, prioritizing what is “mission critical” versus “nice to have,” getting agreement across stakeholders can feel like a never-ending cycle. As a result, requirement gathering has fallen out of fashion with many organizations in the past few years.
However, the ideal starting point for a successful technology project is to have a set of fundamental requirements with sufficient detail to develop against.
Requirement Gathering Is Labour-intensive and Challenging but Remains the Roadmap and Measuring Stick for Software Projects
This approach allows you to maintain sight of the business benefits as well as engaging stakeholders and responding to their feedback. In combination with a clear business case, a well-defined set of requirements also simplifies design and testing, two areas where projects tend to go sideways.
Ensure that requirements for the project are clearly defined and agreed upon among stakeholders and that you have a way to track, measure, and manage changes in requirements as appropriate during the project.
3. Define how you will deliver
When it comes to delivering a major project, one size does not always fit all. All products are customizable to some degree, so what might have worked in one company may not work in another company.
That being said, why reinvent the wheel if it’s already proven successful? Sometimes it can be more beneficial to use an existing off the shelf solution. Whichever direction you take, choose the delivery mode that works best for your company.
4. Risk Identification and Management
Every project has risk and there are many factors out of your control. People leave the organization, for better or worse, leadership changes, budgets get cut, however, many risks to projects can be mitigated or even eliminated with some forethought and on-going management. For example, do you have the resources you need to deliver the project (resource risk). Are project goals clearly understood and requirements clearly defined (scope risk). Do you have a realistic project plan and timeline (time risk).
Mitigating Risk Is a Combination of Science and Art, and Always a Balancing Process
5. Test your product again and again
A technology project is something that should overall support your business. It should not be something that dictates and forces you to change your operations. If this is happening, you should shift gears and focus on tweaking the technology, rather than lowering expectations and adopting less ideal requirements.
Adequate testing is a must for any tech project. While some features may be fine with automated testing, the best approach is to have a dedicated testing team. Testing activities should mirror those with the development team throughout the project’s lifetime. With thorough testing, a project should deliver with less design flaws or missing requirements.
6. Prioritize simplicity and performance
Developers often leave the external look and feel of a product to the wayside thinking these things are not necessities for the consumer to enjoy. However, user experience is absolutely critical to the success of the project.
Developers must consider things like storage, network requirements, processing speeds and overall performance in order to satisfy the customer. If users are going to have to wait for an extended period to allow information to load, there must be a good reason for the wait, otherwise they won’t return for future products.
Simplification and Improved Efficiency Is What Adds Value
Ultimately, using the product should be a smooth and intuitive experience. Additionally, tools and alternative routes must be placed logically without being intrusive. The process can be complicated, but the finished product should emit simplicity. After all, that’s what makes companies like Apple so successful. Simplification and improved efficiency is what adds value.
A Day in the Life of a Project Manager
We all know that project managers are responsible for managing projects through to completion while remaining on time and within budget, but how exactly do they do it? What does a typical day look like for a project manager?
Here’s a sample of what a typical day might look like for a project manager.
The Early Bird Gets the Worm, Success Comes to Those Who Prepare Well and Put in Effort
8.30 am: Starting the day
After settling in for the day’s activities, it’s time to plan out the day. Start up the computer, email clients, draft team schedules, organize time sheets and create the to-do list.
To-do lists help managers and their teams stay on track. If a manager notices that one team member has yet to deliver an assignment, they can address this issue first thing in the morning; otherwise, delays can build up and affect the project. Likewise, lists help managers see the next course of action for projects.
9:15 am: Time to get moving
Efficiency is a must and there is no time to be wasted in project management. After a quick review of project plans and to-do lists, the manager must be prepared to get his team moving right away.
Round up team members, review the project’s current position and emphasize the next course of action. In order to get the team moving on assignments, strong project managers set deadlines throughout the day.
Morning team meetings are also necessary to make sure each member understands the project and their assignments. It’s also a time to answer any questions for clarity or to get feedback or concerns from individuals.
While daily group meetings can be important, they are not always necessary and can be counter-productive. If the team is on the same page and everyone is ready to tackle the tasks of the day, spend a short period re-grouping so that the team can get on and complete their assignments. There’s no need to spend hours planning and reviewing.
10 am: Meetings, meetings, meetings
More than one project manager will be more than likely in the office and they will all need to work together for the benefit of the programme. This is why meetings with other managers and higher ups are necessary in a project manager’s day.
Meetings allow each project manager to go through the status of their respective projects and to track the weekly schedule and other deadlines. It is also a time to address any business-critical tasks that might come up.
It’s worth considering that only 7% of communication is spoken. The other 93% is made up of tone (38%) and body language (55%). So although facts and figures are easily communicated via email, letter or phone, an actual discussion or negotiation is best handled where you can see the other person and therefore are able to see for yourself what their tone and body have to say on the matter.
10:30 am: Tackling the small stuff
Meetings will be on and off throughout the day for project managers, which is why it’s important to tackle the small tasks in between appointments. Small tasks include wrapping project reports, booking future meetings, answering correspondences with other colleagues, reviewing items and team reports among other things.
It’s also important to schedule post-mortem meetings with the project team to review the success of projects in order to apply any lessons learnt to future projects.
11 am: Project kick-off meeting
When one project ends, another begins, which means it’s time for yet another project kick-off meeting. Kick-off meetings can take on various forms, depending on the type of business. However, they all share the same basic needs.
Every individual involved with the new project should be in attendance and have the latest version of project specifications in written form. As project manager, it might be wise to send this to team members several days before the kick-off meeting to ensure everyone has time to review.
During a kick-off meeting, it’s important to review the overall goals for the project, both commercial and technical details, break down functional requirements, and spend time for discussion and questions. By allowing team members to communicate questions and share ideas, it opens the lines of communication and may bring up potential concerns that might have been missed in the initial planning stages.
Conclude kick-off meetings with a definition of the next steps and be sure individuals are aware of deadlines and their assignments.
11:30 am: Reviewing project specs, budgets and scheduling submissions
Other important tasks to tackle in between meetings include reviewing specifications and budgets and schedules for future projects. If a project begins that day, now would be a good time to apply the finishing touches to the project documentation before presentation and approval.
When it comes to establishing project estimates and budgets, a project manager must bring all of his experience into play in order to create a realistic budget that includes wiggle room for factors such as project complexity, team experience and skill levels, stakeholders involvement, time needed, third-party services needed, and contingency allowances among many other things.
It’s Not Easy to Squeeze in a Lunch Break, but It’s Often Necessary for the Project Managers Health and Sanity
12 pm: Lunch
In the midst of the seeming chaos that is project management, be sure to fuel up for the rest of the day’s work. Lunch is also a great span of time to check in with team members to make sure they are still on target for later-day deadlines.
2 pm: Launching the next project
After digesting lunch, it’s time to launch the next project. Get the whole team ready to go live and present the project to the client and begin testing aspects of the project in a live environment. It’s a time to spot problems and address them and review schedules and deadlines and other project needs.
3 pm: Time for everything else
The final two hours in the office are spent addressing everything else on the project manager’s plate. A project manager must be good at multi-tasking and whatever duties couldn’t be accomplished throughout the day are reserved for the final hours. Most of the time, lower priority tasks are reserved for afternoon hours. These tasks could include project update meetings with various departments, logging finances, reviewing monthly project schedules, approving time sheets, writing weekly reports, sorting purchase orders and communicating with suppliers. There are so many other small to-do list items that project managers are responsible for, but are often overlooked.
Spending Time at the End of the Day as Well as the Beginning to Review and Plan Will Only Help You Succeed as a Project Manager
5 pm: Review the day, plan for tomorrow
Before heading home, review the day’s list and what’s been accomplished. Anything that has been added or was left unfinished should be scheduled for the next day or sometime throughout the week. Reflect on your team’s work and clear the email inbox. Use a filing system that makes sense for you and be ruthless about deleting stuff. The beauty of an empty inbox is a thing to behold. It is calming, peaceful and wonderful.
Top 10 Project Management Myths Debunked
Since the dawn of time, mankind has used myths to make sense of the uncertainty that surrounds us. In the early 1990s a lot of people believed that project management was the best kept secret in business. However, because project management was not seen as a prevailing profession at that time, it suffered from a lack of awareness which was in a sense, a double edged sword. Those who were knowledgeable in the practice of project management became extreamly valuable to organisations and pioneers for the profession.
These early adopters were able to convince organisations that project management practitioners were needed. Myths around project management began to form in the business community and as the role of the project manager was unclear, questions were raised as to what project management was and what it could offer organisations.
The definition of the word myth is a “widely held, but false belief or idea.” Here, we’re going to examine 10 of the most pervasive PM myths that have emerged.
Myth #1 – Contingency pool is redundant
This is one of the most ‘mythical’ myths that has plagued the industry for a long time. Coupled with the tendency to presume that ‘real work’ is tantamount to implementation or building something concrete and you have the perfect recipe for project disaster. The thought pattern behind this approach typically originates from budget constraints and/or having unrealistic expectations. As we all know, or should know, the unexpected happens quite regularly. An effective contingency plan is important as it aims to protect that which has value (e.g., data), prevent or minimise disruption (e.g., product lifecycle), and provide post-event feedback for analysis (e.g., how did we fare? did we allocate funds correctly?).
Myth #2 – Project Management software is too expensive
If your idea of project management software involves purchasing servers, and purchasing a software application from a major vendor for a small practice with 10 practitioners then, yes, it is too expensive. If, however, you have gone cloud and elected to use a powerful web-based project management solution (such as Smartsheet), then you are likely to save thousands of pounds while reaping the benefits of a pay-as-you-go price structure. The present, and future, lie in cloud solutions that provide equal, or superior, functionality at a fraction of the cost.
Myth #3 – Project Management methodologies will slow us down
Project managers have a reputation of using process-intensive methodologies that favour ideology over pragmatism. In some instances this may, indeed, be the case when there is a mismatch between a specific project management approach and the organisation’s acutall needs (e.g., a process-driven method, such as PRINCE2, may not be appropriate for a slightly chaotic environment that favours an adaptive approach, such as Scrum). So, in sum, put down the paint roller (“Project Management isn’t for us!”) and take out your fine-bristled brush (“The Critical-Chain method may not be our cup of tea, but Agile on the other hand”¦”).
Myth #4 – Facts and figures are more important than feelings and perceptions
While facts are very important, projects are often derailed and sabotaged because of false perceptions. The PM must pay attention to both fact and fiction to navigate through turbulent organisational change.
Myth #5 – Project managers need to be detail oriented and not strategic in nature
While it is of the utmost importance for the project manager to understand how to read the details of the project, they must also understand how the project supports organisational objectives. Having a strategic perspective adds great value to the skill-set of the project manager.
Myth #6 Rely on the experts in everything that you do
It is true, we do need to rely on the experts but our trust can not be a blind faith. The job of the project managers in this area is twofold. First we must extract information and second we must verify that the information is accurate. A good example of this is asking a planner to provide an estimate on the effort required to perform a task. In some instances team members forget to include tasks which ultimately results in a faulty estimate.
Myth #7 All the battles have to be fought and won so that we can succeed
Project managers sometimes make the assumption that they need to stand firm to get the job done, however, coming to compromise on a particular issue is often a better course of action in order to win the war.
Myth #8 Project Managers can wear multiple hats
Wearing different hats can be extremely confusing. This is especially true if the project manager is asked to be a business analyst or technical expert on top of serving in their PM role. They end up doing both roles with mediocrity. When we “wear two hats” we essentially tell ourselves that both hats fit on one head at the same time. However, what happens if the demands of two roles conflict and what assurances do we have that we’re managing the inherent conflict of multiple roles and the risks the roles introduce? Sadly, multiple roles become more common as we move up the management hierarchy in an organisation, and that’s exactly where potential conflicts of interest can do the most harm.
Myth #9 Once the risk register is created, it’s full speed ahead
Risk management provides a forward-looking radar. We can use it to scan the uncertain future to reveal things that could affect us, giving us sufficient time to prepare in advance. We can develop contingency plans even for so-called uncontrollable risks, and be ready to deal with likely threats or significant opportunities. Too often, it’s not until a catastrophic event occurs and significantly impacts project progress that ongoing risk reviews are conducted.
Myth #10 Project managers can not be effective in their role unless they have specific technical expertise in the given field that the project falls within
You don’t need to be an engineer to manage a construction project or a IT technician to manage a software development project. All you need is a fundamental understanding with strong PM skills to manage the team. Experience in the field helps but does not guarantee success.
Project management is challenging enough without the myths. The profession has come a long way since the 1990s and some of these myths are fading. However, we still see remnants of them in one form or another. Great projects cut through false assumptions and confusion, allowing their teams to make smart decisions based on reality.
These are just 10 project management myths, what are yours?
The Hard Side of Change Management
Change management is an approach to transition individuals, teams, and organisations to a desired future state. For over three decades, academics, managers, and consultants, realising that transforming organisations is difficult, have avoided the subject.
My Way or the Highway
Major organisational change is profoundly difficult because the structure, culture, and routines of companies often reflect’s persistent and difficult-to-remove ways of working, which are resistant to radical change even as the environment of organisations change.
What started out as a financial buzzword in the early nineties has become fundamental business practice, with executives recognising the need to keep abreast with the competition in a rapidly developing corporate new world.
Navigating change
Globalisation and the constant innovation of technology result in a constantly evolving business environment. There is an ever-increasing need for Change Management Lead’s / Senior Managers who can help organisations successfully navigate change in today’s business environments. The focus of this movement to date has been on how to partner with organisations to define education, training and communication platforms that help to support the change initiatives and concerns of company employees. The critical aspect is a company’s ability to win the buy-in of their organisation’s employees on the change initiative.
While a project team is important for success, a senior level advisor is invaluable and can work with an organisations leadership team to avoid common pitfalls that change management projects often fall into. There are four key areas where an Advisor should act as this resource as follows:
1. Defining A Strategy
Executives should start by asking themselves what exactly needs changing and why? Organisational change directly affects all departments from entry level employees to senior management and must be aligned to a companies strategy. Too many programs are heavy on the jargon and light on the substance. Executives are often sold on an idea only to realise as the change initiative begins that they need a different outcome, tool or process to be successful.
In this situation the strategy for change needs to be re-aligned with the organisation and its goals.
An outside senior advisor with a unique perspective of the organisation will play an important role in helping an executive to explore and shape the strategy they are defining and highlight whether it will truly create the outcomes they desire. This upfront partnership can save money on the back end of a project, by avoiding costly re-scoping of initiatives.This relationship between senior advisor and executive should therefore begin as early as possible in the process.
2. Coalition Building
Its important to give people multiple opportunities to share concerns, ask questions, and offer ideas and to make following up with answers and updates a top priority. Executives must reach out across their functional work streams to build a large cohesive team to support the project once the correct strategy has been set and the urgency for the project has been established. A good senior advisor will be able to guide an executive though these interactions.
As a senior change management professional, it is important that you help leaders of the organisation craft the correct message. While leaders often know what it is they want and see the urgency for themselves, the outside view that a coach provides can support the development of a team around the initiative and help to navigate the strategic and political interests in linking the change to the interest of multiple team members.
The more people are involved in the process, the fewer will be acting as internal saboteurs.
Communication Is Key to Successful Change Management
3. Communication
Don’t confuse process visioning, planning and endless powerpoint presentations with communication.
Change is uncomfortable, and adapting to change is messy. A Gantt chart can not capture the hard side of change management. Why? Because tasks are easy to list, but behaviour and long-held habits are not easy to change. Gather outside information, solicit perspectives, and adapt the approaches for your organisation and group.
The importance of communication within an organisation around the change cannot be underestimated. Executives often fall short on communication in two main areas, not communicating the right message and not communicating it frequently enough across an organisation. It is often thought that everyone else in the organisation is on board and understands the change, however, the reality for an executive is not the reality for another worker who may have lost a job because of a well intended change initiative. A senior advisor can apply consistent pressure to the leader of the change around the need for communication and its messaging.
Quantity Is Fine, but Quality and Consistency Are Crucial
4. Share Relevant Information Quickly
Most CEOs and managers are quoted as saying, “You can’t communicate too much,” Part of the communication will be the support the urgency in messaging. “My way or the highway” is often used, but is not an effective communication strategy. Senior Advisors can work with executives to tailor their message to each area of the organisation in order to define content that is important to them.
A study by Towers Watson shows that “only two-thirds (68%) of senior managers say they are getting the message about the reasons behind major organisational decisions. Below the senior management level, the message dwindles further to (53%) of middle managers and 40% of first-line supervisors understanding reasons behind major organisational change.
The forwarding and cascading of information does not work as consistent communication around the change will be necessary at all levels of the organisation using a variety of communication pathways and vehicles. As a trusted advisor it is important to encourage executives to lead by example in both their messaging and communication of the change agenda.
Only 25% of Change Management Initiatives Are Successful over the Long Term
Maintaining The Change
Many leaders and managers underestimate the length of time required by a change cycle. It is paramount that as the change effort reaches its completion that leaders of the change recognise that the process does not end there. The role of a Senior Advisor will be to guide them to the idea that work must be undertaken to maintain the change over time. Maintaining change does not mean that an executive must own the initiative forever, just that they take the necessary steps to ensure that change has a lasting impact by integrating the change into the corporate culture and measuring the benefits and highlighting areas for future improvements.
The outside unbiased view is that a Change Management Lead is crucial to the success of a change management program.
This article provides food for thought rather than counsel specifically designed to meet the needs of your organisation or situation. Please use it mindfully.
Are Women Better Project Managers Than Men?
Why Do Projects Fail?
Hidden Sins of Using Spreadsheets to Manage Projects
Manage Your Project More Effectively Now
There are a few who get project management right from the outset, but for many it’s a minefield. In theory, project management seems easy, but it’s not as straightforward as it seems. If you’re like the majority of people, you follow what seems like a simple project management process. You start by setting your budget, you choose the right people to join the team, and hope the project gets completed without too many hitches along the way.
But, realistically speaking, project management is nothing like this – it’s hardly ever so straightforward. Mistakes are made. You might choose the wrong people to complete the project. Your team might have no idea what’s expected of them or what the project goals are, or in some cases they might even receive conflicting information, which puts the whole project in jeopardy. Sometimes the scope of the project changes, and because of everything else that’s going on, your team is unable to fulfill the requirements and meet the project deadlines.
It happens, and you’ve got to be prepared for any situation while working together towards the common goal – successfully completing the project.
Don’t throw in the towel just yet. It might seem daunting, but there are few surefire tricks of the trade which businesses and project managers can implement to better their chances of successfully completing a project on time and within budget.
1. Know the Project Details Well
Before starting, you need to create a thorough project scope that outlines every single thing. This then needs to be approved by every stakeholder involved.
Your scope needs to have as much detail as possible such as the short-term milestones, deliverable dates, and a budget outline. It makes sense really. The more detail it includes will improve your odds when it comes to completing the project successfully.
What’s more, you’ll also improve your relationship with your client throughout the whole project process from the beginning right through to the end. Of course every project will encounter a few changes along the way – this is the norm, but having a detailed plan will help you manage your client better when something is off course.
Choose your Project Team Members and Size Wisely
2. Choose your Project Team Members and Size Wisely
Naturally, if you want your project to be a winner, you need the right people for the job, which includes having the right project manager on board. Keep your team as small as possible – size does matter; so don’t let anyone else tell you otherwise.
The smaller the team, the better the communication. It also eases the stress and takes the pressure off the project manager. With a smaller team made up of the right people, the project manager will be able to organise their group without losing sight of all the details and work that’s needed doing. So, if you really want to have an effective project, limit your group’s size and only use those people and their skills that can benefit the project.
3. Highlight your Expectations from the Outset
You need to outline what you expect and what the client expects, which includes all the milestones, from the very beginning. Setting more milestones more frequently will allow you to follow the project’s progress more effectively. This way you’ll be able to jump on things quickly when they begin to go off scope, allowing you and your team to remain on target and on time.
Setting frequent milestones in a project will also allow you to review your spending and the investment thus far, which in turn will help you stay within the budget.
Milestones remove any ambiguity. They allow people to stay on target and there’s less risk of derailing the project.
Milestone setting should be a team effort. Everyone should be on board, so there won’t be any excuses later on down the line.
4. Does your Team Know what They’re Doing?
It may sound like a given, but it’s really important to be crystal clear from the beginning regarding people’s roles in the project. In other words, you need to highlight who is responsible for what, and what their deadline or deadlines are.
Things can get complicated with many people working on the same task. Sometimes things get misinterpreted or lost in translation. Avoid anyone being confused by clearly stating who should do what right from start, and make sure you enforce accountability.
You don’t need to worry about manually managing such tasks, as there are plenty of easy-to-use online task management programmes that can do this for you, so embrace technology and ease your pressure.
You may think it’s a waste of time spelling it all out, but this ensures that the full scope of the project is understood, people are clear of their role and individual and collaborative timelines. This is the key to keeping people on task and motivated.
5. Stop Micromanaging
It’s important to constantly touch base with your team members. However, there’s a fine line between supporting them and breathing down their necks. Give them space instead of micromanaging. Empower your team, trust them, and you’ll get their best work.
6. Use a Reliable System to Manage the Project
Communication is key. Most people rely on emailing, but when it comes to managing a big project with a number of different people working on it, this can hinder the project’s progress. Constantly referring back to old emails and previous correspondence is only going to waste precious time. Use software that keeps everything in one place from communication to any project information and updates. This will save you and your team a lot of time and money.
Motivate your Team
7. Motivate your Team
Everyone works better with positive reinforcement. Set milestones and reward when they’re reached. Your milestones will keep all people on track. Celebrate milestones together, but be sure to also recognise those who can’t meet them.
8. Frequent Short Meets to Stay on Track
It’s a project with many people collaborating, so holding regular meetings is a must. This is the only way to ensure that everyone and the project are on track. But you need to keep it short and sweet. Don’t meet for the sake of meeting. Have an agenda and stick to it. If you’re doing your project virtually, it’s even more important to touch base on a regular basis, so keep those communication lines open.
People do tend to go on at times when given the floor, so give everyone a set time to speak and make sure you all stick to it.
9. Allow Time for Change
No project ever runs 100% smoothly and specifications do change along the way. So to avoid the unnecessary stress and running around frantically, do some forward thinking, and set aside a certain amount of time for any changes in the scope – you’ll thank yourself for doing so in the end!
