Analysis of British Petroleum's management of the 2010 Gulf of Essay

Analysis of British Petroleum's management of the 2010 Gulf of Mexico's oil spill - Essay Example There was also a huge fouling of beaches in Florida, Louisiana, Mississippi and Alabama which meant that the leisure activities of many people had to be put to a halt not to mention the many beach hotels that suffered huge losses due to lack of customers (Eilperin, & Mufson, 2010; Tangley, 2010). The spill resulted into hundreds of law suits that were filed. A special investigative panel consisting of officials from the coast guard office as well as the department of Interior was constituted by President Obama to look into the issues that surround the oil spill. BP began an assessment of the resource damage as soon as they managed to control the spillage. The losses incurred by the company are huge since at least 185,000,000 gallons (which comes to around 4.4 million barrels) of oil was lost. The clean up process might have succeeded to remove the spilt oil but the ramifications on the environment are probably going to last for decades to come (Jervis, & Levin, 2010; Jervis, 2010) Th ere are many questions concerning the resource damage that might not be fully answered any time soon. The extensive media coverage during the duration of the spill raised important questions that unfortunately did not have very comprehensive answers. For instance: the delay in response to the emergency, the companies that are to blame and most importantly and if the environment could survive such a disaster. Who is to blame? Before the OPA 90 was passed, it was not very clear who amongst the federal state, private players and the other local officials was directly responsible in the event of an oil spill of the magnitude of the BP Mexican gulf spill. The current legislation now demands that federal government should step in immediately when such a disaster strikes. The responsibility on the government according to the OPA 90 covers spills on the land as well as coastal spills. Offshore incidents like the recent BP Gulf of Mexico spill lie well in these boundaries. In the same breath e; the OPA 90 also includes the coast guard as a party that should be in charge of evacuations and control of the spillage. The biggest challenge of this is that the coast guard may not have access to the kind of equipment and personnel that it requires to handle such spills. However, legislation gives the coast guard the authority to acquire the equipment from private companies. BP was consistently present during the control of the spill and though it was largely in charge of the process, it was also assisted by personnel and equipment that the coast guard had acquired. There was some tension between the government and BP originally. This tension was addressed by the reports made by the president’s commission. Ideally, the responsible party is both the partner and the adversary since they are in charge of containing the spill and they are also required to take responsibility for all damages. It is a relationship that often confuses the general public but it is something that was established in the OPA 90 (Schwartz, 2010). Oil spill management is usually based on the National Contingency plan. The National Contingency plan identifies the national, regional as well as the local infrastructures. It integrates the different agencies that might be involved in the event of a spill. The National Contingency plan usually comes up with an initial disaster response team both nationally and regionally. It coordinates the efforts by setting up an on-site coordinator as well as a centralised command

IRAC Brief Essay Example | Topics and Well Written Essays - 500 words

IRAC Brief - Essay Example As the employer of the victims, was Mariano Prime LLC dba MD Wholesale cognizant of the harassment that took place and was it required to put an end to this type of behavior? Rule: Harassment can include undesirable sexual advances, solicitation for sexual favors as well as verbal or physical harassment that are sexually attuned. A client, employee or a customer of either male or female gender can experience sexual harassment. Analysis: The EEOC, upon conducting its investigation, filed a lawsuit with the U.S. District Court for Guam District in September 2011 (EEOC v. Mariano Prime LLC dba MD Wholesale, Case No. 11-00029). This came after futile attempt to settle the case through conciliation process. During the EEOC’s investigation, it established reasonable evidence suggesting that MD Wholesale facility breached Title VII of the Civil Rights Act of 1964 ("Marianas Variety",  2013). The case has also made apparent that there was no training whatsoever on sexual harassment, sexual assault, or reporting procedures. We can further assume that from management throughout subordinate levels, were totally oblivious of the consequences due to violations of a persons civil rights. Conclusion: MD Wholesale made a settlement with EEOC in the amount of $77,500 for the victims and accepted to change its policy and procedures for dealing with grievance on workplace sexual harassment. In addition, MD Wholesale is also required to retain an EEOC as a way of ensuring that their staffs are educated about their rights in light of workplace discrimination, harassment as well as retribution. Further, the company is expected to implement training program for its management to ensure compliance with future complaints. MD Wholesale agreed to offer extra training for its management and human resources personnel in order to ensure that they are capable of dealing effectively with future EEO grievances. Apart from monetary compensation to

