Do you have what it takes to be a project manager?

The field of project management has intrigued me for the past three years – ever since I participated in a project to implement a new accounting system at work. While I was only an individual contributor on the project representing finance, I had an opportunity to observe the project leader in action. After the project concluded, I walked away impressed by his discipline and decision making ability under stressful situations. I have since wondered if I can succeed as a project manager.

After taking this class and interviewing a project manager, I am starting to wonder if project management is suited for me. After reading the article “Do you have what it takes to be a project manager” by Moira Alexander on CIO.com, I may be convinced that project management is not for me.  Moira has identified 8 facets of the job to decide if it is the right career choice for you. Do you think you have what it takes? Do you think you can handle the things listed below?

Project management is fast-paced:  Project management is often fast-paced and filled with deadlines and shifting priorities. You are constantly challenged with new obstacles. If you thrive in fast paced environment, then you have passed the first gate in your decision to be a project manager.

Project management comes with an abundance of uncertainty:  As we saw in class with the resource and cost assignment exercise, things can change from week to week. Uncertainty is a big part of projects. Being able to deal with uncertainty under duress is a big part of being a good project manager. Do you think you can handle not knowing what’s lurking in the background waiting to jump in and ruin your plans?

Project management involves constant pressure and stress:  One of the constants in project management is persistent pressure and stress. You are constantly juggling multiple things. Are you someone who can stand the heat?

Project management means dealing with continual change:  Due dates, deliverables, costs and resource availability can change without any notice. As a good project manager, you are expected to adapt to change and handle certain level of chaos in your life. Do you think you can handle continual change? If you are someone who likes structure and routine in your life, this may not be the field for you.

Project management means multiple deadlines:  Prioritizing and managing multiple deadlines are essential part of successful project management. Project deadlines are constantly evaluated and maybe altered. This can require you to balance human and financial resources, and can also impact the quality of the product or services being delivered.

Project management means dealing with internal and external conflict:  Dealing with difficult people is one of the most dreaded aspects of project management. However, this is an essential skill for good project managers. Being able to influence people require skills and tact. Are you able to work with people and be prepared to set aside your ego and opinion?

Project manager have demanding schedules:  If you are looking for a 9-5 job, project management is not for you. As stated in the article, “project managers often “eat, sleep and breathe” project management from the initiation through to the close-out”. Burnout is a serious issue for project teams and especially project managers.

Project management requires exceptional organization skills:  Exceptional organizational skills are a must-have for successful project managers. Being able to handle all the things mentioned above requires great organizational skills.

Now that you have an idea of what the job entails, are you up for the challenge? Do you have what it takes to be a project manager?

http://www.cio.com/article/2896325/project-manager/do-you-have-what-it-takes-to-be-a-project-manager.html

 

 

From Complexity to Ingenuity

I have learned from the project management course that risk management is the essence of project management, by understanding, analyzing, mitigating, and monitoring project risk the company would reduce the number of surprises and that will leads to project success and increase stakeholder satisfaction. According to PMI’s report Pulse of the Profession in 2013 “Every $1 billion spent on a project, will have $135 million at risk, the trend becomes more troubling for projects with added complexity, which, on average, have budgets nearly twice as large.”

Project manager must identify complexity in a project from the beginning to help control the risk through the life of the project, to make sure his or her team is focused and the project is better governed and managed. Also, he or she would decide if the project is worth the risk and what should be done to manage the risk through the life of the project. According to PMI’s report in February 2014 “From Complexity to Dexterity” the report added seven tips to taming complexity in a project as follows;risk_measurement_400_clr_5483

1. Project and program management culture comes from above.
Having engaged project sponsors is one of the main drivers for project success.

2. Set a clear vision for project outcomes.
Setting specific goals for what the project needs to define how decisions are made, and prevent scope creep from pulling the project of track.

3. Break highly complex projects into manageable pieces.
Determining the elements of complexity early when problems are cheaper to solve.

