Re: [xmlWiki-developers] Oct 8 Meeting Minutes/Other Items
Brought to you by:
elhugo
From: CS327 TA <cs3...@cs...> - 2001-10-11 01:25:29
|
To this list: > your code > some UML diagrams explaining it > meeting logs > programming logs > some personal reflections on what worked and what didn't I would also add: "User stories". > If you haven't seen it yet, it's probably worthwhile to check out the > newly posted http://wiki.cs.uiuc.edu/SEcourse/XP+Best+Practices , > where the course staff gives advice on what XP project groups should > do. We should perhaps think about how to implement some of these > ideas in an geographically distributed manner. PAIR PROGRAMMING For > this last HW (3&4) Chris Heistad and I worked together. We had great > success with Microsoft Netmeeting as a tool for "Pair Diagramming", > and it seems that it would probably work just as well for pair > programming. I think that Pair Programming is at the heart of XP, and > our experience with NetMeeting seems to me a strong indication that > Pair Programming could work just as well for our group as it could for > any other. (Chris, please voice your agreement or disagreement. :) ) > TEAM-BUILDING AND HWs I have an idea for people to consider before our > next meeting. Chris and I pretty well "bonded" as teammates during > HW3/4. I understand that other people in our group have paired off > together to work on HWs as well. Who would be up for switching around > partners if the course staff indicates that the next HW is able to be > done in groups as well? Disadvantage: This would mean that one > person always has to do the HW alone, since there's 7 of us, but > perhaps the course staff will broaden the number of potential people > per group to 3. Advantage: Enhanced team cohesion. Can you use the voice-chat feature of NetMeeting while sharing a workspace? Or is that too much of a bandwidth hog? If that doesn't work, and you've got spare minutes in your long-distance plan, I would consider calling each other up while pair-programming - the dialog that occurs *while* you navigate the code is the essence of it. A chat box on the side just isn't the same! - Andrew. |