Throughout December, we’ve looked at the scandals of the advent. The definition of the word scandal is an action or event regarded as morally or legally wrong and causing public outrage. From the King becoming to an unmarried teenager, to being born in Poverty, then the murders surrounding Jesus’ birth. What about the expensive elaborate gifts given to a humble king? Then having to be moving like a fugitive to avoid the law of the land. The greatest of all scandals must have been the insurrection at the cross. Jesus’ scandalous death on the torture instrument called the cross would cause outrage and cast a long shadow over his life and his followers.
What makes the Christian faith different from any other, is how Christ’s followers all have scandalous lives just like the Advent and the crucifixion. The Christian faith has the boldness to declare that we were lost in sin and through Christ’s death on the cross the world was reconciled to God. The Christian faith has the audacity to declare that those who are Jesus’ disciples should take up the cross…
I suppose the ultimate scandal is that suffering can be used by God for our good. Suffering is not only redemptive in the life of Jesus. It is redemptive in our own lives. Christ will use our sufferings to establish his kingdom, witness to his gospel, and work greater holiness in our personal lives. On this day as we kick off the new year, here’s a resolution worth keeping: Take up Christ’s cross of obedience, face the hardship that such a life of discipleship creates, and follow your Lord with everything you have – loving your neighbour as yourself. HAPPY NEW YEAR!
“Anyone who does not take his cross and follow me is not worthy of me.” (Matthew 10:38).
Let’s Pray Yahshua, thank you for your willingness to bear my burdens. Father, give me the strength to bear the burdens of others and take up the cross of discipleship and all that it brings for your sake. In Christ’s name, Amen.
I’m always disheartened, bewildered and even confused by the way we use the word “love,” prompting the question “what is love?” We love food, movies, clothes and sports, but we also love our family or spouse.
In the Word of God, we see God’s true definition of love. First Corinthians 13 tells us that “love is patient and kind. It does not envy nor boast. It is not proud. It is not rude. It does not seek its own way, is not easily angered, and keeps no record of wrongs. Love does not rejoice in evil, but rejoices in the truth. Love believes, hopes and endures. Love never fails.” This is how God responds to us, and this is how we should respond to the people in our lives with patience, kindness, hope, humility and love. Scripture tells us that God is love, and His character never changes!
Today, and every day, know that God loves you more than you love pizza, ice cream and cake. He loves you with an everlasting, unconditional love. He will never leave you nor forsake you. He is there for you and has a great plan for you. Receive His perfect, consistent and patient love, and let Him transform you from the inside out. His love is the greatest love and will last throughout all eternity! Hallelujah!
“And now abide faith, hope, love, these three; but the greatest of these is love.” (1 Corinthians 13:13, NKJV)
Let’s Pray
Yahweh, thank You for loving me and accepting me with all my fault and flaws. Father, thank You for doing a work in my life that no one else can do. God, please help me to love like You, with patience and consistency. Help me to see others the way You see them, and respond in love, because You are love. I bless You, honour You and love You today and always, in Christ’ Name! Amen.
Faith gives substance to the things you hope for. In other words, faith brings things into your life. Notice the verse below starts by saying, “Now faith.” It’s not “later” faith or “one day” faith. It’s faith for today, right now.
The basic definition of faith according to the Bible, is simply believing in God’s goodness, and believing that He rewards the people who seek after Him. It’s taking His Word as truth–right now. Can you believe that God wants to move in your life, now? Do you believe He can provide for your need, now? Do you believe He can heal your relationship, now? Do you believe He can heal you, now?
Today, whatever you are hoping for, open your heart and expect that God is working for you, right now. Dare to believe that God will come through for you, today. Stand strong and declare that the victory is yours, right now! Let your words put action behind your “now” faith and receive His strength and power to see victory in every area of your life!
“Now faith is the substance of things hoped for, the evidence of things not seen.” (Hebrews 11:1, KJV)
Let’s Pray
Yahweh, today I choose to believe that You are working on my behalf. Father, I trust that You have a good plan for me, and that You are leading and guiding my steps now. God, please help me stand strong in You, now, in Jesus’ name! Amen.
The Nigerian construction industry is mostly concerned with the development and provision of projects such as roads, bridges, railways, residential and commercial real estates, and the maintenance necessary for the socio-economic developments contributes immensely to the Nigerian economic growth (Bureau of Statistics, 2015). Butcher and demmers (2003) described projects as an idea which begins and ends by filling a need. However, a project fails when its idea ends without meeting the needs and expectations of its stakeholders.
Nigeria Has Become the World’s Junk – Yard of Abandoned and Failed Projects worth Billions of Naira!
Hanachor (2013), revealed that projects form part of the basis for assessing a country’s development. However, a damming report from the Abandoned Projects Audit Commission which was set up by the Ex-President Goodluck Jonathan in 2011 revealed that 11,886 federal government projects were abandoned in the past 40 years across Nigerian (Abimbola, 2012). This confirmed the assertion by Osemenan (1987) “that Nigeria has become the world’s junk –yard of abandoned and failed projects worth billions of naira”.
Abandoned projects including building and other civil engineering infrastructure development projects now litter the whole of Nigeria.
Physical projects do not only provide the means of making life more meaningful for members of the community where the projects are located, successful projects also result in empowerment and collective action towards self improvement (Hanachor, 2013).
This Issue of Abandonment Has Been Left Without Adequate Attention for Too Long, and Is Now Having a Multiplier Effect on the Construction Industry in Particular and the Nigeria’s National Economy as a Whole. (Kotngora, 1993)
PROJECT FAILURE
Project Failure might mean a different thing to different stakeholders. A project that seemed successful to one stakeholder may be a total failure to another (Toor and Ogunlana, 2008). Some stakeholders, more especially the project users and some private owners, think of failed projects as a situation where a completed building project collapsed, a situation where by a completed dam project stopped working after few days of completion, or a completed road project that broke down after few months of completion. Other experienced stakeholders, such as engineers and architects conform to the iron triangle by Atkinson (1999) which states that the most strategically important measures of project failure are “time overrun”, “cost overrun”, and “poor quality”.
Turner (1993) noted that a project fails when the project specifications are not delivered within budget and on time;the project fails to achieve its stated business purpose; the project did not meet the pre-stated objectives; the project fails to satisfy the needs of the project team and supporters; and the project fails to satisfy the need of the users and other stakeholders. Lim and Mohamed (1999) cited in Toor and Ogunlana (2009) clarified that there are two possible view points to project failure namely; the macro-level and the micro-level. They further explained that the macro view point reviews if the original objectives and concepts of the project was met. Usually the end users and the project beneficiaries are the ones looking at the project failure from the macro view point, where as the project design team, the consultants, contractors, and suppliers review projects from a micro view point focusing on time of delivery, budget, and poor quality.
In the early 1990s, the failure as well as the success of any project was determined by the project duration, monetary cost, and the performance of the project (Idrus, Sodangi, and Husin, 2011). Belout and Gauvrean (2004), also confirmed that the project management triangle based on schedule, cost, and technical performance is the most useful in determining the failure of a project. Moreover, a project is considered as an achievement of specific objectives, which involves series of activities and tasks which consume resources, are completed within specifications, and have a definite start and end time (Muns and Bjeirmi 1996, cited in Toor and Ogunlana, 2009). Reiss (1993) in his suggestion stated that a project is a human activity that achieves a clear objective against a time scale. Wright (1997) taking the view of clients, suggested that time and budget are the only two important parameters of a project which determines if a project is successful or failed. Nevertheless, many other writers such as Turner, Morris and Hough, wateridge, dewit, McCoy, Pinto and Slevin, saarinen and Ballantine all cited in Atkinson (1999), agreed that cost, time, and quality are all success as well as failure criteria of a project, and are not to be usedexclusively.
FACTORS OF PROJECT FAILURE
Cookie-Davies (2002) stated the difference between the success criteria and the failure factors. Hestated that failure factors are those which contributed towards the failure of a project while success criteria are the measures by which the failure of a project will be judged. The factors constituting the failure criteria are commonly referred to as the key performance indicators (KPIs).
Timeand Cost Overrun
The time factor of project failure cannot be discussed without mentioning cost. This is because the time spent on construction projects has a cost attached to it. Al-Khali and Al-Ghafly, (1999); Aibinu and Jagboro, (2002) confirmed that time overrun in construction projects do not only result in cost overrun and poor quality but also result in greater disputes, abandonment and protracted litigation by the project parties. Therefore, focus on reducing the Time overrun helps to reduce resource spent on heavy litigation processes in the construction industry (Phua and Rowlinson, 2003). Most times, the time overrun of a project does not allow resultant system and benefits of the project to be taking into consideration (Atkinson, 1999). Once a project exceeds the contract time, it does not matter anymore if the project was finally abandoned or completed at the same cost and quality specified on the original contract document, the project has failed. Furthermore, Assaf and Al-Hejji, (2006) noted that time overrun means loss of owner’s revenue due to unavailability of the commercial facilities on time, and contractors may also suffers from higher over heads, material and labour costs.
Poor quality/Technical Performance
The word “Performance” has a different meaning which depends on the context it is being used and it can also be referred to as quality. Performance can be generally defined as effectiveness (doing the right thing), and efficiency (doing it right) (Idrus and Sodangi, 2010). Based on this definition of performance, at the project level, it simply means that a completed project meets fulfilled the stakeholder requirements in the business case.
CAUSES OF PROJECT FAILURE
A lot of research studies have investigated the reasons for project failures, and why projects continue to be described as failing despite improved management. Odeh and Baltaineh, 2002; Arain andLaw, 2003; Abdul-Rahman et al., 2006; Sambasivan and Soon, 2007; all cited in Toor and Ogunlana, 2008, pointed out the major causes of project failures as Inadequate procurement method; poor funding and availability of resources; descripancies between design and construction; lack of project management practices; and communication lapses
The contract/procurement method
A result obtained from two construction projects which were done by the same contractor but using different procurement methods showed that rework, on the design part which occurs when the activities and materials order are different from those specified on the original contract document, makes it difficult for the project to finish on the expected time (Idrus, Sodangi, and Husin, 2011). This is as a result of non-collaboration and integration between the design team, contractor, and tier suppliers. The rework on the design portion has a huge impact on project failure leading to the time overrun. The traditional method of procurement has inadequate flexibility required to facilitate late changes to the project design once the design phase of the construction project has been concluded.
Nigerian most widely used procurement method is the traditional method of procurement (design-bid-construct) which has been confirmed to be less effective to successfully delivery of a construction project (Dim and Ezeabasili, 2015). And, the world bank country procurement assessment report (2000) cited in Anigbogu and Shwarka, (2011) reported that about 50% of projects in Nigeria are dead even before they commence because they were designed to fail.
The way the construction projects are contracted, in addition to the way the contracts are delivered, contributes to the causes of projects failure. Particularly, among the methods of project contracting is lump-sum or a fixed-price contracting method, in which the contractor agrees to deliver a construction project at a fixed price. The fixed-price contract can be low-bid or not however, once the contract cost has been agreed upon the contract award, it cannot be changed. And, contractors are expected to honor and deliver the contract agreement, failure to do so can result in a breach of contract which can result in the contractor being prosecuted.
Awarding a contract to an unqualified personnel also contributes to project failures. When a contractor places more emphasis on money and the mobilization fee after a construction project has been initiated instead of getting the right workforce and skilled professionals that will execute the project. Instead the workforce chosen will often not be base on competence and required skills rather it will be based on availability. Moreover, poor strategy and planning by contractors who have overloaded with work also contributed to one of the causes of project failure.
Poor funding/Budget Planning
A lot of public projects in the Nigerian construction industry failed as a result inadequate funding, and the difference between the national annual budget and the budget actual released. Most of the Nigerian public projects are signed even before the actual release of the national budget. The difference in budget of the contracted project and the actual budget release can get the contracted company stuck as a result of inflation of prices, scarcity of construction material at the time of the budget release and mobilization to site. Also un-planned scope of work which can be as a result of the contractor working on another contract when he is called back to mobilization to start work. Moreover, poor budget planning is a regular mistake made by some contractors by not undertaking feasibility assessments before starting the design. The construction project should be planned according to the available resources and not according to the unrealistic expectations a client has in mind.
Discrepancies Between the Design and Construction
Limited collaboration between the contractors, engineers, and the architect results in discrepancies between the project designs and construction on site, and further leads to rework. Changes on a project designs, and changing to the scope of work in the middle of construction processes on site can be dangerous, and can lead to time overrun, increase in cost, and most of all can lead to abandonment. Moreover, many cases have been seen where the designs from the architects are not buildable on site, whileIn some cases, most contractors are unable to adequately specify the scope of work for the construction processes on site. Therefore any default on the design by the architect can be an opportunity for the contractor to make more money which might cause the project duration to exceed the time specified on the contract document.
RESEARCH METHODOLOGY
This research starts with a general reasoning or theory which says that the major cases of project failure in the Nigerian construction industry are defined based on time overrun and cost overrun. The findings from the data analysis will help on the decision to accept the theory or not. The research data was collected from the progress report for the month ending of October, 2015 published by the Nigeria of Federal Ministry of works on thirty-nine on-going highway construction projects at the South-South geopolitical zone. The table 1 below shows the information on the data collected which comprises of the project title, contract Number, project description, the contractor that was awarded the projects, the date of project commencement, date of completion and the extended date if any. The scheduled time for each project was specified as follows: project commencement date labeled as “a”,project completion date labeled as “b”, and the extended date labeled as “c”.
Table 1: The analyzed data on the highway project at the South-South zone in Nigeria.
DATA ANALYSIS
The data analysis was done with the use of Microsoft excel. The analysis started by obtaining the number of days between the date of commencement of each project and the date of completion to show the duration of each highway project. And, the number of days between the project completion date and the extension date showed the time-overrun. The project duration and the extended days were obtained with the use of NETWORKDAYS function in Microsoft Excel which calculates the number of working days between two dates excluding weekends and any dates identified as holidays.
The standard deviation between the specified project duration for each highway projects and the extended days was calculated to obtain the extent to which each highway project contract failed on its time of delivery. This was denoted as the degree of failure. The table 1 above showed the projects ranking which was done based on the degree of failure of all the highway projects. The highway projects that were ranked from one to sixteen have low degree of failure and are represented with green color, while the rest are those with high degree of failure and are represented with red color.
FINDINGS
The findings made showed that the successfully completed highway projects have no extended days or time overrun, and the successful on-going highway projects are still on schedule and have no extended days unlike the on-going highway projects that have already failed as a result of the extended dates. Other projects have been abandoned because they have exceeded the delivery date as specified on the contract document, and have no extended date of completion. Thus, no work is going on.
Figure 1: Abundance of failed highway projects at south-south zone, Nigeria.
Figure 2: On-going failed highway projects
Figure 2 above showed that 14% of highway projects are still on-going projects because they have not exceeded the original date of completion as specified on the contract document. However, they are heading towards failure because they have been given an extended date of completion which can be as a result of some critical activities running behind schedule, causing delay on the critical path network of the projects. Moreover, the other 86% completely failed because they have exceeded their completion date specified on the contract document.
Figure 3: Successful on-going highway projects
The figure 3 above showed that 63% of the successful highway projects are still on-going because they have not exceed their completion dates, and they are not yet completed. However, those on-going highway projects might end up as failed projects as a result of poor funding, discrepancy between the design and the construction on site, and conflict between the construction parties or stakeholders.
“Say what you will do, and do what you said” or “Say as you will do it, and do it as you said”
CONCLUSION AND RECOMMENDATION
The idea of knowing what a failed project is, the factors and the causes is very important in project management. Success in project management can neither be achieved nor measured without the knowledge of project failure, its factors, and causes in the Nigerian construction industries. This work has shown that project failure is as a result of exceeded time of delivery, cost overrun, and poor quality. However, the analysis was only done based on exceeded time of project delivery because of the nature of the data collected.
This work suggested a few approaches to help reduce the number of failed projects in the Nigerian construction industry if properly implemented. Firstly, Having good collaboration between the project stakeholders involved in a construction project at the early stage of project conception is most important in order to accomplish the project objectives, and deliver the project on time, within budget, and quality specified on the original contract document (Othman, 2006).
Secondly, Adopting the ISO 9000 technique which is used for quality management will also help in achieving a successful project delivery. This technique states “ say what you will do, and do what you said” or “say as you will do it, and do it as you said”. This technique is not an indication of high quality but it promotes control and consistency which leads to specialization, and improved productivity and quality. Also, adopting the principles of lean construction will help to reduce waste within the construction and stream-line activities in order to improve the on-time delivery of projects.
Thirdly, Learning from the precedent failed projects, how those projects failed, and the reason for their failures. This will help the project manager to plan and mitigate the risks of project failures in the future. And, finally, more seminars and workshops will help to educate and enlighten clients (the federal government representatives), users, contractors, engineers, and architects on what is project failure, the factors that contributes to abundant failed projects, and their causes.
REFERENCE
Abimbola, A. (Novermber 24, 2012). About 12,000 Federal Projects Abandoned across Nigeria. Premium times (November 16, 2015). Retrieved from www. Premium timesng.com/news/108450-about-12000-federal-projects-abandoned-across-nigeria.html.
Al-Khali, M.I and Al-Ghafly, M.A. (1999). Important Causes of Delays in Public Utility Projects in Saudi Arabia. Construction management and Economics, 17, 647-655
Aibinu, A.A and Jagboro, G.O. (2002). The Effects of Construction Delays on Project Delivery in Nigeria Construction Industry. International journal of Project management, 20(8), 593- 599.
Anigbogu, N. and Shwarka, M. (2011). Evaluation of Impact of the Public Procurement Reform Program on Combating Corruption Practices in Public Building Project Delivery in Nigeria. EnvirontechJournal, 1(2). 43-51.
Assaf, S. and Al-Hajji, S. (2006). Causes of Delays in large Construction Projects. International Journal of Project Management, 24, 349-357.
Atkinson , R. (1999). Project management: Cost, time, and quality, two best guesses and a Phenomenon, it’s time to accept other success criteria. International Journal of project Management, 17(6), 337-342.
Belout, A and Gauvrean, C. (2004). Factors Influencing the Project Success: The impact of human resource management. International Journal of project Management, 22, Pp. 1-11.
Butcher, N. and Demmers, L. (2003). Cost Estiumating Simplified. Retrieved from www.librisdesign.org.
Cookie-Davies, T. (2002). The Real Success Factors on Projects. International Journal of Project management, 20(3), 185-190.
Dim, N.U. and Ezeabasili, A.C.C (2015). Strategic Supply Chain Framework as an Effective Approach to Procurement of Public Construction Projects in Nigeria. International Journal of Management and Susutainability, 4(7), 163-172.
Hanachor, M. E. (2012). Community Development Projects Abandonment in Nigeria: Causes and Effects. Journal of Education and Practice, 3(6), 33-36.
Idrus, A., Sodangi, M., and Husin, M., H. (2011). Prioritizing project performance criteria within client perspective. Research Journal of Applied Science, Engineering and Technology, 3(10), 1142-1151.
Idrus, A. and Sodangi, M. (2010). Framework for evaluating quality performance of contractors in Nigeria. International Journal of Civil Environment and Engineering. 10(1), 34-39.
National Bureau of Statistics (January, 2015). Nigerian Construction Sector Summary Report: 2010-2012.
Kotangora, O. O. (1993). Project abandonment, Nigerian Tribune.
Osemenan, I. (1987). Project Abandonment. New Watch Magazine, Vol. 1, pp. 15.
Phua, F.T.T and Rowlinson, S. (2003). Cultural Differences as an Explanatory Variable for Adversarial Attitude in the Construction Industry: The case of HongKong. Construction Management and Economics, 21, 777-785.
Reiss, B. (1993). Project Management Demystified. London: E and FN Spon Publishers.
Toor, S. R. and Ogunlana, S. O. (2008).Problems causing Delay in Major Construction Projects in Thailand. Construction management and Economics, 26, 395-408.
Toor, S. R. and Ogunlana, S. O. (2008). Critical COMs of Success in Large-Scale Construction Projects: Evidence from Thailand constructuction industry. International Journal of Project management, 26(4), 420-430.
Toor, S. R. and Ogunlana, S. O. (2009).Beyound the “Iron Triangle”: Stakeholder perception of key performance indicators (KPIs) for large-scale public sector development projects. International Journal of Project management, doi: 10.1016/j.ijproman.2009.05.005.
Toor, R. and Ogunlana, S. (2009). Construction Innovation: Information, process, management. 9(2), PP. 149-167.
Turner, J. R. (1993). The Handbook of project-Based Management: Improving the process for achieving strategic objective. London, McGraw-Hill.
Wright, J., N. (1997). Time and Budget: The twin imperatives of a project Sponsor. International Journal of Project Management, 15(3), 181-186.
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.
Companies that goes nuts for agile because they know they have to deliver faster and for less cost to keep up with competitors may be making a big mistake and face a collapse of their efforts.
If they focused first on a deep understanding of their business’ needs, they could more accurately decide if agile is a good fit. A better approach for you to take is analyse your current processes to determine if agile methodologies actually support your goals and needs.
2) Educated Stakeholders Make Excellent Allies
Agile works from a focal point of improving quality delivery and frequency. It does not start with reducing time to market or cutting costs. Those benefits are a result of implementing agile methods over time, after the requisite investment of time and resources has been made.
3) Don’t Do the Project Without at Least One Committed Product “Owner”
A “product owner” is a the committed business leader who will make or break the project. This person will be expected to put at least half of their time into the project. They’ll also be responsible for getting all the decisions made through the right channels in a reasonable period of time. You must have a leader like this to succeed.
4) Gain Consensus on the Definition Of “Finished”
Everybody on-board needs to agree on what constitutes being finished with any stage of implementation. For some, it will mean that by the end of each and every iteration, the production-ready software will be available. This is not always possible, so get out ahead of a potential problem and gain consensus.
5) Build an Exceptional Cross-Functional Team
Cross-functionality is what separates the ineffective agile teams from the high-performance ones. Team members have to be proficient in performing any and all necessary tasks so that they’ll be able to always deliver what the customers need.
Team building requires that you identify the right parties and that you shape them into a functional team by making sure that they share your own true goal of always delivering massive value to product owners.
6) Make the Proper Investment in the Tools That Support Agile
The beginning stages of any agile project will involve you investing in the of the robust frameworks, infrastructure, and process automation tools that fully support agility. This includes a wide range of solutions like continuous build servers, automation testing, video conferencing, interactive chat, and software frameworks. Don’t scrimp on other important details like the solution architecture, either.
7) Retrospectives Need to Be a Main Priority
Inspection and adapting are the keys to agile. Organisations using this methodology use a vehicle called “retrospectives” to ensure these tasks are being performed correctly. A proper retrospective should embrace the qualities of self-improvement and transparency. Any actions that are a result of the retrospective must be given the highest priority. This is especially true of estimations, which are crucial to achieving the kind of team velocity that keeps projects on track.
8) Start the Project with a Solution Architecture
Even though documentation is not always the most glamorous part of any project, you’ll be well served to make sure you understand that documentation is still important to a successful project. Using a solution architecture pays off because it serves a blueprint for the final project that will be delivered by the team. Team members need this document so they understand what will happen if they make changes. Members who are added to the project at later days will use the documentation as a reference point so they can be brought up to speed.
9) Embrace the Fact That Change Is Coming and Plan for It
You can’t make a change without a cost in agile. Change is something you always have to embrace philosophically, but be aware of the costs and the impacts to the project. When you are doing the estimation process, factor in potential changes when applicable.
10) You and Your External Partners Should Have an Agile Relationship
Agile is not always the best fit for traditional vendors. They prefer contracts that use fixed prices and fixed outcomes. When you switch to agile you’ll need to make a point out of understanding the ramifications the changes will have with your vendors. You and they may have to make some changes to keep the relationship running smooth.
Try to build a transparent relationship with all of your external vendors. Risk Reward contracts that employ clearly defined KPIs work amazingly well for agile organisations.
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?
A well crafted quote, very much like good storytelling and can elucidate fuzzy concepts. For example, creativity” and “innovation” are not the first two words that come to mind when talking about procurement. However, According to Deloitte’s paper Charting the Course, this is where procurement’s destiny lies.
By transforming beyond today’s definition of “procurement as the sourcing of raw materials, and goods and services,” procurement can reach new heights.
Here are 10 quotes to help you find motivation and inspiration to make a positive change.
All models are wrong but some of them are useful – George Box (Statistician)
People will forget what you said, people will forget what you did. But people will never forget how you made them feel – Maya Angelou (Writer)
We cannot solve our problems with the same thinking we used when we created them – Albert Einstein
Opportunity arises for the prepared mind – Louis Pasteur (chemist and microbiologist)
A journey of a thousand miles begins with a single step – Lao Tzu (Philosopher)
What gets measured, gets managed – Peter Drucker
Leonardo da Vinci’s Simplicity is the ultimate sophistication – Dale Dauten
Worrying does not empty tomorrow of its troubles, it empties today of its strength – Corrie ten Boom
The best way to predict the future is to invent it – Alan Kay
Strive not to be a success, but rather to be of value – Albert Einstein
What are some of your favorite inspirational quotes? Share in the comments
Big Project Failures Claim Their Victims in Spectacular Fashion
You’ve just been assigned a high visibility failing project and you’re working round-the-clock to get the work to the client on time, despite the fact that the job bears barely any resemblance to the project you initially discussed. The scope keeps creeping, the risk and issue alerts are coming in thick and fast, the project is already two months past the original deadline, the clients are getting antsy even though they’re yet to provide you with various key pieces of information in order to baseline the project. Is this your chance to shine and showcase your skills?
If You Don’t Know Where You’re Going, You Will Probably End up Somewhere Else – Laurence J. Peter
If you manage to turn the project around and the project is successful, you will attract many fathers. However, if the project fails, you will probibly be offered up as the sacrificial lamb (scapegoat), there is absolutely no way around it. A high percentage of projects fail to deliver useful results, that’s a fact.
Project managers are regularly blamed for schedule delays and cost overruns for projects they inherit by no fault of there own, however, in most cases, the fault for such issues rarely lies with just one person.
Sufficient data has been gathered to indicate that blockers such as unsupportive management, senior sponsorship or low resource availability are as much to blame for project failure as ineffective stakeholder management or poor communication.
Capture all decisions
The only way to protect yourself is to ensure that you capture all decisions made in the project. In most cases many of these decisions will have been made by people above you. While you can influence decisions made by people under you. Get into the habit of building a dashboard early in the project and updating it each week with actuals. Also consider using a standard repeatable technique to analyse the health of your project.
Constrained resources
If you are in a project where resources are constrained, clearly outline the resources that you require to deliver the project in terms of time, scope, budget, risk and quality. If resources are pulled from your project, clearly articulate the affect of that in delivery terms and measure that to time delayed or cost added.
Risk and issues register
Operate a strong risk and issue register, ensure it is both visible and assessable so your team can actively participate in updating it.
Stop the project
Always remember, cancelling the project is not always a failure. There can be many reasons why the project may no longer be desirable now. If you have done your job well, you can be really successful by ensuring a project does not continue to meander along, wasting time and money when there is no possibility of completing the project.
Organisational change management
Unfortunately, the same can’t be said when there are organisation change management issues. While there are a few project managers who feel their jurisdiction ends at the triple constraint, most now understand the need to achieve the expected benefits from their projects.
So when is it fair to blame a project manager for poor implementation of a project’s deliverables, this is assuming that they were employed at the beginning of the project?
If they didn’t perform good stakeholder analysis during the project initiation stage as well as at regular intervals.
If they turned a blind eye and deaf ear to factors that could impact value achievement
If they didn’t insist on a clear communication strategy and progressive information sharing with relevant stakeholder groups.
If they didn’t engage influencers from key stakeholder groups throughout the project lifecycle.
If the organisation management deliverables were not built into the project’s scope definition and work breakdown structure.
Assuming the project manager was appointed at the start of the project and had undertaken all of the above, what are invalid reasons to blame the project manager if the project failed?
A lack of timely resource availability or commitment by the organisation
Directives to the project manager to not engage certain stakeholder communities
Ignorance by senior sponsors to management risks raised by the project team
A management decision that is too bitter a pill to swallow in spite of how much it has been sugar coated
Have any comments or stories that could help to expand this article?