4. Establish centralized functions for oversight.
Setting guidelines and providing tools between project teams and leadership to ensure they remain aligned.

5. Create a formal governance process and follow it.
Diligently oversight projects by people empowered to make decisions to mitigate issues before they become a major problem.

6. Invest in people.
Developing the expertise of project leaders ensures the organization has a broad pool of leaders ready to manage highly complex projects.

7. Communicate effectively with all stakeholders.
Seeking out different perspectives and ensuring project objectives are widely understood.

The report indicated that the pharmaceutical business is a prime example for complexity when dealing with uncertainty about the future of creating new drug to market. “We are trying to predict what’s going to happen 10 years from now with respect to multi million euro rug development projects.Research wants to develop a new drug, commercial wants something to sell, and customers and stakeholders want a product proven safe and effective.” says Ken Jones, President and CEO of Astellas Pharma Europe Ltd. As organizations have little choice to deal with indexcomplexity, but such project management strictness helps Mr. Jones’ team better control the risks and determine which projects should be fast-tracked, slowed down or killed.

Which one of the tips do you find most important to taming complexity in a project and can you think of any additional tips to add to this list?

URL: http://www.pmi.org/~/media/PDF/Business-Solutions/Complexity_Dexterity_whitepaper_v2.ashx

 

Is your Labrador smarter than your PM?

An article called My Dog is Smarter Than Your Project Manager by Brad Egeland caught my eye when I was skimming new project management articles to read. I immediately thought, how rude! Aside from the outlandish comment about his Labrador being smarter than some project managers (I am certain that could not be true) I get author’s point and he had some good words of wisdom for project managers as well. Brad listed three best practices for project mangers to follow:

  1. Stay on top of the project schedule – Conduct weekly meetings to get the status update on your team and revise the project schedule daily.
  2. Manage the scope well – The scope serves as a basis for keeping everything else on track well like the project timeline, budget, and keeping the project as profitable as possible.
  3. Communicate – That means listening well, too…don’t forget that. Conduct meetings, follow-up afterwards with notes, keep project team informed at all times, and do the same for senior management.

Brad also brought up some things that I could relate to. Those moments where your project manager does not seem to be listening or grasping what the group is saying. Additionally, when they suggest things that are completely out of left field like they don’t get what’s going on at all. I can certainly relate to that at work right now. Our project manager in my department does keep up on the schedule, even when I’m not sure if we should be because of how our last meeting ended. It’s probably best he stays on schedule though or else we wouldn’t accomplish anything. He has been lacking at managing the scope because he has not been able to redirect our meetings back to the scope whenever they get off track. For example, we are converting our paper employee files to electronic, so we’re implementing a new software called m-files to replace our outdated/inefficient paper file system. Several times our compensation and benefits manager, who we all respect greatly on this project, has come into the meetings that should just be about the employee file and he has taken it so far out of scope into a whole philosophical debate about our shared drive in the office that I don’t think our project manager knows how to rein him in.

Communication is something that our project manager could improve on too. We receive too many emails from him all around 5-5:30 PM, very last minute, the night before a big meeting at 9 am the next day. So I’ll end up reading it on my phone upset that he didn’t email me that a few hours earlier! We are using SharePoint as a way of editing files, and he could clean up the entire thing a large amount so that we weren’t spending half our time trying to find the current version of whatever document were working on either.

Regardless of all my minor complaints about my project manager’s work style, I do not think that a dog is smarter than him! I am impressed with his skills, how far he’s gotten us, and his enthusiasm about the project. His positivity is the only thing that keeps me engaged in this project.

Have you been in a project where you thought so little about your project manager that you think they could be replaced by a dog? Or have you known anyone who was so upset with their project manager that they would think the same as Brad?

Estimating project time and cost

