Programming Team Methodologies - Coursework Example

Programming Team Methodologies Introduction Software development methodologies are important for programming teams that are keen to make sure there is good information flow system, and the team also develops. There are many methodologies that different organizations rely on. The decisions on which approach is important in most cases depend on the type of programming teams that the business firms use. Programming is an important area of any organization that is determined to become successful in its operations. It helps the organization or business firms to be able to plan and avoid missing out some important things. Therefore, there is the need for programming teams to be included in organizations so that they help in planning activities and administration of information. There are various programming team methodologies that firms can rely on to ensure they have an effective system development plan. This paper is going to look into three approaches to team programming in terms of how they are similar and different to each other. System development life cycle (SDLC) This is a programming method that deals with project management. For any project that is aimed being successful, information is a key factor. The SDLC methodology highlights the steps that are to be taken when developing information systems. In this methodology, emphasis is on the process of coming up with an information system for an organization. The process is usually systematic with every stage requiring full participation of the team members. There are many examples of SDLC methodologies being used by various organizations for team programming. They include the Joint Application Development, the Waterfall Model, and the Rapid Application Development[Con11]. The first stage is usually an analysis of the systems that the organization in question has been using in its operations. The stage is only applicable when the firm is not trying out the idea of having information systems for the first time. At this point, the shortcomings of the already used systems are highlighted through interviews with the users of the system. The next stage in the SDLC methodology is handling of the deficiencies noted in the first step. The organization can also think of the requirements for a new information system in a case where there was no system before. It is at this level that improvements to the programs and software used by a group or team can be done[San11]. This methodology also entails coming up with proposed systems for the organization being served with the programming team. The design of the system contains details about the hardware required, the safety matters and operating systems needed. Requirements are supposed to be assembled after the management of the project has approved the proposal. The next stage in this method of programming is developing of the proposed system. A system that is well planned always contains all the requirements available, and the objective of the system well stated[Mat15]. The programs availed will then be installed as operations begin. SDLC method pushes for the organization or team to use components of standard qualities only[Con112]. Finally, the system being developed is put into use after it has been assembled to become a complete information system program. However, regular thorough evaluations are supposed to be conducted as per this methodology. The evaluations are meant to spot any areas that are to be improved for the system to become fully efficient to the users and the organizations. SDLC is a programming team method that is aimed at providing an outline of how a new system of operation can be introduced into an organization. The system can be information systems or any other operation systems in the firms that need to be programmed for better performance[Sha122]. Extreme Programming (XP) The approach of extreme programming is usually a methodology for developing an information system or software in an environment where things are not stable. The main idea behind the extreme programming methodology is to make the process of coming up with information and operation systems as flexible as possible. Under this approach, programming is done with an aim of cutting down the costs of making changes to the existing systems. In this approach, there are five qualities that also turn out to be the process of implementing the approach in team programming. Communication is the first value that the XP methodology puts into consideration as being one of the necessary factors for success in an operational and information system. the approach states the importance of good communication between the developers of the systems and the users. The clients of the firm can also get informed about any important ideas through effective communication[Din12]. Feedback comes in a good complete communication challenge. However, it is considered as a separate quality that is important for the success of team project developments. According to the extreme programming approach, the customers of a business firm should also be given room by the management to react to any system programs that run products for the organization. Input from the systems themselves can also be communicated back through feedbacks after enquiries are made[Moh13]. The same way, team members get to be connected easily through the feedbacks that they give according to the condition that all team members should have a point for the team. The approach of extreme programming pushes for courage as another critical element for the development of programming systems[Str12]. Courage is a quality that would enable a member to make important decisions for the organization or team without having fear. Courageous forces make it easier for codes that are adding no positive value to the organization to be dropped. The third value for this methodology is having simplicity. The approach requires that the process put down for the programming team to follow be as simple as it can be. The reason for the simplicity is the fact that the approach is aimed at making the process of programming flexible. Simplicity also helps in cutting down unnecessary costs that may arise when an organization or team is facing changes in its software systems. Reduced cost of implementing changes to software is among the major goals of this programming team methodology[Con111]. Eventually, respect comes out as another value that extreme programming advocates for when creating software and information systems. The approach believes that respect among team members is an important value that would make a team cooperative enough to work as a success-oriented team. Due to the respect, it even becomes impossible for a selfish team member to make a decision that would cancel a well-done job[Fer13]. The extreme programming methodology is targeted at making an information development team accept changes in their operations without involving a lot of risks. The approach is concerned more about the quality that programming teams offer, and cutting down the costs of adapting to changes[Fit12]. The Agile Methodology The agile model is a method of team development that is more concerned about the communication networks of team member irrespective of their geographical distances. In this approach, it is first necessary that the team or working cells be spotted and located in a particular area. The method is a combination of various approaches that are all directed towards achieving the same goals as the agile methodology. The examples of models under this approach include Crystal Methods and the Scrum Model. Just like the Extreme Programming, Agile Methodology also aims at minimizing the possible risks that an organization might face while trying to develop or improve a software system. The methodology introduces a series of stages through which these risks can be avoided. For instance, it starts with breaking the entire project into short timeboxes which are referred to as the iterations[Ger112]. The idea of the timeboxes is to make the project easy to evaluate and improve. Each timebox is expected be on for less than four weeks. This makes it possible to have constant regular analysis of the project. At iteration levels, there is a set of tasks that are to be done. Among the tasks done at each level include, an analysis of the requirements to get a system running, documentation for the system, and the design to be used[Lit11]. It is expected that at the end of each timebox there will be a newly completed software or information system. After the many subsections of the project in terms of the iterations have been completed, an entire reevaluation of the project is done. The agile methodology is an approach whose main objective is to bring in the real-time communication into a team’s operations. Due to this reason, many teams that are operated under this approach are usually divided into bullpens that enable team members act as if they were located in the same area. In the bullpen, actual customers, programmers, and analysts form the main members. Therefore, the methodology advocates for communication systems that are more of face-to-face. The issue of written documentation is not emphasized in the agile approach. The differences in the methodologies System development life cycle (SDLC) Extreme Programming (XP) The Agile Methodology It talks of the steps involved in developing an information system mainly. It talks about the core values that are critical for success in the development of a system. Its main concern is the ability to have real-time communication in a team. It does not look into the cost of implementation of the software or system program. It is concerned with reducing the costs that are incurred when changes in a system are introduced in the organization. The methodology does not major on the costs of introducing the new software and information systems. Coordination and communication of the team members are not restricted to a specific. Functionality of the methodology is not fixed to a particular communication method. It focuses on using face-to-face communication as it is aimed at creating real-time communication. In this methodology, team members can work in dispersed location. Team members can be coordinated from any geographical location for operations. The approach pushes for the whole team to be located in the same place. The similarities of the three methodologies System development life cycle (SDLC) Extreme Programming (XP) The Agile Methodology Customer participation is encouraged through interviews to highlight the challenges of the existing systems. Customers participate in the programming when they give feedback concerning the knowledge spread through the processes. The actual customers are among the members of the bullpens that are formed in this approach. The methodology seeks to better the information systems of the organization or projects through improving and introducing new systems. It also seeks to better the structure of developing information systems by highlighting the values critical for the processes. The approach seeks to improve the coordination of project members in programming through iterations that minimize project risks. The three methodologies explained in this paper are all important in ensuring the practices of programming teams run smoothly. However, among the three it is the System development life cycle (SDLC) that I would consider the best option. The reason is because this methodology gives the necessary steps that ought to be taken when a programming team wants to improve its operations or improve the information system they rely upon[Hog11]. The difference for global, virtual and co-located programming teams Location of team members differs in these types of programming teams. Global programming teams are usually made of members who are distributed across the continent. For such teams, the members can be found on different continents but still manage to work together. On the other hand, co-located teams are usually made of team members who are found in the same working environment. For these workers, it is usually easier for them to connect. Virtual programming teams are can either be located in the same area or dispersed locations. The members are usually connected through remote technologies. Due to the geographical distances between members, their ability to be clear on the team goals varies. The global programming teams are affected most by this issue as the members are usually not so clear about the goals they are set to achieve because of the communication challenges. The virtual teams are usually connected in a way that they operate as if the operations are from one location. Therefore, virtual and co-located programming teams have their members clearly informed about the organizational or team goals. When a programming team methodology is being picked for any team, it is advisable that type of team to use the system to be identified[Iiv11]. The reason for this is because different approaches can only be suitable for some types of teams. For example, the agile model emphasizes on the use of real-time communication which is only appropriate for virtual and co-located teams. Conclusion Even though the three programming team methodologies discussed in these paper are very useful in ensuring effective planning and information systems are in place, the success of the approaches depend on how teams apply them. For example, in the case of system development life cycle (SDLC) approach the team players must always be ready to follow the steps in this model properly. It is also important that the choice of approach to be followed is made while considering the type of team that is going to implement the new system adapted by the organization. Therefore, there are a lot of factors to have in mind when dealing with team programming, and it is determined that the team becomes successful. References Con11: , (Conboy, Agility From First Principles: Reconstructing the Concept of Agility in Information Systems Development, 2011), San11: , (Sanchez & Mejia, 2011), Mat15: , (Matharu, Mishra, & Singh, 2015), Con112: , (Conboy & Golden, Agility in Information Systems Development: A Three-Tiered Framework, 2011), Sha122: , (Sharma, Sarkar, & Gupta, 2012), Din12: , (Dingsoy & Nerur, 2012), Moh13: , (Mohammed, Alwadan, & Ababneh, 2013), Str12: , (Strode, Huff, & Hope, 2012), Con111: , (Conboy, Coyle, & Wang, People Over Process: Key People Challenges in Agile Development, 2011), Fer13: , (Fernando & Mendis, 2013), Fit12: , (Fitting, 2012), Ger112: , (Gerhat & Yelowitz, 2011), Lit11: , (Litan & Apostu, 2011), Hog11: , (Hogan & Raja, 2011), Iiv11: , (Iivari & Iivari, 2011), Read More