Search

Showing posts with label Project. Show all posts
Showing posts with label Project. Show all posts

Sunday, November 28, 2010

WHY DO PROJECTS FAIL?

WHY DO PROJECTS FAIL?
                “What we learn from lessons learned is that we don’t learn from lessons learned.” This old saying when comes to projects is not far from the truth. In fact, two times or more numbers of projects are failures, and they fail the same few ways over and over again.
                For a person like me who haven’t yet experienced making big projects (those to be considered complex), the word “failure” of a project is something objectionable and appalling. However, in reality, statistics proved that it is common for projects to fail, but it is not common to know the ultimate cause of the failure. No one sets out to fail, but for some reason people just accept that a lot of projects won’t deliver on time, under budget with the expected scope intact. But talking about what causes failure makes people uncomfortable, because nobody wants to give or take that kind of criticism.
                Many believe that the main reason why projects fail is due to methodology used. Some says because of the Project Managers and others because of the unexpected vast changes. During my class on Project Management, our facilitator said that the reason why projects fail because the people behind the project fail to plan. Do you agree? I do not, and so is he. What he truly meant was that people behind the project plan to fail. He used as an example our admission at the university. He pointed out the reasons why we are in the university studying. Since a lot of my classmates (us for I’m one) were not be going to commencement exercise on time (that means failing the project *see my post about what is a project), was a proof that from the start we actually plan to fail, for if we didn’t, we should be doing our assignments and submitting our school projects prior to or on deadline and attending to class on time.
WHAT IS PROJECT FAILURE?
               
                I’ve read many articles about the reasons why projects fail, but only few define what project failure is. Regular Geek  said, defining what a project failure is determining who’s to blame. A few simple guides are whether a project finished by a planned deadline, whether the project finished within a planned budget or whether the number of production defects. Once the definition is set, then the blaming will be so determinable? If the project is late, then the project manager should be blamed. If the project is over budget, then the customer is to blame because they requested too many features. If the number of defects is too high, then the developers are to be blamed. Nice and simple, right? Wrong. There are two problems with this simple blaming pattern. First, there are likely several things that went wrong during a project. So blaming one thing is never the answer. The second problem is the stigma of failure within software engineering. What if your definition of failure, a late project, is met but your customers love the new system? Is that really a failure? Even if the project meets the three simple definitions of failure, late delivery, over budget and poor quality, blaming someone does not help. Projects and companies fail all of the time. If people stopped at their first major failure, half of the entrepreneurs currently working in Silicon Valley would not be working.
