September 8, 2006
Categories:
Articles
On a few of the Agile lists, Paul Arrowood asked: “How does Agile address a conventional Risk Log? I wouldn’t call these ‘blocked items’ (aka issues). But more or less the [Scrum Master's?] watch list for things that could go awry (content not fabricated, new/unfamiliar technology, geographically dispersed team, interdependence with another project, etc).” I wrote an answer, and liked it well enough to put it here.
September 4, 2006
Categories:
Articles
It is my pleasure to offer the Agile community a new resource, an Agile Forum. I’m hoping it will be a brand-neutral, consultant-neutral place, open to and shared by everyone who is interested in advancing him- or herself in Agile, or in bringing Agile to the world. I’m inviting you to help make it a place you’d like to be.
Kate gives Dan Devlin, the company owner, an overview of Scrum.
Chet Hendrickson and I have offered to help the Scrum Alliance build a broad and growing base of information relating to Scrum / Agile, and to the many skills and practices that can help teams be successful. Our offer has…
Here’s the current code, and some commentary, for the “But We Need a Database” article. UPDATED: Comments on Python style.