Project Development, Day 4
Agile Software Development
Daily Stand-Up Meeting
We go around the room and report:
- What did you do yesterday?
- What do you plan to do today?
- What is in your way?
Everyone reported on the progress they made
No obstacles -- work in progress.
One concern I have is that pairs have stagnated over the
last couple of days. Let's look for opportunities to
mix up from now on.
When asked about the state of the code, the team seemed
pretty satisfied. During development, though, several
pairs expressed a desire to refactor a couple of classes,
or to have them refactored.
We followed the routine: Everyone pairs off, checks out a
clean copy of the project repository:
svn checkout https://student.cs.uni.edu/svn/810188-May10
... grabs a story, and writes a test.
Things of note:
- We are reaching the end of our first iteration. The only
unclaimed stories at this point are the two "close a
journal..." stories. They are important but also too big
(by my estimation) for one day. Let's try to wrap up open
stories today and early tomorrow.
- We will use any available time tomorrow to do a team code
review and refactoring session.
- Chris and Zack were looking at a potential refactoring
where the only duplicated code in two methods was a
particular being called in one expression. Ruby does
all us to pass procedures and method names as arguments.
This idea is new to many of you. Here is an
example of how to pass and call a method
- Homework. None.
- Reading. None!
- Programming. Keep learning Ruby, especially any language
features you encountered today but didn't understand well. You
may also work on the team project but only with a partner.
We will continue to do pair programming for all team code.
Eugene Wallingford .....
May 26, 2010