Project cost and timelines are usually the hottest topics when a project is initially rolled out. Let me start by stating I am no Project Manager nor pretend to be, but I have lead and assisted numerous projects throughout my career. One of the burning questions my managers have seem to always ask is “when will I have this completed and how much is it going to cost?” From my experience he was always more concerned with getting the project completed on time than cost. Not to say that cost was not important, as long as the expenditures were in reason. In manufacturing as in any other industry the customer comes first and is the main focus of everyone in the company. As we know estimating cost can be either from the bottom up or the top down. In my opinion bottom up approach is preferred because it is usually the project manager or project engineer that will be see the project through. I know in my field of manufacturing you don’t have top level managers on the production floor. They are knowledgeable but operations is a completely different world than engineering, sales, or marketing.

As I mentioned earlier completion time and meeting deadlines is what top managers are looking at when projects are in process. I used a critical path analysis chart to help with my estimation for completing a project. The project consisted of relocating a family of speakers that logistically makes since to assemble on the west coast. Considering most of the raw components we buy for this speaker are from the west cost and the finished assembly is primarily sold to customers in that region. We decided to relocate this product family to the Anaheim plant. So this project from a operations stand point consisted of transferring all the purchased and manufactured components from Illinois to California and setting up a work cell.  So the critical path chart made a lot of since for this project because so many part numbers needed to be transferred, equipment needed to be purchased, testing equipment needed to be fabricated, along with standard work and training documents.

So when I had my completion date estimated and total cost of all invoices for this project. I presented it to my manager and his manager. Unfortunately the project was not completed until two months after my estimation, for reasons that were out of my control. from an operations stand point everything was ready to go. My manager understood that and knew I had completed all my task. All Project managers struggle with the same dilemmas and that is estimating how much a project will cost and how long will it take to complete the deliverables. I wanted to see what project managers in the field had to say on this topic so I visited the PMI website. Click on the link below to see what they had to say. Also feel free to leave a comment on your experiences with estimating.

http://www.pmi.org/Learning/knowledge-shelf/project-estimating.aspx

 

 

Blogging while Jogging

Kenneth White

MGT 598

Dr. Cook

 

http://www.liquidplanner.com/blog/tips-for-managing-rogue-projects/

 

While my experience with actual project management is limited, my knowledge of what it takes to be a project manager has increased significantly. With the lessons and material discussed in class, it has enabled myself to more clearly define what project management is and how to engage in the many obstacles that come with it. Speaking of obstacles, I’ve found an interesting article discussing tips or managing a rogue project.

There are a lot of different issues that could go wrong with a project. To make things worse, a project within a project can always pop up. You’re still driving to accomplish a goal within a constraint. While these rogue projects come up you’re dealing with shorter times constraints. Usually these mini projects may range from one day to a month, but it depends on the business.

Typically a specific project may have numerous ramifications. They may affect multiple groups, whether customers directly, or the shareholders. Rogue projects on the other hand, or a project within a project, usually focus on a single goal. Because the goal of this particular “rogue project” is smaller in can be easier to get the project off the ground. The limitations of time require you as the project manager to act more quickly and thus get the project going instantly. Rogue projects can also be less resource intensive. While there can be exceptions to this, Rogue projects tend to rely on more on specialized talent and resources versus the whole larger project. There is lesser supply of financing, as well as labor or materials. This is because the rogue project usually only addresses a temporally specific function, rather than the “big picture” initiative.

Collaboration is key to successfully tackle these projects. In addition, prioritizing risk assessments follows. The limited timeframe of a rogue project truncates a large chunk of procedures associated with traditional PM. Risk assessment can be a very long process, while its still crucial to anticipate the weaknesses and possible vulnerabilities in the planning phase.  A good project manager should be able to determine which risk directly may have an impact on the rogue project. Being able to asses the risks that directly relate to the projects values are the ones you should spend time on.

Ultimately, no matter how big or small your project may be, as a project manager, you still need to have a plan. Now I’m not talking about the creation of a committee. A short timeframe doesn’t negate the importance of planning. according to PMI, approximately 44% of projects experience scope creep. The importance of a work breakdown is crucial. A work breakdown structure can be helpful in order to divide the project into smaller portions so that it will have more accurate cost and time estimates.

