CHAPTER 3 ā AGILE SOFTWARE
DEVELOPMENT
CHAPTER 3 AGILE SOFTWARE DEVELOPMENT 1
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
AGILE METHODOLOGIES, DEVELOPMENT, SCALING AGILE METHODS, Slides of Software Engineering
Agile software development, including agile methods, agile development techniques, and agile project management. It compares plan-driven and agile development and covers topics such as extreme programming practices, test-first development, customer involvement, and pair programming. The document also introduces Scrum, an agile method that focuses on managing iterative development. It provides examples of task cards and discusses the importance of refactoring in agile development.
Typology: Slides
2021/2022
1 / 66
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download AGILE METHODOLOGIES, DEVELOPMENT, SCALING AGILE METHODS and more Slides Software Engineering in PDF only on Docsity!
CHAPTER 3 ā AGILE SOFTWARE
DEVELOPMENT
TOPICS COVERED
ļ” Agile methods
ļ” Agile development techniques
ļ” Agile project management
ļ” Scaling agile methods
AGILE DEVELOPMENT
ļ” Program specification, design and implementation are inter-
leaved
ļ” The system is developed as a series of versions or increments
with stakeholders involved in version specification and
evaluation
ļ” Frequent delivery of new versions for evaluation
ļ” Extensive tool support (e.g. automated testing tools) used to
support development.
ļ” Minimal documentation ā focus on working code
PLAN-DRIVEN AND AGILE DEVELOPMENT
AGILE METHODS
AGILE METHODS
AGILE METHODS
ļ” (^) Dissatisfaction with the overheads involved in software design methods of the 1980s and 1990s led to the creation of agile methods. These methods: ļ” (^) Focus on the code rather than the design ļ” (^) Are based on an iterative approach to software development ļ” (^) Are intended to deliver working software quickly and evolve this quickly to meet changing requirements. ļ” (^) The aim of agile methods is to reduce overheads in the software process (e.g. by limiting documentation) and to be able to respond quickly to changing requirements without excessive rework.
THE PRINCIPLES OF AGILE METHODS
Principle Description Customer involvement Customers should be closely involved throughout the development process. Their role is provide and prioritize new system requirements and to evaluate the iterations of the system. Incremental delivery The software is developed in increments with the customer specifying the requirements to be included in each increment. People not process The skills of the development team should be recognized and exploited. Team members should be left to develop their own ways of working without prescriptive processes. Embrace change Expect the system requirements to change and so design the system to accommodate these changes. Maintain simplicity Focus on simplicity in both the software being developed and in the development process. Wherever possible, actively work to eliminate complexity from the system.
AGILE METHOD APPLICABILITY
ļ” Product development where a software company is developing a
small or medium-sized product for sale.
ļ” (^) Virtually all software products and apps are now developed using an agile approach
ļ” Custom system development within an organization, where
there is a clear commitment from the customer to become
involved in the development process and where there are few
external rules and regulations that affect the software.
EXTREME PROGRAMMING
ļ” A very influential agile method, developed in the late 1990s, that
introduced a range of agile development techniques.
ļ” Extreme Programming (XP) takes an āextremeā approach to
iterative development.
ļ” (^) New versions may be built several times per day; ļ” (^) Increments are delivered to customers every 2 weeks; ļ” (^) All tests must be run for every build and the build is only accepted if tests run successfully.
THE EXTREME PROGRAMMING RELEASE
CYCLE
EXTREME PROGRAMMING PRACTICES (B)
CHAPTER 3 AGILE SOFTWARE DEVELOPMENT 16 Pair programming Developers work in pairs, checking each otherās work and providing the support to always do a good job. Collective ownership The pairs of developers work on all areas of the system, so that no islands of expertise develop and all the developers take responsibility for all of the code. Anyone can change anything. Continuous integration As soon as the work on a task is complete, it is integrated into the whole system. After any such integration, all the unit tests in the system must pass. Sustainable pace Large amounts of overtime are not considered acceptable as the net effect is often to reduce code quality and medium term productivity On-site customer A representative of the end-user of the system (the customer) should be available full time for the use of the XP team. In an extreme programming process, the customer is a member of the development team and is responsible for bringing system requirements to the team for implementation.
XP AND AGILE PRINCIPLES
ļ” (^) Incremental development is supported through small, frequent system releases. ļ” (^) Customer involvement means full-time customer engagement with the team. ļ” (^) People not process through pair programming, collective ownership and a process that avoids long working hours. ļ” (^) Change supported through regular system releases. ļ” (^) Maintaining simplicity through constant refactoring of code. CHAPTER 3 AGILE SOFTWARE DEVELOPMENT 17