chap3 - Chapter 3 Agile Software Development Chapter 3...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
Chapter 3 Agile Software Development Slide 1 Chapter 3 Agile Software Development
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Chapter 3 Agile Software Development Slide 2 Topics covered Rapid Software Development Plan-driven and agile development Extreme programming Agile project management Scaling agile methods
Background image of page 2
Chapter 3 Agile Software Development Slide 3 Rapid software development Rapid development and delivery is often the most critical requirement for software systems. Quickly changing global markets mean businesses must be responsive to new opportunities and competition. Software has to evolve quickly to reflect changing business needs. Being responsive to changing environments = coping with unstable requirements.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Chapter 3 Agile Software Development Slide 4 Characteristics of rapid development processes Processes of specification, design and implementation are interleaved. System is developed as a series of versions with stakeholders involved in version evaluation. User interfaces are often developed using an Interactive Development System (IDE) and graphical toolsets.
Background image of page 4
Chapter 3 Agile Software Development Slide 5 Agile Methods
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Chapter 3 Agile Software Development Slide 6 Agile methods background and aim Dissatisfaction with overhead of waterfall methods of the 1980s and 1990s led to creation of agile methods. Focus is on code rather than the design. Based on iterative development . Intended to deliver working software quickly which can evolve quickly to meet changing requirements. (cont’d )
Background image of page 6
Chapter 3 Agile Software Development Slide 7 Agile methods background and aim The aim of agile methods is to: Reduce overhead in the software process (e.g., by limiting documentation), and Allow rapid response to changing requirements without excessive rework. See: www.agilealliance.org
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Chapter 3 Agile Software Development Slide 8 “Manifesto for Agile Software Developers” We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
Background image of page 8
Chapter 3 Agile Software Development Slide 9 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.
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 56

chap3 - Chapter 3 Agile Software Development Chapter 3...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online