A Project Management Overview Of The Xp Software Development Methodology

1895 Words4 Pages
bulb-icon

Recommended: Contrast methods of agile and waterfall

A Project Management Overview of XP Software Development Methodology This paper will discuss at a high-level how software development projects are run when implementing the extreme programming (XP) methodology, and explain during which step, XP covers the Project Management Institute’s (PMI) process groups, and management knowledge areas (MKA) [9]. After the XP process is discussed, XP’s unique way of developing code, its documentation management, and user-centric approach are explained. Since XP is written as being easy to implement, a short discussion of where the real work occurs is included, then guidance on what types projects it is best to implement XP. A brief overview of agile methodologies (AM), of which XP is but one, is included first. Agile Methodologies The characteristics of AM are that they the value “(a) individuals and interaction over processes and tools, (b) working software over comprehensive documentation, (c) customer collaboration over contract negotiation, and (d) responding to change over following a plan”[1]. AM concentrate on developing functionality over managing the development of functionality. The management of traditional software projects favors a well-planned approach – typically called the “waterfall approach” – documenting all project details before development starts. AM advocates creating a high level design of the whole system, then working on functionality in ascending order from highest to lowest in customer perceived business value. All AM assume requirements will change constantly so shorter development cycles are instituted to accommodate for the new or changed requirements. AM also assume close contact with the business (for the purposes of this paper, business, client, & user are used interchangeably) to answer any questions, and help resolve issues related to design, cost, and scheduling. XP Step One – The Planning Game The first step of an XP project encapsulates the PMI Initiating and Planning processes and is called the planning game. The planning game is a meeting in which desired functionality is discussed and analyzed via the creation of user stories [1]. Participants are users, project and development managers, architects, and developers. Other stakeholders, from the business or development side who can add value to the design of the functionality of the proposed system, are included when needed [3]. After business prioritizes the user stories, development estimates how many top priority user stories can be achieved within the first iteration/coding cycle (iteration velocity [5]). This process continues until all user stories are planned for in subsequent iterations, thus creating the project plan.