Tips for Project Management Success

In our project management course we have discussed the use of a Work Breakdown Structure and a Responsibility Matrix in order to assist us in effectively managing a project. We also need to keep in mind that there are other tools that one acquires outside of a classroom. The author in the article below shares several secrets to project management success. I have listed a few of them with my thoughts.

1. Have full project details before starting.
Understand the scope of the project, and make sure all the stakeholders agree. The project details should contain dates, budget information, and milestones. I have worked on projects that didn’t contain the budget information, and then I was told that we have spent more than we were supposed to.

2. Have the right size project management team in place.
Once you know what the project details are, determine the skills and experience that is necessary, and then select the people you will need. I feel that if you only need 4 people for example, than only select the 4 people you need. Selecting more people then needed will add more work because the project manager now needs to manage a larger group.

3. Be clear about who is responsible for what.
Determine who in the team is responsible for which part of the project, and make sure they are accountable. This step is critical because the project manager and the team need to know what everyone is working on, and what everyone will deliver on the due date.

4. Don’t micromanage.
It’s okay to meet regularly with your team members, but allow them space to work. I have seen this too many times; where a manager doesn’t give his/her employee the space needed to work. What this causes is resentment, and your team may challenge your leadership.

5. Keep team members motivated by rewarding them when milestones are reached.
It is a good idea to motivate and recognize members of your team with some kind of reward. I have worked on projects where the manager has awarded their teams with a lunch or outing during certain milestones.

6. Hold regular project status meetings or calls, but keep them short.
Meetings or conference calls should be scheduled regularly so everyone is up to date on the project’s status. In my experience, meetings need to be long enough to discuss the status, and any open issues that need to be addressed. They don’t need to be too long.

7. Build in time for changes.
Allow time for last minute changes that may need to be made to your project if the specifications change or requests are made. Based on my experience as an engineer, almost all projects always need that extra time to address last minute requirements.

The author states several good tips that I agree with.  Are there any additional tips that you can share that may help one be successful at managing projects?

http://www.cio.com/article/2599794/project-management/9-secrets-to-project-management-success.html

 

Use the Heart to Keep the Buzz Going

On a bright September afternoon, six strangers glanced about the classroom, made eye contact with five proximal classmates, and serendipitously assembled into a high functioning team.  IMG_1412

All members were engaged and participated in all of our planned meetings.  Our brainstorming sessions were fun and productive, yielding a series of ideas that we prioritized unselfishly and weaved into a plan.  We selected and vetted a reputable charity with a just and noble cause.  Through the creativity of our team, we soon had a logo exempt from DePaul brand restrictions, an attractive T-shirt design, a cleverly assembled cookie mix for sale, and a series of fun events that were sure to attract many participants and donors.  We were excited by our progress – there was no way we could fail in our mission.  We launched our team Facebook page and Making Strides ACS team site, sent out an appeal through email and waited for our buzz to go viral….

Family, work, and school responsibilities have placed me into an extended social media coma.  I’ve rarely checked my Facebook profile, and almost never posted anything for the past four years.  Now, due to this class assignment and our social media communication strategy, I began obsessively checking my site for updates and applying as many “likes” to our posts as possible to promote them to my network.  Did anyone out there in Facebook land “like” my posts or the ones on my team site?  Was our message getting through?  Should we consider paying money for Facebook to “boost” our post?  Do we need to invest more money in advertising to raise more money?

Perhaps it’s not the quantity of communications, but rather their quality that matters most.  A recent blog post from the site npEngage compiled some good, if not obvious, tips that will likely seem familiar to many readers.  Periodically updating team members and our social network about our progress towards our financial goals, describing how funding enables the programs of the American Cancer Society, and personally thanking our individual donors are critical communications that we can’t forget to send out.  Are there any communications that your group has sent out that have been particularly effective in generating responses to your campaign?

