Project Planning, pre-Agile

Software Development, pre-Agile

The Agile Manifesto

http://agilemanifesto.org/

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.

Manifesto Principles

http://agilemanifesto.org/principles.html

Beware of Dark Agile

aka Faux Agile or Evil Agile

https://ronjeffries.com/articles/018-01ff/abandon-1/

this obeys Chaffee's Law of Titles: if a discipline's title includes a complimentary descriptor, then that descriptor does not apply

Agile Methodologies

Extreme Programming (XP)

Why is it called "extreme"? Mostly it's tongue-in-cheek, but beneath that is an honest experiment:

Instead of saying "we should really do X..."
(and then not)
...what if we do X all the time ?

(where X is testing, code review, incremental design, refactoring, ...)

XP values

XP Practices

https://en.wikipedia.org/wiki/Extreme_programming_practices

XP Practices: Fine scale feedback

XP Practices: Whole team

XP Practices: Shared understanding

XP Practices: Programmer welfare

XP Practices: Iterative development

Yesterday's Weather

The most efficient way to answer the question,

"What will today's weather be?"

is with the question,

"What was the weather yesterday?"

...sure it'll be wrong 20% of the time, but that's a much better rate than every other planning system

Continuous Improvement

First learn the rules

then obey the rules

then improve the rules

(then repeat)

Retrospectives

see cadence and retrospectives lessons

Next Lesson 

Outline

[menu]

/