Slide 1

Slide 1 text

Dr. Javier Gonzalez-Sanchez [email protected] www.javiergs.info o ffi ce: 14 -227 CSC 307 Introduction to Software Engineering Lecture 03. Agile in Action

Slide 2

Slide 2 text

Previously

Slide 3

Slide 3 text

Strategies 3

Slide 4

Slide 4 text

Agile Manifesto

Slide 5

Slide 5 text

Agile in Action 5

Slide 6

Slide 6 text

Agile Manifesto 6 Our highest priority is to satisfy the customer Working software is the primary Agile Manifesto The 12 Principles of Agile We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: n Individuals and interactions n Working software n Customer collaboration n Responding to change over processes and tools over comprehensive documentation over contract negotiation over following a plan While there is value in the items on the right, we value the items on the left more.

Slide 7

Slide 7 text

Agile Manifesto 7 Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a devel- opment team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity – the art of maximizing the amount of work not done – is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. The 12 Principles of Agile n Responding to change over following a plan While there is value in the items on the right, we value the items on the left more.

Slide 8

Slide 8 text

Agile Manifesto 8 Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a devel- opment team is face-to-face conversation. Simplicity – the art of maximizing the amount of work not done – is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Kent Beck Mike Beedle Arie van Bennekum Alistair Cockburn Ward Cunningham Martin Fowler Robert C. Martin Steve Mellor Dave Thomas James Grenning Jim Highsmith Andrew Hunt Ron Jeffries Jon Kern Brian Marick Ken Schwaber Jeff Sutherland ©2001-2019 The Agile Manifesto Authors. This declaration may be freely copied in any form, but only in its entirety through this notice. THE MANIFESTO AUTHORS Advancing the principles of Agile Learn more at AgileAlliance.org

Slide 9

Slide 9 text

Product Backlog

Slide 10

Slide 10 text

Agile in Action 10

Slide 11

Slide 11 text

Product Backlog 11

Slide 12

Slide 12 text

Features or Functional Requirement a ) M a y st a te wh a t (reactions, behaviors, or services) the system should do. b) services the system should provide, c) how the system should react to p a rticul a r inputs, a nd d) how the system should behave in p a rticul a r situ a tions. 12

Slide 13

Slide 13 text

INVEST in good requirements • Independent – loosely coupled with one a nother • Negoti a ble – Stories a re wh a t a nd why, not how ( 99% ). • V a lu a ble – for the customer! • Estim a t a ble – E ff ort/Cost of design, build, a nd test. • Sm a ll (sized a ppropri a tely) • Test a ble – p a ss or f a il 13 - What it is - How it will be validated - How it will be triggered

Slide 14

Slide 14 text

INVEST Examples of Errors

Slide 15

Slide 15 text

Case 1 15

Slide 16

Slide 16 text

Case 2 16

Slide 17

Slide 17 text

Case 3 17

Slide 18

Slide 18 text

Case 4 18

Slide 19

Slide 19 text

INVEST In Action

Slide 20

Slide 20 text

Storyboarding 20 Who do What

Slide 21

Slide 21 text

Pac-man 21

Slide 22

Slide 22 text

Some Ideas. It is NOT a Complete List 22 MOVE EAT SHOW DETECT COLLISION MOVE/ HUNT SHOW SHOW/ CREATE SCORE HANDLING WINNER DETECTOR MOVE/ HUNT

Slide 23

Slide 23 text

Next 23 Product Backlog Sprint Backlog

Slide 24

Slide 24 text

Questions 24

Slide 25

Slide 25 text

Lab 03. Concepts

Slide 26

Slide 26 text

Homework Quiz 01

Slide 27

Slide 27 text

CSC 307 Introduction to Software Engineering Javier Gonzalez-Sanchez, Ph.D. [email protected] Spring 2025 Copyright. These slides can only be used as study material for the class CSC307 at Cal Poly. They cannot be distributed or used for another purpose.