Sale of Goods Act 1979 Essay Example | Topics and Well Written Essays - 3000 words

Sale of Goods Act 1979 - Essay Example Section 13(1A) of This Act provides as regards England and Wales, the term implied by subsection (1) above is a condition. Under Section 13 of the Act there is an implied condition in a contract of sale, upon the supplier of a service in a contract that the goods will correspond with the description, which will apply to any sale where the purchaser does not see the goods before he buys them & when acting in the course of a business that he will carry out the service with reasonable contractual period. Even if the purchaser has seen the goods, there may be a sale by description if he has relied upon the description. In this question it need to discuss While 'description' itself is an ordinary English word, the Sale of Goods Act 1979 contains no definition of what it means when it speaks (in Section 13) of a contract for the sale of goods being a sale 'by description'. And then it needs to discuss that a contract is from between parties when the seller was agreeing to sell and the buyer agreeing to buy. Now it need to discuss about condition, sale 'by description', current possession, and misrepresentation. First, one has to decide what is the meaning of sale by description. In the case of Varley v Whipp1 it has been held that this phrase must apply to all cases where the purchaser has not seen the goods but is relying on the description alone. Therefore, a sale must be by description if it is of future, or unascertained goods. But in addition, the term applies in many cases even where the buyer has seen the goods. Not only the term "sale by description" includes goods of a generic kind, for example, a packet of brand X cigarettes but also specific goods when they are sold as a thing corresponding to description. In the case of Beale v Taylor2 the subject matter of the contract was described as a 1961 Triumph Herald Convertible and the plaintiff saw the car and bought it. In fact, it turned out to be two different cars joined together. It was held that the car did not comply with the description. In Grant v Australian Knitting Mills [1936] the sale of woolen underwear was held to be a sale by description even though the buyer was buying something displayed before him on the counter. But a sale is not a "sale by description" where the buyer makes it clear that he is buying a particular thing because of its unique qualities, and that no other will do, or where there is absolutely no reliance by the buyer on the description (Harlingdon Ltd v Christopher Hull Fine Art Ltd3). In other words it appears that the only case of a sale not being by description occurs where the buyer makes it clear that he is buying a particular thing because of its unique qualities and that no other will do. For this reason, the sale of manufactured item will nearly always be a sale by description (except where it is second hand) because articles made to an identical design are not generally bought as unique goods but as goods corresponding to that design. In the Harlingdon case, the buyer was a professional art dealer who knew the seller had no experience or knowledge of the type of painting being said. There was accordingly no breach of s. 13 when the painting turned out to be a forgery. The buyer had placed no reliance on the seller's description. These cases suggest that the real question at issue in deciding whether the sale should be classified as a

Analysis of British Petroleum's management of the 2010 Gulf of Essay