During our team’s October 4, 2015 yoga event, I found the instructor’s connection of our project to the yoga session moving.  Mariel Victoria introduced the class to a difficult (for me) pose, “the wheel,” that was selected in the spirit of opening the heart to charity and kindness.  After 75 minutes of physically demanding yoga, Mariel encouraged the class to bring forward any other projects or concerns to share with the group.  Prior to the start of the session, I was prepared to speak to the class with enthusiasm about our events and items for sale.  Afterwards, I knew that my delivery would not have been nearly as effective as Mariel’s for that audience.  Many of the attendees stopped by our area and took information, bought cookie mix, or just donated.  For me, this reemphasized the importance of quality in the communication, and I intend to up my game for the remainder of the “Blue Demons for a Cure” campaign.  How will you adjust your message to optimize your project’s appeal?

A Risk Management Lesson from “Silicon Valley”

The video clip linked below is from HBO’s “Silicon Valley”. This television program follows a group of software engineers as they launch an innovative app and their associated start-up company (both named Pied Piper). This clip focuses on Pied Piper’s primary competition, a tech conglomerate named “Hooli”. The clip shows a speech by Hooli’s CEO, followed by several discussions between members of a project team.

HBO’s Silicon Valley on Risk Management

This scenario highlights several instances of risk management failure which are tragically relevant to the workplace. Some of the failures I observed are lack of communication within the project team, lack of escalation within the project team and larger organization, and absence of risk planning and mitigation planning early in the project. In today’s hyper-competitive, fast-paced marketplace proper risk management is critical to project success. Has anyone observed this type of situation at their workplace?

Recently I encountered a scenario where the customer made a significant design change late in the project. The product was nearly qualified, but was deemed unacceptable due to reliability and performance requirements. The team was faced with a tough decision: kill the project or redesign.

As the contract manufacturer in this arrangement, I raised concerns regarding the potential risks this design change could have on the project. Any delay or high defect rate would result in lost revenue and profit to my organization as well as the customer. I was reassured there would be no issues and no change to the product ramp/launch dates and product cost.

As we built increasing numbers of the product the failures began to pile up. Both customer and manufacturer turned to firefighting mode and additional resources were dedicated to expedite resolution. In my customer’s organization I could see finger-pointing among several teams as each department tried to cover themselves and avoid being the next bearer of bad news to upper management.

Eventually the product was fixed and had a successful (yet slightly delayed) launch after several weeks of many stressful meetings. Could this situation have been prevented? I believe so, but only if the correct tools, controls, and planning were put in place at the beginning of the project at both the customer and manufacturer. The following article details such risk management best-practices:

Risk management and project management go hand in hand

Some noteworthy items include ingraining a risk management culture/mindset in the project team, frequently analyzing the project status and forecasting new risks, developing and agreeing to risk response plans in advance, and assigning an owner to each risk who can drive corrective actions and track progress. Although you cannot predict every possible risk in a project, I’ve seen how important it is to conduct this planning at the beginning of the project to avoid firefighting late in the project.

Does your company have a formalized process for risk management? Are these successful, or would you suggest alternate approaches? Do you have any horror stories similar to mine? Please share your experiences!

 

Daily Steps for The World Water Crisis

Have you ever looked at a potential problem and thought “There is no chance on earth that i can solve this. There is too much to do and not enough time.”  In my three years with my company Darley, there have been a few moments where i felt overwhelmed about the amount of work i needed to do.  However over time I realized that big challenges in my job are a ‘set of daily tasks’ that need to be done.

In my job at Darley, I have worked as Business Development Manager to develop two new divisions of the company; Darley Water Purification Systems and Darley Custom Pump Solutions.  Both divisions started within the past five years and we are attempting to do one of the hardest things in business : Sell New Products to New Customers.

Due to the undefined role of Business Development for these emerging divisions, I began to learn as much as possible about the different market segments.  In particular, the WATER MARKET.  Currently there is no market more attractive in the world than technologies surrounding water treatment, storage, distribution, monitoring, etc.. With all the potential for growth in in the industry, I still found myself thinking: Where do i start?  Who can i sell products to?  Where are the customers?  The questions don’t stop.