On the PMBOK Fourth Edition, there are now 6 variables being checked—scope, schedule, budget, risk, resources and quality. This may be better than the original 3 variables, or also known as the triple constraints (scope, time, money), however it is likely an effort to keep away from failure than to succeed. Can we really define project failure as a set of measurements?
Defining Failure
The list of failed projects is long than the list of successful projects, however defining failure is not easy s it may seem. Upon reading a number of articles regarding this matter, I wondered why even though we already know why projects fail; we know how to prevent their failure –why do they still fail?”They said when project has not delivered what was required in line with expectations, it is considered a failure, therefore, in order to succeed, a project must deliver to the 6 variables mentioned above to define threshold
Here are. So, let’s look at each one:
Scope – For any given project, scope can be used to determine whether a project is complete. However, feature completeness should not be the criteria for success. Functional completeness, which is whether the users can complete their work using the system, is a better measurement and it is also harder to define. Functional completeness is not known until many users go through their typical work flow in the system several times.
Schedule – If a project goes past its deadline, many companies consider that a failure. I do not believe you can measure the schedule miss without looking at other aspects of the project. Also, you need to look at the reason for the deadline. If the deadline is only the time when all of the work was estimated to complete, then it was not really a deadline. If there was a time to market concern or the users have some other schedule constraints and need the system by a particular date, then the schedule does become very important. Missing an estimated end date and missing a constrained scheduled deadline are two very different things.
Budget – Money is an issue for most companies and is one of the few measures that can be a big indicator or cause of failure. The budget for a project is typically a function of the number of resources over the life of the schedule, unless there are capital expenditures like new hardware. For smaller companies, the budget can be of extreme importance because funding is limited, especially when compared to large corporations. In the most extreme cases, the budget can be the reason a project gets shut down, obviously meaning that the project is a failure.
Risk – At this point, I ask that all project managers skip to the next bullet. Risk and the implications of that risk is something that can be managed but should not be evaluated in terms of the success or failure of a project. There are very few cases where risk should matter, and those are projects where the defining feature is to reduce risk in the business itself. Risk is a good measurement to determine the possibility of failure or other bad situations, so from the management perspective it is a good window into the health of a project.
Resources – Staffing of a project is typically not used as a measurement of failure, but it can be a very good indicator of impending doom. For example, if a project was estimated to require 5 software engineers for 6 months, and after 2 months another 5 engineers are added, that is a significant indicator that something is wrong. It may mean that a large amount of scope was added to the project, or that the project or its complexity was severely underestimated. Additional resources will also affect the budget; probably add more risk due to communication difficulties and likely impact the quality of the software delivered.
Quality – As I mentioned before, quality should be a huge determining factor in the success of a project, but it should not be the defining factor. A high defect rate is always a bad thing, and will have long lasting effects on the application. Thankfully, agile processes like test driven development, and basic automated unit testing have helped developers ensure some level of code quality. The only problem with quality is that you can never rid a system of all defects, you can only be rid of known defects. It can also become fairly expensive to ensure the highest levels of quality.
At this point, you are probably asking where the definition of failure is. Technically speaking, failure is very specific to your environment. I have limitedly defined success and you could say that failure is not matching or exceeding the success criteria. The most important thing is defining success and failure in the context of your business. If you know what these definitions are, then you can actually determine whether your project was successful and how you can drive towards success in your projects.
(Reference: http://regulargeek.com/2010/11/08/defining-project-failure/)
COMMON REASONS WHY PROJECTS FAIL
From the discussion on our Project Management class, our facilitator presented us these 10 reasons why projects fail.
-poor estimates
Poor estimate refers to the bad associations of plans. Bad estimates lead to bad cost projections which ultimately equate to poor delivery. The problem being when estimates are needed for efforts to be completed to project costs. Often a project is estimated for resource effort before it is budgeted. Therein lays the problem. The estimator is rarely the individual doing the work and the amount of work may not be fully understood. This is one of the reasons why the estimator must be well knowledgeable and skilled. Estimations involves time (influenced by the scope of the project) and planning. In estimations, one must understand the project outcome. Since it is only estimations, one would not think that it will be perfect; however, accuracy plays an important role.
-scope changes
Defining scope is perhaps the most important part of the upfront process of defining a project. In fact, if you don't know for sure what you’re delivering and what the boundaries of the project are, you have no chance for success. Managing scope is one of the most critical aspects of managing a project. However, if you have not done a good job of defining scope, managing scope will be almost impossible.

The purpose of defining scope is to clearly describe and gain agreement on the logical boundaries of your project. Scope statements are used to define what is within the boundaries of the project and what is outside those boundaries. The more aspects of scope you can identify, the better off your project will be.
Defining and planning a project is only the first step in successfully managing a project. After you plan the work, you have to work the plan. You must make sure that the work you agreed to deliver is completed within the timeframe and budget allocated. Part of the work-the-plan process is preparing for the inevitable fact that, once the project starts, the client will probably end up asking for more (or different) work than what was originally agreed to. This is when you must use scope-change management. If you don’t, you will end up trying to complete more work than what was originally agreed to and budgeted for. In other words, you will be heading down the road to trouble.
-work breakdown failures
Projects don't just happen they are planned. The whole project team should develop the plan not just the project manager. This ensures that the teams' experiences are taken into account and that everyone is fully committed and has ownership of the plan.
Running a project without a plan is foolish. Working without knowing where you are going is likely to lead to problems and possible failure. Running a project without a plan is like trying to find your way in a strange city without a map. As the saying has it, "If you fail to plan, you are planning to fail."
In order to identify the individual tasks in a project it is useful to create a Work Breakdown Structure. The WBS is the foundation for the detailed project plan. Get the team together and brainstorm all of the tasks and sub-tasks in the project, in no particular order. Write them down on sticky notes and put them on a whiteboard. Once everyone has thought of as many tasks as they can, arrange the sticky notes into groups under the major areas of activity. Add, modify, remove and shuffle the sticky notes until the WBS is accurate, complete and logical. The purpose of a WBS is to decompose the project into steps and sub-steps.
www.projectsmart.co.uk/planning-a-project-using-a-work-breakdown-structure-and-logic-network.html
-not enough time/ resource allocated
Sometimes managers are not given the opportunity to plan because time pressure from senior management take over and most of the time the project is on it’s way before it has been clearly defined (New Zealand Management, 2003). In such cases, people see planning as a waste of time because they believe that time is better spent doing something rather than planning (Fichter, 2003).
 -incompetent project manager
According to the experienced failures, one of the major major reason of projects failure is due to the incompetence of the project manager. Project mangers have a lot of responsibility to handle just to make their projects successful. One of the responsibilities of project mangers is about communication. Since Project managers get busy, many times they don't make time to manage project communications properly. Also, the project manager may think they are doing a good job communicating, but that may not be the case. Project managers must remember that the project team is made up of individuals. Each person on the team has a preference for the types of communication they like to receive, and each person processes communications differently. Poor Communication leads to poor project team, and this matter considered to be a fault of the project manager. There are a lot of incompetent project managers that are hurting our profession because they either refuse to alter their communication styles or are too arrogant to change.
-ineffective use of PM discipline and processes
Every step of business succession progresses according to project plans. So project management becomes very important part of succession because a small mistake may result in wrapping up the business plans forever.
During one project management study, the working methodologies adopted by project management professionals employed with management consulting firms were analyzed. The conclusion drawn was that most of these project management professionals employed at these management consulting firms used the project management techniques which were perfected with the trial and error methods and deep understanding of the business rules.
Project management is all about calculating the pitfalls and creating outlets to avoid the consequences. All the projects share a common aim – following ideas and activities to shape them into working realities. Even if the project is well planned and carried still the possibility of encountering dangers exists.
Project management progresses by following methodologies
§ Plans
§ Organizing
§ Staffing – employing right people who can do justice to the job
§ Guiding – Guiding people to do follow things
§ Monitoring – Monitoring the flow of project at each step
§ Innovation – Introducing new ideas to add uniqueness to project
§ Completion – Setting deadlines for the completion of project
Any project which lacks to identify its objective can be compared to going on a fishing trip in a dry river. An objective goal will always give direction and lead to the project. The objectives should always be concrete, not something vague as improving customer satisfaction or improving the popularity etc. Such objectives are immeasurable whereas you can set objectives like easing out the process by introducing some value addition etc. Often project management teams proceed to work towards achieving some selected objectives because setting many objectives may hamper the quality of work.
(http://www.selfgrowth.com/articles/Importance_Of_Project_management.html)
 -lack of proper management support
The project manager is the interface between the business and technology sides of the company (The Standish Group, 1999). Without executive support project managers in the organization find difficulty in aligning business with their projects. The executive management also needs to be straightforward if they have reservations about the project. Otherwise, once problems are encountered in the project their support will weaken (Glaser, 2004).
Most projects will change the work life of many users and require that they participate in design and implementation. Without user involvement nobody in the organization feels committed to the project. User involvement requires time and effort, but the staff might be already stretched and unable to find time for a new project on their schedule. That is why executive management support is important to make priority clear to the staff.
-wrong use of technology
Information technology should be an asset to a business and support the business through a clear definition of the role technology will play in the business. This is defined in the business plan.
Implementing a full technology strategy can have benefits that cascade throughout the organization.  Wrong use of technology would somehow lead to the failure of the project.
Conclusions
The past failure need not discourage project managers from future efforts. Past examples of IT project failures gives us the opportunity to point to the relevant lessons that can be derived from recognizing areas where IT projects is more likely to fail.
Project managers can position themselves to reduce the possibility for project failure by considering the following recommendations:
  • Make sure to plan before starting the development or implementation.
  • Pay attention to tasks in the critical path.
  • Set up the necessary processes to calculate and inform the risk.
  • Ensure that the IT project has clear objectives.
  • Understand project trade-offs when making decisions regarding objectives change.
  • Use the duration instead of the time on task to estimate schedule.
  • Avoid using linear approximation when estimating time or resources.
  • Get the support from the executive management and ask them to be open if they have any reservations about the project.
  • Ensure and communicate regular about the progress, even if it seems invisible.
  • Require that users participate in design and implementation of your project
  • Make sure you have the appropriate planning, communication, and technology skills.
(http://www.projectperfect.com.au/info_it_projects_fail.php)
Other causes of failure could be added ad nauseam, but the existence of additional factors is not the point. The factors of successful project management have been documented for years—they merely need greater attention. But if this article has helped serve as a reality check for your project, it will have served its purpose. If you violate any of the principles noted by the consultants and practitioners in this article, you should not expect to succeed in spite of yourself.

Monday, November 22, 2010

What is project management?

What is project management?

         In the twenty-first century it has become fashionable to manage one's own investments. People nowadays are very much serious on deploying their projects in order to ensure the success of it. Indeed, our environment today is very complex that it requires ongoing implementations. By the use of project management skills, we can be able to manage chaos by providing framework for working amidst persistent change. Or in better understanding, by use of it we can create an environment conducive to getting critical projects done! So what is project management then?
Project management as described by the book, is an application of knowledge, skills, tools, and techniques to project activities to meet project requirements. Project management is accomplished though application and integration of the project management processes of initiating, planning, executing, monitoring, controlling, and closing. Project management is then about organization, about changing people’s behaviors, about managing, or about decision making. And the person responsible for accomplishing the project’s objectives is called a project manager.

           We all know already that there is no magic formula to guarantee the success of a project. But there are techniques and strategies that will help plan and manage projects. These things are in the scope of project management. Project management therefore provides methods and tools to ensure that objectives are successfully achieved. Thus, without proper project management, a project would certainly fail.

           There 3 constraints I learned on managing a project. First is to find its scope. Finding the scope means developing a common understanding as to what is included in, or excluded from, a project. What is it you are supposed to accomplish by managing this project? What is the project objective? Is it a real time system? Is it all screen-based? What reports can be produced? Where does the information come from? What manipulation is required for the data? Is all the data compatible? Do you want to generate standard letters? How many letters? How customizable are the letters? Do you want to store the questions? Do you want to store the answers? Etc. etc. etc. Scope is not about determining the time and cost. We are not talking about deciding how long it will take, or how much it will cost. Time and cost are outputs of scope or comes after the scope is defined. So it is of paramount importance to define the scope to determine the outcomes. Poor scopes leads to failure, so we must see to it that the scope we included or excluded are accurate.

The other two are time and cost. In project management time management describes how to monitor and control time spent within a project. It is all about recording the time spent by people on a project. The time process helps the manager know which tasks has been worked on, when and for how long. It also get varies depending on the present circumstances. Time factor is not in total control despite more sources and alternatives are available to achieve the task. If you have limited resources you can’t control over the time. It is one time of limitation once you are behind the time schedule.

               In the case of the cost, we can't know the exactly until the project is complete because we can't accurately predict the future. Cost of the project depends on the different factors like change in the rate of materials, equipments & machinery, change in rate of labors and other various factors. However, we can do an estimate. Doing an estimate would create a good understanding of how projects should unfold through the project life span.
Before ending this piece, I conclude that it is therefore important to understand project management for us to be aware on decision making. Through this we can manage any risk that would eventually comes our way while achieving our project’s objectives.

What is management?

What is management?

               If we are going to ask by this question, as first thought, we would probably shout “it is what managers do!” I would possibly do that, but I will not shout huh? Lol. Seriously, the definitions of this term over the internet all have similar concepts. My friend Wikipedia says “it is an act of getting people together to accomplish desired goals and objectives efficiently and effectively” and that it “comprises planning, organizing, staffing, leading or directing, and controlling an organization (a group of one or more people or entities) or effort for the purpose of accomplishing a goal” and my other friend in Suite101 says “Management is an organizational function, like sales, marketing or finance. It doesn't necessarily mean managing people. We can manage ourselves or the material assigned to us at work. If you managed a project very well on your own, it would mean that you did the job in a well-organized, efficient manner, making good use of all resources at your disposal” Ohh.. They just have the same idea I have in mind, they just raised their hands first! Lol. But I guess I have to share my ideas too…Well, to sum up all my understanding, management, I guess, is like raising your kid. You need to have a plan for his future first. You need to guide, direct, instruct, control, or advice him so that he will not be into the path he should not walk. Through that you will be rest assured that you will have the best results after all the things you’ve done. If you are a parent, you understand that it is pretty hard to do. Management therefore not is just a simple task. It requires great responsibility in order to perform it well. It requires time, skills, and resources if necessary. What would be the world if there are no managers like? Do you agree we need managers to plan for us? What about leadership?
          On the class, I learned that management is different from leadership. I thought before there is no difference. But with the help of our facilitator I recognized that leadership and management are two different functions or simply they provide two dissimilar purposes. A manager executes while a leader directs. Implementing existing directions and maintains efficient operations are the main role of managers. Making new directions to influence others through innovation are the things leaders do. Managers focused only on performance, they only make sure that the project would be efficient that’s why they are seen as task-oriented, controlling and insensitive to peoples needs. On the other hand, leaders induce us to change. They don’t control us. They are just to direct us for the better. We don’t necessarily follow them. We can have a choice. These are the reasons why leaders described as inspiring, visionary and emotionally engaging. But for clarifications, managers also provide direction but only on HOW to execute efficiently. Managers are more on occupying a position, while leaders are more about doing something different. However I’m with no against with management. In fact I do not agree with our facilitators thought of changing our course description from Project management to project leadership. But I do not also agree if leadership will be out of bounce. Both management and leadership skills are needed at the organizational, team, and personal levels. It's not a case of either/or, but and/also. Futurist, Joel Barker provides another helpful distinction between the two roles; "managers manage within paradigms, leaders lead between paradigms". Both are needed. Trying to run an organization with only leadership or management is like trying to cut a page with half a pair of scissors. Leadership and management are a matched set; are both needed to be effective.
         I also learned from the discussion the PODC thingy in management to make a group of individual more effective and to achieve their objectives efficiently. ‘P’ stands for Planning. Planning has a broad definition but for simplifications, it means setting up. Planning refers to the process of deciding what to do and how to do it. It involves preparing a sequence of action steps to achieve some specific goal. To reduce to bare bones, think a plan as a map. When following a plan, you can always see how much you have progressed towards your project goal and how far you are from your destination. Without a proper business plan the business has no direction. One can do the business without plan, but the results are not what one wants. It is rightly said “Well plan is half done”. A carelessly planned project will take three times longer to complete than expected .A carefully planned project will take only twice as long.

          ‘O’ stands for Organizing. This is the second function of management. This happens after a plan is already in place. It transforms plans into reality by deploying people effectively through assigning and coordinating tasks, and makes use of the resources orderly and wisely. There is also called an organizational structure. It is framework intended for decision making. The organizational structure is defined as set of formal tasks assigned to individuals and departments, formal reporting relationships, including lines of authority, decision responsibility, number of hierarchical levels, and span of managerial control, and design of systems to ensure effective coordination of employees across departments.

        ‘D’ stands for directing. It is a process in which managers guide and instruct to achieve their goals. They said it is actually the heart of the whole management process. Without it, planning and other functions are with no importance. This function involves influencing human behavior. This might be through motivation, leadership, discipline, development, etc. In this function, managers are transforming into good leaders’. They are bound to accomplish the organizations’ objectives while concurrently helping each team members grow.

          The last function is controlling or control. This function involves instructing team members in order to achieve the organization’s goals or simply making sure other people do what should be done. For managers, the key to maintain management control is to establish performance standards for employees because it will give them an idea of what is expected of them and tells them how you assess their performance. Controlling also is a function in the management cycle closely related to planning. After plans are made, controlling function ensures that the plans made are carried out, or, if circumstances necessitate, that the plans are modified.

          I remembered during my high school days I was asked what I eventually wanted to be. Without hesitation, I answered “to be a manager”. I never thought that time that managing is not easy as it may seem. The position it will create needs great responsibility. You must be well skilled before entering this area. Some might think that managers do not have any personal production, that they don’t do anything aside from instructing. The true fact is, every manager has something to do that no one else can or should do.

What is a project?

What is a project?




            I know you too encountered this term even before and you would perhaps agree that we usually used this term when we are referring to our afterschool activities right? On my case, I used this term frequently when I’m referring to my big school works. I mean those that require a long span of time, those tasks I considered as with high difficulty or usually conducted before the semester ends. And if you are not a student anymore, this term might usually mean something that you are working to in relevance with your career. But, is the definition of this term limited only to what we are thinking?

           I was a bit surprise with the definition I learned in the first day of our class in Project Management which is still facilitated by Mr. Randy Gamboa. According to him, everything we do is actually called a project. I was puzzled that time. I mean, is it really everything? I could agree with him if he says it’s called work or something alike, but he still insisted. He then asks us what we usually do in our house. One of my classmates said, “I do wash plates”, and then sir said “Well, that’s a project.” “How you enter this university is called a project too”, he added. I began to realize that projects perhaps are about matters that needed to be under a course of action or process before completion. But my realization that time was still narrow (although not wrong) until he cited an additional case. He asked, “Why you are here studying? What’s your purpose?”Some answered “to learn”, and some naughty people answered “to have an allowance”. Then sir said, “You are here because you wanted to graduate!” Well, we could not agree more with him. Then he said with conviction, “That’s your project!” “By entering in the college you are actually starting your project, and graduating means finishing it” he added. Then he continued on lecturing. He defined the term project with the help of the PMBOK or Project Management Book of Knowledge, as a temporary endeavor undertaken to create a unique product, service or result. From this definition we can say that projects are in fact temporary only . Temporary because it has a definite beginning and end not necessarily mean short in duration. Remember the example our facilitator stated that I mentioned earlier? The graduation thingy? Yes, like what he said, entering the college means starting the project, and graduating means ending it. Therefore, the definition from the book and the example are actually in match. Studying is a project that had a definite beginning and a definite end. However, according to the book, an end of a project is reach when the project’s objectives have been achieved or it becomes clear that the project’s objectives will not or cannot be met, or the need for the project no longer exist. So now, can we still call studying as a project? Certainly! Before we enter college, our minds are already set for the diploma, right? So if you can notice, right from the start we already have a vision or an objective, which is to graduate, and not just to graduate, but to graduate on time! If we cannot reach that objective, that simply means we cannot graduate so the project fails and ends. Or if it became clear to us that the project’s objective will not or cannot be met either due to the difficultness of the course we took or to the terror teachers who keep their prying eyes on us, that still means we cannot graduate, so the project still fail and have its end. Or maybe because of the worst case scenario where in the need for the project no longer exist (example is when we realized that we are into teaching and not in the computing field).And the best thing, if we be able to graduate (on time), or we achieved our objective, that means the project is successful and have its wonderful ending.

         You know, honestly, what I wrote above was the “temporary” nature of a project. It was just one of its six natures. So we still have 5 more to tackle. Let’s start with the next.
          According also to the book, a project is a “job done once”. Well, I’m not pretty sure if that was from the book or from the mouth of our facilitator, but anyways, as what the second nature implies, a project is actually a task done only once. (Waah! I’m just repeating it. lol) So if you already graduated from that course, what the hell you wanna take it again? Taking PhD and Masteral doesn’t mean taking it again huh? When you do the masteral and PhD means you want too be more knowledgeable to that field. And hey! You are starting new project again with new objective! Wow! You’re impressing me! lol.

           Next nature, according to our facilitator (or from the book, I guess), a project is “designed to solve a problem”. We do projects for specific purpose. If we want to prove that students fail because of the teachers, we could have a research project about it. It can be used to determine whether or not it’s true. It will surely create a great impact in the society especially on educational areas. Referring to the definition of the project I mentioned earlier, a project creates unique product, service or result. These 3 are what call project deliverables. Let’s go technical while explaining this 3. According to the book, a project can create a product or articraft that is produced, is quantifiable, and can be either an end item in itself or a component item. In case of the services, it has the capability to perform a business functions supporting production or distribution. And a project also can create as a result, such as outcomes or documents. Therefore, a project actually has the property called uniqueness. Uniqueness in the light of my understanding means something a project possess in order to solve a problem. A project has to provide a specific response to a need (problem) in a specific context. They are innovative in short. It is something important in project deliverables. Since a project is unique, it means it is plan to work out on a specific problem also. Take for example, assuming that a bridge in your place was broken and needed to be fix, do the project need to fix also other broken bridges near your place? I guess not. Every project has its scope, time and budget. It has its limitation then. I will just discuss this further on my next post soon.

        A project also “consists of interrelated tasks”. When making project, we need to gather data or information first to solve for a particular problem. If the information we gathered are not interrelated, there’s no sense in continuing the project ‘cause it will surely fail. And since projects are the product of collective endeavour. They are run by teams, involve various partners and cater for the needs of others.

          The last nature was phrased as “all projects are work, but not all work is a project.” According to the book, work is operational or ongoing while project is temporary and unique. Still a bit puzzling? Well, what I think is that all projects are called work because they just not simply end, they could have impacts or aftereffects that could sustain a business or something. However, not all work is a project might be because a project is just temporary or it is designed to attain specific objectives then terminate if achieved. A work as we know creates new objectives once the other objectives were achieved then continue all along. And works also activities which can be repeated or transplanted anywhere at any moment; I think that’s the difference.
           This time, I do know exactly what a project means, that everything is a project. Everything we do has objectives…that might be simple or hard to accomplish. And like all the projects, the endings are not predictable especially when we are not skilled at project management. There are times a project will fail because we did not attain the objectives or the need of it no longer exists. Just like life.