Analysis of British Petroleum's management of the 2010 Gulf of Mexico's oil spill - Essay Example There was also a huge fouling of beaches in Florida, Louisiana, Mississippi and Alabama which meant that the leisure activities of many people had to be put to a halt not to mention the many beach hotels that suffered huge losses due to lack of customers (Eilperin, & Mufson, 2010; Tangley, 2010). The spill resulted into hundreds of law suits that were filed. A special investigative panel consisting of officials from the coast guard office as well as the department of Interior was constituted by President Obama to look into the issues that surround the oil spill. BP began an assessment of the resource damage as soon as they managed to control the spillage. The losses incurred by the company are huge since at least 185,000,000 gallons (which comes to around 4.4 million barrels) of oil was lost. The clean up process might have succeeded to remove the spilt oil but the ramifications on the environment are probably going to last for decades to come (Jervis, & Levin, 2010; Jervis, 2010) Th ere are many questions concerning the resource damage that might not be fully answered any time soon. The extensive media coverage during the duration of the spill raised important questions that unfortunately did not have very comprehensive answers. For instance: the delay in response to the emergency, the companies that are to blame and most importantly and if the environment could survive such a disaster. Who is to blame? Before the OPA 90 was passed, it was not very clear who amongst the federal state, private players and the other local officials was directly responsible in the event of an oil spill of the magnitude of the BP Mexican gulf spill. The current legislation now demands that federal government should step in immediately when such a disaster strikes. The responsibility on the government according to the OPA 90 covers spills on the land as well as coastal spills. Offshore incidents like the recent BP Gulf of Mexico spill lie well in these boundaries. In the same breath e; the OPA 90 also includes the coast guard as a party that should be in charge of evacuations and control of the spillage. The biggest challenge of this is that the coast guard may not have access to the kind of equipment and personnel that it requires to handle such spills. However, legislation gives the coast guard the authority to acquire the equipment from private companies. BP was consistently present during the control of the spill and though it was largely in charge of the process, it was also assisted by personnel and equipment that the coast guard had acquired. There was some tension between the government and BP originally. This tension was addressed by the reports made by the president’s commission. Ideally, the responsible party is both the partner and the adversary since they are in charge of containing the spill and they are also required to take responsibility for all damages. It is a relationship that often confuses the general public but it is something that was established in the OPA 90 (Schwartz, 2010). Oil spill management is usually based on the National Contingency plan. The National Contingency plan identifies the national, regional as well as the local infrastructures. It integrates the different agencies that might be involved in the event of a spill. The National Contingency plan usually comes up with an initial disaster response team both nationally and regionally. It coordinates the efforts by setting up an on-site coordinator as well as a centralised command

Sale of Goods Act 1979 Essay Example | Topics and Well Written Essays - 3000 words

Sale of Goods Act 1979 - Essay Example Section 13(1A) of This Act provides as regards England and Wales, the term implied by subsection (1) above is a condition. Under Section 13 of the Act there is an implied condition in a contract of sale, upon the supplier of a service in a contract that the goods will correspond with the description, which will apply to any sale where the purchaser does not see the goods before he buys them & when acting in the course of a business that he will carry out the service with reasonable contractual period. Even if the purchaser has seen the goods, there may be a sale by description if he has relied upon the description. In this question it need to discuss While 'description' itself is an ordinary English word, the Sale of Goods Act 1979 contains no definition of what it means when it speaks (in Section 13) of a contract for the sale of goods being a sale 'by description'. And then it needs to discuss that a contract is from between parties when the seller was agreeing to sell and the buyer agreeing to buy. Now it need to discuss about condition, sale 'by description', current possession, and misrepresentation. First, one has to decide what is the meaning of sale by description. In the case of Varley v Whipp1 it has been held that this phrase must apply to all cases where the purchaser has not seen the goods but is relying on the description alone. Therefore, a sale must be by description if it is of future, or unascertained goods. But in addition, the term applies in many cases even where the buyer has seen the goods. Not only the term "sale by description" includes goods of a generic kind, for example, a packet of brand X cigarettes but also specific goods when they are sold as a thing corresponding to description. In the case of Beale v Taylor2 the subject matter of the contract was described as a 1961 Triumph Herald Convertible and the plaintiff saw the car and bought it. In fact, it turned out to be two different cars joined together. It was held that the car did not comply with the description. In Grant v Australian Knitting Mills [1936] the sale of woolen underwear was held to be a sale by description even though the buyer was buying something displayed before him on the counter. But a sale is not a "sale by description" where the buyer makes it clear that he is buying a particular thing because of its unique qualities, and that no other will do, or where there is absolutely no reliance by the buyer on the description (Harlingdon Ltd v Christopher Hull Fine Art Ltd3). In other words it appears that the only case of a sale not being by description occurs where the buyer makes it clear that he is buying a particular thing because of its unique qualities and that no other will do. For this reason, the sale of manufactured item will nearly always be a sale by description (except where it is second hand) because articles made to an identical design are not generally bought as unique goods but as goods corresponding to that design. In the Harlingdon case, the buyer was a professional art dealer who knew the seller had no experience or knowledge of the type of painting being said. There was accordingly no breach of s. 13 when the painting turned out to be a forgery. The buyer had placed no reliance on the seller's description. These cases suggest that the real question at issue in deciding whether the sale should be classified as a

