See www.agile2005.org. The due date for tutorials and workshops is March 1; for Experience reports, research papers, and the educators' symposium is March 15.
Call for Participation - Agile 2005
July 24-29, 2005. Marriott Hotel, Denver, Colorado, USA.
March 1: Submissions due for Tutorials and Workshops
March 15: Submissions due for Research Papers, Experience...
on Feb 6, 2005
Object Mentor's reviving their XP courses with "Agile/XP Immersion 2"; see http://www.objectmentor.com/Immersion2. March 21-25.
I attended the first one of the original series, and really enjoyed it.
on Feb 5, 2005
Reflecting on your process and how to improve it is an important part of agile methods.
Later this month, Diana Larsen is leading a class on retrospectives that may be of some interest:
"Project Retrospectives and Reviews: A Facilitator's Toolkit,"
January 24-25, 2005, at Oregon Graduate Institute;
She's also announcing another class in April...
on Jan 17, 2005
"Harold and the Purple Crayon" is a children's book where Harold uses his crayon to draw whatever he needs, and then it's real enough to use.
Sometimes you want to navigate to a class. One way is to go find it in the list of classes or out on disk. If you have a one-keystroke "jump to definition", one way is to just type the class name into the file you're in, and navigate on that. Yes, it may...
on Jan 6, 2005
William Pietri has posted a picture of his team room, at http://www.scissor.com/resources/teamroom/
I'm maintaining a gallery of team rooms, too, at http://xp123.com/xplor/room-gallery/index.shtml.
I'd love to have pictures of your team room or charts that you use.
on Dec 24, 2004
XP2005 has their call for participation out. They'll be at Sheffield University (UK), June 18-23, 2005.
See http://www.xp2005.org for more information.
Paper submissions: January 16, 2005
Acceptance notification for full papers: March 6, 2005
Submissions for tutorials, workshops, panels and activities, PhD
Symposium, and posters: March 1, 2005
Acceptance notification for...
on Dec 9, 2004
The Scrum gathering was a workshop gathered for a couple days in Denver, this past October. We worked in three groups: metrics, process, and facilitation. (Scrum is an agile process. I think of it as approximately the project management part of XP, though that's of course not fair to either one:)
I participated in the facilitation group. (The others were metrics and process.) We spent a lot of...
on Dec 4, 2004
Sven Gorts has introduced what he calls Refactoring Thumbnails. These are UML-like diagrams augmented with some flows, and used to summarize refactorings. (For example, the UML might have no words, but rather squiggles to represent identical text in two different classes.)
In addition to summarizing the transformation involved in simple refactorings, he uses these to show how large...
on Aug 9, 2004
Someone asked on the XP egroup about getting access to private methods for testing purposes. Others suggested a number of ways to get this effect, but it got me thinking about refactoring.
Refactoring is often thought of as a pure, safe transformation: convert a program into another program with the same semantics but a better design. From the standpoint of a refactoring tool, the "same...
on May 31, 2004
I recently had a chance to do some refactoring of some Visual Basic code. I hadn't worked with it in several years. In particular, I hadn't worked with the object support that's in VB.Net. It's very striking how much it's like C# with different keywords.
My task was to convert some code from using web services (which were too slow) to just straight object code. Several factors came together:...
on May 12, 2004
Test-Driven Development is a style that says "write a test for a small bit of functionality, write code to make it pass, refactor, and repeat."
In a way, the "test" part of the name is misleading. TDD does produce tests in the sense that they are written to verify whether something works, that an expected answer is defined in advance, and so on. But they're not tests...
on Apr 18, 2004
Test-driven development uses a tight cycle of "test, code, refactor" to develop software.
Tension and Release
I use the analogy of a stoplight: you start with a green light (all tests passing). Then you write a test; often you're referring to classes or methods that don't exist yet, and get a compiler error (yellow light). You fix this error by writing stubs, and when you run the test it fails...
on Mar 3, 2004
A traditional project plan has an ethos, "Plan the work, work the plan." The planning process will work out all the expected tasks, estimate them all, and assign workers to the tasks. This has several problems: the sheer mass of data makes it hard to see what's really important, the plan is vulnerable to changes in direction, and it's hard to keep up to date.
XP and Scrum (and some but not all...
on Feb 3, 2004
I'm reflecting on the most important tools I've been using this past year for my Java projects.
IntelliJ Idea - A fine IDE. My current default.
Eclipse - I've used it some, and found it a little clunkier than IntelliJ's. But I plan to move toward it more this coming year.
P4 - Perforce source control system. It's free for a single user, and does a nice job.
I've used two primary testing...
on Dec 25, 2003