We'll be finishing up pair programming for this sprint. I hope we can devote anywhere from 4-8 hours before Thursday's meeting. I would like to get full TCP communication implemented for the joining of a game instead of UDP to make the application more robust.
In terms of how the project is shaped by techniques used, it's very tough to gauge student work because (at least in our case) there aren't many set times where we can both meet to work. That being said, in larger groups or more structured projects, a time could be set aside once or twice a week to effectively get the group together and complete tasks.
Pair programming is working incredibly well for us and has made us the most effective. I think that for many student projects, using pair programming with small tasks is a more effective development technique. It makes sense because it combines student experience and allows two people to look at the same code and share ideas.
No comments:
Post a Comment