In my three years, trying to direct the company towards the water market has not been an easy task.  Darley is a committed fire company with a many tendencies of an old school company.  Darley likes to innovate, but at the speed of Darley.

As i sat at my desk in the early days, many times i would get stuck because i didn’t know what to do.  This wasn’t because there was a shortage of work, but because there were so many things that needed to happen in order for Darley to grow in these water sectors.  Where do I start when trying to do something to solve the world’s water crisis?

This is when the light bulbs started going off.

If I do a better job of personally managing my time in the office, that is one step closer to help more people in the world get access to clean water.  If I can better plan out my tasks out in the morning, I can complete tangible action items that need to get done.  With my tasks better defined on a daily basis, I can better utilize the internal resources I have at Darley to get more things done.  If i get more tasks done a daily basis on a personal and group level, we are moving one day closer to helping more people with access to clean water.

I now look at my job as a daily adventure.  Of course I need to plan for future trade shows and what are we doing in 3-6-9 months.  However all we can do is best manage our time on a daily basis to be as productive as possible.  I want to change the world.  I want to help people get access to clean water.  I know this will not happen overnight, but my actions needs to improve and get more efficient every day.   Now before I go to bed I always ask myself “Did I do anything today that moved me closer to my goal of helping people around the world?”  If i answer “no”, I think about what went wrong, acknowledge the inefficiencies, and move on to the next day.  

Water, water everywhere…but not a drop to drink.

If you have time, watch VICE.  VICE is the best documentary series in television right now.  Season three has a special about the water crisis in India. For me to truly get behind a solution, I need to experience the problem first hand.  I spend one week in India and watched this documentary.  Here is a sneak peak: https://www.youtube.com/watch?v=GcLFXixHyW0

Risk, Risk, Risk, Can you avoid it? Can you plan it?

I came across an article that talks about managing risk on our projects.  Brad Egeland, who is the author of the article implies that the risk can be mitigated by dedicating a chunk of the project money to the risk.  He also points out that, there are times where we create a risk management plan but don’t follow through with it due to time or budget constraints.  I totally agree with Egeland that well documented risk management process is always going to be a great strategy to follow.  What happens when you don’t have enough money to asses or plan for risk?  Do projects without any budget assigned to risk fail?

In class we have learned that, to manage risk we must proactively attempt to recognize and manage internal events and external threats that could potentially affect the project.  One of the most asked questions on the project is “What could go wrong?”.  Many times we are uncertain of the consequences of our actions until they are completed.  There are times where we can sit down and really ponder about the situation that could potentially put the project at risk.  Usually ideas that put a project at risk are put on the side and quickly forgotten.  Risk management teaches us to be more proactive than reactive.  I think everyone can agree that being proactive could potentially eliminate most of the risks from the project unless we experience unforeseen risks.  At that moment we better have some kind of a contingency plan that will reduce the negative impact of a risk event.  Contingency plan will usually require some kind of a budget.  Depending on the project, the risk assessments could identify additional budget requirements or reserves as some might call them.

Many times I jump into a project without thoroughly assessing the situation for risk.  Risk is not something that we think about everyday.  Most of us usually react to the situation and are not proactively estimating the potential risk.  Once the problem arises, I personally document what went wrong.  I start from the beginning and trace all my steps to find out how,why and where did this go south.  Once I have determined the root cause of the problem I am more inclined not to make the same mistake twice.  The reason many of us jump into the project without looking at the risks is because risk planning takes long time and sometimes is unavoidable.  Some might argue that risk planning should depend on the size of the project.  I would strongly recommend that even a small project should have some kind of a risk assessment.  At the end of the day don’t we all want to be perfect?

If you would like to read more about managing risk on our projects please feel free to read Brads article.  The article could be found at http://blog.aecsoftware.com/2015/04/are-we-really-managing-risk-on-our-projects/