I predict that as the force increases Essay Example for Free

I predict that as the force increases Essay Newtons second Law of motion: Force = Mass x Acceleration (N) (kg) m/s (variable) (measurement) In simple terms, this means that if the force is to increase then the acceleration must also increase because the mass multiplied by the acceleration must equal the force. The equation, like many others can be re-arranged in order to show a possible prediction for the value in m/s that the acceleration will be the subject of the equation. Acceleration = Force (Mass / 0. 400kg) Mass Weight is a force. Weight is quite oftenly confused with mass, however each one differs to the other. Mass is measured in kilograms (kg). The weight of an object only concerns the amount of matter an object is made up of. In contrast to the mass of an object, the weight of an object regards how much it is being pulled down to the centre of the earth through gravity. Weight is a force and is measured in Newtons (N). Diagram of apparatus: The experiment that was carried out occurs when a slider is pulled through two light gates via a weighted pulley upon a soft bed of air to minimalise friction powered by a vacuum connected to the air track. When the rider breaks the beam produced from Light gate 1, a recording is began by a computer linked up to both light gates. Once the rider cuts through the second light gate, then the timer on the computer steps automatically as the light gates can relay a signal to the computer. A computer is used rather than the naked eye because the computer can be precise to 2 decimal places (d. p). Once the slide has passed through both light gates, it is moved around both light gates and the experiment is repeated. The variable for this investigation is force, that is controlled through the weights used n the pulley. The weights are changed at five separate times, at each time a different weight is used. My variables are as follows: 0.02 N , 0. 03 N , 0. 07 N , 0. 08 N , 0. 12 N ( N = Newtons) The values I chose are all the smallest possible values that I am able to create. In relation to safety, there are no specific safety issues that come to into play during this particular investigation, however behavior around the apparatus and the laboratory is always considered a safety issue. The factors that are necessary to maintain as constants throughout the experiment in order to keep a high degree of accuracy are: Â  Straight light gates (equidistant 40cm apart) Â  Same starting point of the rider ( 5cm before the initial light gate). Mass of the rider (0. 400kg) The light gates are required to be equidistant (40cm apart) and level in order to keep the test so accurate readings can be recorded. The mass of the rider must also be mentained at exactly 0. 400 kg because a slight chance in the weight will cause a change in the acceleration of the rider can result in widespread and inconsistent results. It is also important to mention the starting point of the rider that must remain constant in order for the rider to pass through each light gate at the same speed during each repeat reading recorded. In addition to these points of accuracy, there are others, which have sufficient relevance to the experiment. The level at which the air track is must be kept horizontal so that the rider has neither too longer, or too shorter acceleration value that is recorded due to the slider being against or along the gradient of the air track. This can be simply modified by adjusting the track then leaving the rider without a weight and switch on the air track, if the rider remains stationary then the air track is horizontal. The experiment will be measured on 3 occasions for each variable, these repeat readings will be averaged out into a single figure to gain an accurate set of results. To prepare for the investigation, a preliminary test was carried out in order to discover which mass of the rider produced the most accurate results. To do this, the lightest mass of the rider was used with the lightest and heaviest weights (0. 020N lightest) and (0. 170N heaviest). The masses of the rider were the largest possible (0. 400 kg) and the smallest possible ( 0. 200kg). The results showed me that the lighter the mass of the rider, the wider the range of results that I recorded. In contrast, the heavier the mass of the rider was, the more reliable my results were because they provided the smallest range. This meant that I chose the heaviest possible weight of the rider possible, which was 0. 400kg. Skill area O (Obtaining The Results): FORCE (N) MASS (KG) Acceleration ( m / s ) Test 1 Test 2 Test 3 Average 0. 02 0. 400 0. 05 0. 04 0. 05 0. 05 0. 03 0. 400 0. 07 0. 08 0. 07 0. 07 0. 07 0. 400 0. 18 0. 18 0. 17 0. 18 0. 08 0. 400 0. 19 0. 19 0. 21 0. 20 0. 12 0. 400 0. 31 0. 31 0. 310. 31 Skill area E : Evaluation: My results throughout my investigation, were very accurate. The spread of my repeat readings were very small, each reading for each strength of force were close together shown a high level of accuracy throughout the investigation. All my average points that I recorded are close to the best-fit line that I have drawn, which suggests that all my results have been accurately recorded and displayed in my analysis and obtaining evidence sections. The procedures to which I applied my investigation were suitable because I was able to produce an accurate set of results with relative ease. In my opinion, my evidence can support a sufficient conclusion that as that the force upon on object is directly proportional to its acceleration produced. My results were tested over a reasonable range and are considered accurate as they fit in with my initial theory and also they fit in with my initial predictions that I was able to produce. I was able to produce these predictions by re-arranging Newtons second law to show me what the acceleration of an object can b equal to in terms of its force and mass. (Old equation) Force = Mass x Acceleration (N) (kg) m/s (variable) (measurement) (New, Re-arranged equation) Acceleration = Force (mass / 0. 400kg) Mass I have a range of values for my force, I inputted each one of these values to gain predicted results. (When force = 0. 02) : 0. 02 = 0. 05 (Actual average = 0. 05) 0. 400 (When force = 0. 03) : 0. 03 = 0. 075 (Actual average = 0. 07) 0. 400 (When force = 0. 07) : 0. 07 = 0. 175 (Actual average = 0. 08) 0. 400 (When force = 0. 08) : 0. 08 = 0. 20 (Actual average = 0. 20) 0. 400 (When force = 0. 12) : 0. 12 = 0. 30 (Actual average = 0. 31) 0. 400 As the above figures display clearly, my results are all highly accurate and sufficiently support my prediction and theory. All that remains is to discuss how I can extend my investigation. The obvious point that springs to mind is to gather further results to obtain an exceptionally high level of accuracy. However, I can also look to change my variable from the force to the mass of the rider. I can do this by investigating the relationship between the mass and force on a rider to give me additional information. I can carry out these tests in the same manner as I have discussed for this particular investigation, but changing the variables used. I will use a range of variables that will aid me complete my investigation reaching sufficient conclusions.

