JSL Program for Summer Fall 2000

Last Updated - July 31, 2000 - Go Back

Introduction

Projects that illustrate the proper use of Java, OO and best practices have been working well for us. Lighting Modeling has also worked well. In all of this we've been emphasizing process heavily, because it's so beneficial.

We learned a few things from the MVC Pattern Project we started in January 2000. It was useful, but has room for these improvements:

  1. We need to cover the use of Continuous Testing more.
  2. The project needs shorter process cycles, so that JSL members can see the big picture more frequently.
  3. We need to cover more patterns, not just mostly one.
  4. A long project can begin to bog down and lose its educational effectiveness.

Scratching my head for months on all this, I've come up with this program:

  1. Use Extreme Programming's leading edge best practices. We will also use others as necessary, but the focus will be XP.
  2. Start a project that builds a lightweight testing framework. Such a work product can be used by many of our members, especially if they delve into XP. Such a work product is small and well understood enough for our group.
  3. Introduce a wide variety of best practices in a formal way, by using a Configurable Process that incorporates practices from Mini Process, XP, Rational Unified Process and our experience. Jack is creating this.
  4. Use very short process iteration cycles to retain the big picture effect, one iteration per meeting.
  5. Use Pair Programming sessions on weekends or alternate Thursdays for the low level project work. This way all seriously dedicated JSL members can get to the heart of the matter, instead of just watching someone else.

One goal will be to design the testing tool so well that half our members use it. :-)

First Meeting

For the first meeting of the new program, August 3, we will:

  1. Take another VKSL quiz that covers the Configurable Process we will be using. This will be very educational.
  2. Start the project using process components Jack has preselected. The group will make final decisions, because it's their project.
  3. Complete the first Project Plan, which has the releases and first release iterations listed.
  4. Plan what needs to be done in the first Pair Programming sessions and schedule them. Also plan anything else needed not in the Project Plan, and add it. :-)

Those new to XP should read the article from Application Development Trends, July 2000, "Extreme Method Simplifies Development Puzzle". Thankfully this is online. Without at least this introduction to XP you will be lost. For some reason the online version omits the XP flowchart. Anyone have a url for the flowchart?

It's not clear yet whether we can do Pair Programming sessions at New Horizons. Therefore I'm scheduling the first session at my house on Saturday, August 5. We will have two hour sessions. These will be 10:00 - 12:00, 1:00 - 3:00 and 4:00 - 6:00. Folks can come to one or all, but my living room/office only handles about 5 people max. The group can schedule addtional and future sessions at the meeting or on the JSL list.

That should be enough info to get us started. It's gonna be an incredible year!!! ;-)