Download
1 / 20
200 likes | 304 Views
Final Project. K15T2-Team 5 – POD Team. Team 5-K15T2. Members :. Hà Thùy An – Leader Nguyễn Văn Thọ Trần Thanh Hoàng Nguyễn Lê Phương Phú Lại Thanh Anh Tuấn Thôi Quyên Quyên . Presentation. 1. Introduction Software Development Process. 2. e Xtreme Programming . 3. 4.
E N D
Final Project K15T2-Team 5– POD Team
Team 5-K15T2 Members : HàThùy An – Leader NguyễnVănThọ TrầnThanhHoàng Nguyễn Lê Phương Phú Lại Thanh Anh Tuấn Thôi Quyên Quyên
Presentation 1 Introduction Software Development Process 2 eXtreme Programming 3 4
Presentation 1 Introduction Software Development Process 2 eXtreme Programming 3 4
XP Process 1 Introduction 2 Process 3 Roles and Responsibility 4 Practies Scope of use 5
Introduction • History: • Extreme Programming was created by Kent Beckduring his • work on the Chrysler Comprehensive Compensation System • payroll project. • Although extreme programming itself is relatively new, many of its practices have been around for some time; the methodology, after all, takes "best practices" to extreme levels. • XP is a software development process • XP is widely used in many medium or small sized companies. 4
Introduction • Factors to the success of XP • The customers associated with the development process, need attention to their needs. View them as members of development team. • Ability to respond flexibly and quickly to changes of customer requirements at any stage of the project. • Ability to offer a version of the software release quickly • when customers need it. 4
XP Process 1 Introduction 2 Process 3 Roles and Responsibility 4 Practies Scope of use 5
XP Process 1 Introduction 2 Process 3 Roles and Responsibility 4 Practies Scope of use 5
XP Process 1 Introduction 2 Process 3 Roles and Responsibility 4 Practies Scope of use 5
XP Process 1 Introduction 2 Process 3 Roles and Responsibility 4 Practies Scope of use 5
Scope of use • The projects usually ranged from 6 to 15 months. • XP is aimed for small and medium sized team • Historically, XP only works on teams of twelve or fewer people. One way to circumvent this limitation is to break up the project into smaller pieces and the team into smaller groups. It has been claimed that XP has been used successfully on teams of over a hundred developers. 4