The History Of The Heavyweight Methodologies

The History Of The Heavyweight Methodologies INTRODUCTION Software has become an essential part of human life both at professional and personal end. The development of software has become a chaotic business and is normally cited as the code and fix. In the initial days the software programs were written without much of plan, design and without long term site. This however was fine for the small systems. With the advancement of technology several changes were made and it became difficult to incorporate these changes and it was hard to fix the bugs. This was the result of improper planning. This has led the roots to another alternative, Methodology. This emphasized on the disciplined process of software development to make the whole software development process smooth and predictable. Traditional methods were heavily dependent on documentation, design, work plan and structure making it the way to call it the heavy method. However, this seemed increasingly lengthy and frustrating for few developers who were looking for rapid change. This has resulted in consultants preparing methodologies independently. These methods are known as agile methods. Agile methodology is getting extensive popularity in the industry. This is a mix of accepted and controversial practices. It is the features of the projects such as scope, requirement, resource and size that determine the appropriate methodology that should be used. Thought practicing professionals still emphasise on the importance and usage of heavy methods, the empirical studies are emphasizing on the Agile methods. Heavyweight methodologies Heavyweight methodologies are considered the traditional way of software development. These are based on step by step evolution approach. Several steps in this process include, defining requirement, solution formation, testing and development. In this process it is also mandate to prepare a document that has a set of requirement at the beginning of the project. Waterfall approach: This emphasizes on structured approach. Each stage in this process has a set of actions. These activities much be fulfilled before progressing to the next stage. Each phase is named differently. The first phase determines what the system will be, the second phase determines how the system will be developed. It is in the third stage that the actual coding and designing is started. The developed system is tested in the fourth stage. In the fifth and final stage appropriate training and documentation are provided. In terms of engineering, the term waterfall is used to denote a subsequent or sequential development. Waterfall Model Life Cycle Unified Process (UP) Each activity comprising modelling is divided into workflows in the UP process. This process takes place in an repetitive and incremental manner. In this method the whole process is divided into four phases. The below diagram depicts the stages of this process: Inception At the end of this process the feasibility of the project is determined. The scope of the design is set and a business plan is prepared. Elaboration In this phase, a basic design is made and a plan of structure or construction is made. A risk analysis is also done at this stage. The major risks determined should also be addressed. Construction In the construction phase the system of beta-version is prepared. A well developed system good enough for the preliminary test should also be available in this stage. Transition This is the final stage. In this stage the system is commenced to the stakeholders and end users. The process is considered complete if the stakeholders agree that the objectives mentioned in the inception phase are met. As part of UP there are approximately 50 work items that should be completed. This rigid approach and heavy documentation add a lot of the complexity to the UP. Also, the roles in this process are predefined making it less flexible. Spiral Model This is another heavy model which merges both design and prototype stages trying to combine the benefits of top-down and bottom-up benefits. The four phases in the development model are as follows: Objective setting- In this phase objectives of the project phase are identified. Risk assessment and limitations In this phase key risks are identified and analysed. Information about reducing these risks is also collected in this phase. Development and validation A suitable model is selected for the next phase. Planning The project is reviewed and plans for the next round of spiral are made in this phase. Characteristics of Heavyweight methodologies Heavyweight methodology is known for a long time. This is a very disciplined approach in the software development. Few characteristics of heavyweight methodologies are as follows: Predictive approach: This methodology plans most part of its software development for a longer time. A great emphasis is given to drawing focusing on the needs and measure to answer these needs. Drawings determine how to build the system and act as the basis for the construction process. This also predicts time table and budget for building or constructing the software. Inclusive Documentation: Traditional software development considers the requirements documentation as a key element of documentation. It collects all the customer and stake holder requirements before writing code. Process orientation: The purpose of this method is to allocate or define a process of work that suits the one using it. A process may contain few processes just a manager or a tester can perform. For every task in this method there is a procedure. Agile modelling Agile process concentrates on adding lightness to its processes leading to high quality of software and customer satisfaction. Few of the agile models are as follows Extreme Programming (XP): This has evaluated out of problems raised from traditional systems. This process is known for short cycles of development, incremental planning and continuous feedback, communication leading to evolutionary designing. This methods life cycle is divided into 6 phases i.e. Exploration, Planning, Iterations to release, Production, Maintenance and Death. During the Exploration stage, the client creates story boards about his needs. This is followed by the planning phase in which the story boards are prioritised and a first release schedule is prepared. In the Iteration to Release stage it is the responsibility of development team to create the whole system by continuously testing and integrating the code. In the Production Phase additional testing and performance checks are done. Developments and suggestions detected in this stage are documented for later implementation. Based on this updated releases are made in Maintenance Phase. The final stage is the Death Phase is reached when customer has no more stories to be implemented and the final documentation is prepared. Scrum: Scrum is a repetitive and incremental process of product development. Scrums main focus is on how members should work in order to generate flexibility in a continuously varying environment. At the end of each iteration it makes a set of potential features. In this method it is not compulsory to use any specific software development methods. Key practices in this method are : Product Backlog, Sprints, Sprint Planning, meeting, Sprint Backlog and Daily Scrum. Dynamic System Development method: This is a mixture, and extension for rapid application development and iterative development practices. The basic notion behind this method is to give more importance to time and resources before the functionality of a system. In this method a high emphasis is given to quality. This method has five stages : Feasibility Study: A decision is made about usage of DSDM. This decision is based on project type, organization requirement and people. This stage has two outcomes, 1) feasibility report ii) A prototype plan Business Study: A business study to understand the business aspect of the project. This forms the base for prototype. Functional Model Iteration: This phase includes analysis, coding and prototypes. The output of this stage is a prototype code and analysis models. Design and build iteration: Main system is built in this stage. The prototypes are reviewed and developments are made based on user comments. Implementation: This is the final stage where the project is handed over to the user. Appropriate training is also provided. Characteristics of agile methodologies People oriented: All the stakeholders. i.e. customers, developers, users and end users are very important in this methodology. Adaptive: This methodology is preferred by those who are open to change and are flexible. Balancing Flexibility and Planning: Though planning is important, a trial and error method is followed in this approach as it is hard to predict the right things in the initial stage of software development. Simplified process and small groups: A simple process of concentrating on the present rather than the future is the motto of Agile process. It also maintains small teams and any communication is provided to the whole team. Comparison Traditional heavy methodology for software development is prevailing successfully for a long time now. However, it has several disadvantages such as inflexibility and high time consuming etc. Taking these drawbacks in to account a new system was developed which is Agile. Both the methodologies i.e. (agile and heavy weight) have their advantages and disadvantages. People usually use one of these methods based on the feasibility. A Summary of difference in agile and heavyweight is shown in the following table. There are important factors influencing the decision and selection methodology, which is suitable for different conditions. These factors can be divided into the size of the project, people and risk Project size: One of the major limitations in this process is size of the project. The important elements in this process are budget, time span of the project and team organization. A huge project needs huge team and huge budget. This in turn requires better co-ordination and better communication. Heavy methodology provides this by a thorough planning, design and documentation. However, this is not possible in case of Agile process. According to Alistair A light process needs few people in contrary to the heavy method where more people are required. A major limitation of agile methods is the size of the project. Main elements of the same are budget, duration of projects and organization of the project team. The larger unit or a larger budget, you need the larger project. Thus, requires a compilation of more demands, requirements of more people and better coordination. Heavyweight support this methodology by providing planning, documentation and processes for better communication and coordination in large groups. Fewer people are needed if the methodology used is lighter. However, more people will be needed if the heavier methodology (Alistair Cockburn, 2003). The larger group also has its impact on communication in the design and performance. The methodology is a matter of coordination and management of human communication. This implies that the level of methodology must be increased if the numbers of people increase. This makes it even more difficult to use agile methods with large groups. However, Ken Schwaber (one of the deve lopers of SCRUM) argues that large groups can be broken down into small teams using the dimensions of the scrums. Project duration is another factor in the choice of methodology. Heavyweight methodology needs a lot of extra time for output such as documentation, design documentation, writing, analysis etc. Therefore, it can be concluded that when time is short agile development methodologies would be the best option. People Factor: The Agile methodology gives very much importance to stakeholders i.e. it concentrates on peoples factor. This methodology makes sure that experienced people and skilled people are part of the process. Experts who are part of the team provide continuous feedback about the effects that the use may face in selecting the project. As part of this process the customer also gets a right to check progress and change the direction of development at any stage or iteration. This is one of the main features that make the agile process more attractive than the heavy process. Organizational culture is another important factor while choosing the methodology. If any organization is not open to change and is inflexible, An agile process cant be used there. Risk Factor: An important risk factor in the software development is how it responds to change. Agile methods can be used in case of applications that should be built quickly and dont have any quality hurdles. If the project is critical and requires several quality layers then the traditional system is appropriate. Improper definition may lead to several defects. Agile methodologies help in developing short term projects and give importance to customer reviews. Conclusion I would like to end it by saying that heavy methodology consisted of severe methods of comprehensive planning, design documentation.. Heavy thoughts that accompany them will be taken over by the agile movement not in the distant future. The need for Heavyweight approaches still prevails in large, long-lived projects that have specific security, reliability and security requirements. However, business needs to respond quickly to the environment in innovative, cost-effective and efficient manner is increasing the need to use agile methods of software development.