Tag: Schedules

Posted on

A Day in the Life of a Project Manager

Managing Daily Routines: A Day in the Life of a IT 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.

Posted on

65% of Mega-projects Fail

There’s a reason why  Mega-projects are simply called “Mega-projects.” Extremely large in scale with significant impacts on communities, environment and budgets, mega-projects attract a lot of public attention and often cost more than 1 billion. Because of its grandiose, a successful mega-project requires a lot of planning, responsibility and work. Likewise, the magnificence of such projects also creates a large margin for failure.

Mega-projects Come with Big Expectations. But a Project’s Success Is Often in the Eye of the Beholder

Despite their socio-economic significance mega-projects – delivering airports, railways, power plants, Olympic parks and other long-lived assets – have a reputation for failure. It is thought that  over optimism, over complexity, poor execution, and weakness in organizational design and capabilities are  the most common root causes of megaproject failure.

Blinded by enthusiasm for the project, individuals and organizations involved with mega-projects often miscalculate the complexity of the project. When a mega-project is pitched, its common for costs and timelines to be underestimated while the benefits of the project are overestimated. According Danish economist Bent Flyvbjerg, its not unusual for project managers who are competing for funding to massage the data until it is deemed affordable. After all, revealing the real costs up front would make a project unappealing, he said. As a result, these projects are destined  for failure.

For example, building new railways spanning multiple countries could prove to be disastrous if plans are overly complex and over-optimized. Such a large-scale project involves national and local governments, various environmental and health standards, a wide range of skills and wages, private contractors, suppliers and consumers; therefore, one issue could put an end to the project. Such was the case when two countries spent nearly a decade working out diplomatic considerations while building a hydroelectric dam.

Complications and complexities of mega-projects must be considered thoroughly before launch. One way to review the ins and outs of a project is through reference-class forecasting. This process forces decision makers to look at past cases that might reflect similar outcomes to their proposed mega-project.

Poor execution is also a cause for failure in mega-projects. Due to the overoptimism and overcomplexity of a project, it’s easy for project managers and decision makers to cut corners trying to maintain cost assumptions and protect profit margins. Project execution is then overwhelmed by problems such as incomplete design, unclear scope, and mathematical errors in risk assessment and scheduling.

Researchers at McKinsey studied 48 struggling mega-projects and found that in 73 percent of the cases, poor execution was responsible for cost and time overruns. The other 27 percent ran into issues with politics such as new governments and laws.

Low productivity is another aspect of poor execution. Even though trends show that manufacturing has nearly doubled its productivity in the last 20 years, construction productivity remains flat and in some instances has even declined. However, wages continue to increase with inflation, leading to higher costs for the same results.

According to McKinsey studies, efficiency in delivering infrastructure can reduce total costs by 15 percent. Efficiency gains in areas like approval, engineering, procurement and construction can lead to as much as 25 percent of savings on new projects without compromising quality outcomes. This proves that planning before execution is worth its weight in gold.

We Tend to Exaggerate the Importance of Contracting Approach to Project Success or Failure

Finally, weaknesses in organizational design and capabilities results in failed megaprojects. For example, organizational setups can have multiple layers and in some cases the project director falls four or five levels below the top leadership. This can lead to problems as the top tier of the organizational chain (for example, subcontractors, contractors and construction managers) tend to focus on more work and more money while the lower levels of the chain (for example, owner’s representative and project sponsors) are focused on delivery schedules and budgets.

Likewise, a lack of capabilities proves to be an issue. Because of the large-scaled, complex nature of mega-projects, there is a steep learning curve involved and the skills needed are scarce. All the problems of megaprojects are compounded by the speed at which projects are started. When starting from scratch, mega-projects may create organizations of thousands of people within 12 months. This scale of work is comparable to the significant operational and managerial challenge a new start-up might face.

In the end, it seems that if organizations take the time to thoroughly prepare and plan for their mega-projects, problems like overcomplexity and overoptimism, poor execution, and weaknesses in organizational design and capabilities could be avoided. After all, mega=projects are too large and too expensive to rush into.

 

Posted on

The Good, the Bad and the Ugly of Project Management for Christian Leaders

It’s Monday afternoon at the office. The week has only begun, but you’re already swimming in a sea of memos, spreadsheets, and schedules. Just as you’re daydreaming about what leftovers you might reheat for a late dinner, your boss pokes his head into your office. He or she mutters something about quotas and deadlines before he or she drops the bomb about a “little project” he or she needs you to complete by the end of the week. And just like that, you know you’ve been handed a nightmare but for whatever reason accept the challenge.

“According to the Cranfield School of Management in the Uk, 68% of Projects Are Destined for Failure Before They Even Start.”

The lack of project management training or experience of many Christian leaders can be an enormous stress factor for them. Whilst natural organizational ability is enormously helpful, in itself it is no guarantee of any project being both successful and low stress.

What is a  nightmare project? It’s something we’re all familiar with. The boss assigns us some vague task and a deadline but leaves the means to a solution up to our creative intellect.

So how do you solve  the problem of this dreaded “project”?

1.             Understand the scope of the project  

First things first, create a list to layout your ideas on how to go about the job at hand. Write out questions you might have that need to be answered, people you might need to work with or talk to in order to understand what work must be done.

Without fully understanding what work must be done, it is impossible to accurately estimate a project’s schedule or budget.

After creating a list, share your ideas with colleagues. Work with peers who have the same goal and share the same work ethics as you. Too often, when faced with an unrealistic project, we tend to work with just about anybody who wearily agrees to have their name on board. The enthusiasm of a new project quickly fades when actual work is needed. Instead of “How can I help?” were met with “I’m busy right now” and “Can it wait until next week?”  The sponsor, project manager, and project team must share a common understanding of the scope of the project.

2.             Get estimates from the people who will be doing the work

To avoid the stress of friendly fatigue, create a solid plan of action with your co-workers. Assign duties and responsibilities and set a deadline for each task.

4.             Re-estimate as soon as you realize an estimating assumption was wrong

Don’t get discouraged if people and other things fall through. Even though it’s frustrating with the broken promises, missed deadlines, mistakes, and poor quality outputs. As soon as you realize a mistake was made, assess the impact and re-estimate the project.

“Unfortunately When Project Managers Spend the Majority of Their Time Trying to Achieve the Unachievable, the Result Is Frustration and Potential Burnout.”

But say you’ve followed those steps and were able to remain positive throughout this grueling week. You completed the assignment, whether enthusiastically or completely drained of all energy, only to be told the higher-ups decided to go a different route and don’t need the results of your project after all. “Good effort, though,” your boss tells you as he or she hands back your laminated report.

If you find yourself in this situation, just remember to never say “yes” to a “little project without first taking a look at what you’ve been handed.

 

As seen on