Show More
Related

  • Agile Management: Enhancing Project Success

    766 Words  | 2 Pages

    Agile project management is an iterative approach to the planning and monitoring of project processes. Agile projects are conducted in smaller tranches called iterations with each of these iterations closely reviewed and critiqued by the project team (employees, representatives of the clients etc.). The knowledge gained from this process is then used to ascertain the next steps of the

    Read More

  • Using Software Development Life Cycle at GM Wilmington Assembly

    1416 Words  | 3 Pages

    The Software Development Life Cycle is seldom used at my place of work. Unfortunately, recent developments in its use are deemed confidential. Due to this fact, this paper will examine in general terms one of the projects we are undertaking right now while at the same time attempting to maintain our confidentiality.

    Read More

  • Project Management Case Study

    1070 Words  | 3 Pages

    What’s the problem at WCBA? Currently, it seems to be a lack of training and leaderships. Ms. Calder is doing a wonderful job building relationships and making the students feel welcome however she is failing at setting the standards on how to run the station effectively. Also, she is spending more times trying to build friendships than training the students and holding them accountable.

    Read More

  • Systems Development Life Cycle ( Sdlc )

    829 Words  | 2 Pages

    The Systems Development Life Cycle (SDLC) consists of phases used in developing a piece of software. It is the plan of how to develop and maintain software, and when necessary, replace that software. In 2007 during my hospital’s transition to a new software system, I was fortunate enough to be included in the process. I did not get involved until the implementation phase, but from then on, until now, I remain very active in the process. I decided to highlight the Waterfall Model of SDLC. The Waterfall Model is a “sequential development process” with each phase continuing in a line (McGonigle and Mastrian, 2012, p. 205).

    Read More

  • Extreme Programming Up Front Design Methodologies

    734 Words  | 2 Pages

    Extreme Programming (XP) has spent the past decades under perpetual scrutiny by software developers fixated on up front design methodologies. The idea behind this is simple: if you want to make sure something is well built, you must design it well first, then put it together using reliable tools. For objects such as houses, cars, or tables, of which the design evolves gradually throughout decades, the methods of up front design suffice. Computer programs, on the other hand, are products often made for an industry that evolves at higher rates than any other. For this type of environment, more dynamic methods are required, which is why XP suits as a viable candidate.

    Read More

  • Project Management Case Study

    821 Words  | 2 Pages

    The projects in today’s world are given a lot of importance and it will continue to grow in the coming years. There are a lot of companies which do not have production, but all of them do have projects. There are a lot of books which have been published on which related to planning and managing the projects. The one of the most important one was published by the author Eli Goldratt in his book ‘Critical chain’. This book basically talks and shows how the application of theory of constraints in the field of project management. The novel is basically based on one of the MBA classes in America where a number of ideas are developed in discussions among the students and the lecturers. The lecturer is basically fighting for a tenure with the president of the university who expects a downturn in the executive MBA. The lecturer who teaches project management has a word with one the senior colleagues and project management was the right topic to teach. There were three students who were placed in the project management team of their company which manufactures electronic products. The students are enrolled in this MBA class along with other students, here they discover a new approach to project management which is known as the

    Read More

  • Agile Approach In Construction Case Study

    1625 Words  | 4 Pages

    The agile approach is based on the idea that change can be of value to the client. The details of the project, the scope of it, are defined as far as value for the client is known. This makes the delivery of value to happen in a short time. And by receiving constant feedback, project progress will be achieved. This will lead to having a result that satisfies the client and not a result that will satisfy what was specified at the beginning of the project. To be able to see these changes as something positive and of value to the client, a more proactive organization is required (Owen, Koskela, Henrich, & Codinhoto, 2006).

    Read More

  • Software Development Methodology Of Fuzzy Logic And Project Management

    2655 Words  | 6 Pages

    During this research only three methodologies wiz Rational Unified Process (RUP), Rapid Application Development (RAD) and Extreme Programming (XP) are considered. The paper is divided into 6 sections. Section 2 & section 3 describe about the basics software development methodologies (RUP, XP, RAD) and Fuzzy Logic respectively. In section 4, our proposed approach is discussed while section 5 concludes the

    Read More

  • Project Management Case Study

    834 Words  | 2 Pages

    The topic of my group (group 4) was “How to totally float through your project for free” and the presentation was held by Roger Goodman who works for PMI NZ and Ernst & Young supply chain management with many years of working experience in many different countries such as Saudi Arabia and China.

    Read More

  • Rational Unified Process

    1248 Words  | 3 Pages

    Given the time, it takes to develop large sophisticated software systems it not possible to define the problem and build the solution in a single step. Requirements will often change throughout a projects development, due to architectural constraints, customer’s needs or a greater understanding of the original problem. Iteration allows greater understanding of a project through successive refinements and addresses a projects highest risk items at every stage of its lifecycle. Ideally each iteration ends up with an executable release – this helps reduce a projects risk profile, allows greater customer feedback and help developers stay focused.

    Read More

  • The Pros And Cons Of Agile And Plan-Driven Process And Methods

    664 Words  | 2 Pages

    As per Boehm and Turner concepts of balancing agility and Discipline six exemplary conclusions were made, of which first one is that neither agile nor plan-driven processes and methods provide a silver bullet which implies that either of the agile or plan-driven approach is not applicable in all situations. Both the processes deals with the essential software engineering complications like complexity, changeability, invisibility and conformity while both the processes have its own advantages and disadvantages. Agile method to some extent achieves changeability and invisibility as the project’s strategies and its implementation is discussed and shared among all the members of a team whereas it fizzles to handle complexity of the project and conformity. Also agile method fails in scaling up to large complex projects. Plan driven concepts handle conformity and invisibility as thorough documentation and extensive planning is done. But it fails in handling changeability as it is difficult to do re-documentation every time and also fails to handle increasing complexity as new systems are added which involves enterprise integration. Hence it can be said that neither agile nor plan-driven processes provide silver bullets instead they can be termed as lead bullets individually.

    Read More

  • Project Management for Information Systems

    3601 Words  | 8 Pages

    Williams, (1997) identified four steps to system planning. Earl (1989) proposed five alternate strategy frameworks which project managers should consider when deciding how the system will enhance the business function. Standard business strategy methods are used to identify such opportunities by using: value chains, application searching and information analysis (Earl 1989).

    Read More

  • Case Study Of PMO

    953 Words  | 2 Pages

    AtekPC had developed a vast array of IT applications primarily focused on for the use of business functions like accounting, manufacturing, sales and distribution. There was very little integration between these systems. Most projects were medium sized and were managed informally by the development team (Lead Analysts). Any new development or maintenance projects were undertaken using an informal approach and this led to quick response time and also fewer conflicts. Also the Lead Analysts had long tenures and developed a deep understanding of the business requirements. Changing business needs required complex projects that involved multiple functional and technological areas. The demands of t...

    Read More

  • An Evaluation Of Requirements Engineering

    1478 Words  | 3 Pages

    As more companies that are leading technology are transforming from the traditional waterfall development model to an Agile software methodology, requirements engineering provides a process for software engineers to understand the problems they need to solve (Martin, Newkirk, & Koss, 2014). It is of key importance to understand the customer 's wants and needs before beginning designing or building the computer-based solution, as developing a solution that ignores the customer’s needs provides value to none of the parties involved. Thus, the intent of requirements engineering is to produce a written understanding of the customer 's problem (Pressman, 2010). Work products that are available to communicate this understanding include user scenarios, function and feature lists, analysis models, and specifications. This paper provides an evaluation of requirement patterns, an assessment of problem solving techniques most effective, a descriptive explanation of the patterns that includes a visual taxonomy, and an explanation of how the patterns identified are related.

    Read More

  • The Vision of the Software Development

    778 Words  | 2 Pages

    The Software development field has grown with exponential rate. New products are coming to market daily. New innovations are flooding. Today the world of Software development is very large and much more complex than at any time. New software in large amount is hitting the market from beta version to fully functional products. This near-exponential growth in Software development market isn’t limited to any one segment of market. Rather it’s to Software Development as a whole – and it represents a huge challenge that must be addressed.

    Read More

More about A Project Management Overview Of The Xp Software Development Methodology

Open Document