1.extreme programming-NCCA
- 2. 2 IntrodctionIntrodction In order to illustration agile process in a bit more detail, I’ll provide you with an overview of Extreme Programming. XP motto: “embrace change” means to accept the change XP values XP process Pair programming Industrial XP
- 3. 3 Embrace changeEmbrace change In traditional software life cycle models, the cost of changing a program rises exponentially over time A key assumption of XP is that the cost of changing a program can be hold mostly constant over time XP is a lightweight (agile) process: Embrace change: 1. Design and redesign, code and test frequently, keep the customer involved. 2. Deliver software to the customer in short time. 3. Eliminate defects early, thus reducing costs.
- 4. 4 XP ValuesXP Values C - Communication S - Simplicity F - Feedback C - Courage R - Respect XPvaluesXPvalues
- 5. XP ValuesXP Values continue…continue… Communication: Communication between software engineer and other stack holders. Collaboration between customer and developer. Feedback: It is derived from three sources: 1. Software it self 2. Customer 3. Other Team-members 5 XPvaluesXPvalues
- 6. 6 XP ValuesXP Values continue…continue… Simplicity: XP should be very simple. XP Restricts developers to design only for immediate needs rather than consider feature needs. Courage: XP practice demands for courage. A better word is “Discipline”. Agile XP must have discipline to design for today’s generation. XPvaluesXPvalues
- 7. 7 XP ValuesXP Values continue…continue… Respect: Agile team includes or indicates respect among it members, between other stack holders and team members, and indirectly for the software itself. XPvaluesXPvalues
- 8. 8 XP ProcessXP Process continue…continue… P - Planning D - Design C - Code T - Test XPProcessXPProcess
- 9. 9 XP ProcessXP Process continue…continue… XPProcessXPProcess
- 10. XP ProcessXP Process continue…continue… Planning: It begins with listening a requirement gathering activity that enables technical member of XP team. Listening leads to the creation of a set of “series” that describe required output. Design: XP design follows the “KISS“ principles. KISS means “Keep It Simple, Stupid!” A simple design is always performed over a more complex representation. 10 XPProcessXPProcess
- 11. 11 XP ProcessXP Process continue…continue… Coding: After Planning & Design this process is occurs. Here member of team will generate the code for the system as per requirement of the customer. Testing: Here the code which was created in above step is being tested by the another member of the agile team. If there is any problem in the coding that person will solve the problem. XPProcessXPProcess
- 12. 12 Pair programmingPair programming Two programmers work together at one machine Driver enters code, while navigator checks it Periodically switch roles XPPracticesXPPractices Research results: Pair programming increases productivity. Higher quality code (15% fewer defects) in about half the time (58%). Williams, L., Kessler, R., Cunningham, W., & Jeffries, R. Strengthening the case for pair programming. Requires proximity in lab or work environment.
- 13. IXP:IXP: IIndustrial endustrial eXXtremetreme PProgrammingrogramming IXP incorporates six new practices that are designed to help ensure that an XP Project works successfully in a large organization. 1. Readiness Assessment 2. Project Community 3. Project Chartering 4. Test-driven Management 5. Retrospectives 6. Continuous Learning 13 IXP
- 14. IXPIXP continue…continue… 1.Readiness Assessment: An appropriate development environment exist to support IXP. The team will be populated by the proper set of stakeholders. The organization has a distinct quality program and support continuous improvement. The organizational culture will support the new value of agile team. The border project community will be populated appropriately. 14 IXP
- 15. IXPIXP continue…continue… 2. Project Community: Classic XP suggests that the right people be used to populate the agile team to ensure success. When XP is to be applied for significant project in a large organization, the concept of the team should be clear in the community. The community contains legal staff, quality auditors, and many more. 15 IXP
- 16. 3. Project Chartering: The IXP team determine the future goals and objective of the project. They also examines the context of project to determine how it extends or replace the existing systems or process. 4. Test-driven Management: Test-driven management establishes a series of measurable destinations and then defines the mechanisms for determining whether or not these destinations have been reached. 16 IXPIXP continue…continue… IXP
- 17. IXPIXP continue…continue… 5. Retrospectives: An IXP team conducts a specialized technical review after a software increment is delivered. The intent of retrospective is to improve the IXP process. 6. Continuous Learning: Learning is the vital part of continuous process improvement, members of the XP team are encouraged to learn the new methods and techniques that can lead to a higher quality product. 17 IXP