Agile Methods About Last Lecture Clarification on process - - PowerPoint PPT Presentation

▶

Dec 03, 2022 278 likes •461 views

CPSC 310 Software Engineering Lecture 3 Agile Methods About Last Lecture Clarification on process selection: People (so developer) are reluctant to change. Introducing a new process into a company is expensive and time consuming.

SLIDE 1

CPSC 310 – Software Engineering

Lecture 3

Agile Methods

SLIDE 2

About Last Lecture

Clarification on process selection:

People (so developer) are reluctant to change.
Introducing a new process into a company is

expensive and time consuming.

Finally it's all about context

SLIDE 3

Where It All “Began”

Agile Man anifesto to (2001)

http://agilemanifesto.org/

SLIDE 4

Individuals and in interactions

ver processes and tools

SLIDE 5

Working software

ver comprehensive documentation

SLIDE 6

Customer coll llaboratio ion

ver contract negotiation

SLIDE 7

Respondin ing to change

ver following a plan

SLIDE 8

Class Activity: Agile Methods

Advantages ? Disadvantages ?

SLIDE 9

Agile Software Development Advantages

Lower risk
Close customer involvement
Better visibility
Compliant with changes

SLIDE 10

Agile Software Development Disadvantages

Harder to enforce with inexperienced programmers
Close customer involvement (again!)
Hard to estimate completion schedule
Increases the risk of feature creep
Can be inefficient

SLIDE 11

The Agile Landscape

More Prescriptive More Adaptive

RUP (120+) XP (13) SCRUM (9) KANBAN (3) NONE (0)

SLIDE 12

Do not develop an attachment to any one weapon or any

ne school of

fighting.

Miyamoto Musashi

17th century Samurai

SLIDE 13

Extreme programming (XP)

Kent Beck mid 90s

Whole Team Planning Game Customer Tests Small Releases Coding Standard Sustainable Pace Continuous Integration Collective Ownership Metaphor TDD Simple Design Refactoring Pair Programming http://www.extremeprogramming.org/rules.html

SLIDE 14

T est-Driven Development (TDD)

est cases are written first

– Cover new functionality or improvement

Then the necessary function is

implemented

Code is “complete” when all tests pass
Refactor before adding feature if design

could be better

SLIDE 15

Class Activity: TDD