scrum

"practical advice for avoiding [delivering broken software with Scrum] – whether you’re an Organizer or you’re an Activist Developer"

The key problem identified is that incentive to abandon code quality to meet time/budget and feature goals.

The solution is to, first, not allow tests, in code, automated, or human, and other issues of code quality to be cut off from the features that are being built. Hide the time in the task estimates if absolutely necessary.

But also:

Agile BoF

Tom McCracken:
Rarely do things just break.

Development

"How do you structure the retainer agreement?"
So many hours per month. So long as we propose good solutions and execute them well,

can-ban - very lightweight agile, that works well for

"Company of only 8 people, i'm the main developer. Does scrum work this small?"

We've struggled to get scrum to work on a $20,000 project [that is small], just not enough cycles.

Hard to get it to scale below $60,000 projects.