Planning stages complete and now the project is moving into it’s first sprint. There has been a bit of confusion over when we were supposed to assign the navigators for the tasks, it was my understanding that for Scrum the navigators pick their tasks at the Scrum Meeting and then take them into development from there.
Our timetable for a Monday is almost solid 9-5 and it left us with just enough time to work out who was doing what but seems to be OK so far.
I was concerned about how we are going to pull all of our source code together and although we will get Source Control and Continuous Integration for Sprint 2, it is going to require that bit of extra work and time moving everyone’s projects into source control. Given our busy timetable this may or may not be a problem. Time will tell.
As part of one of my 3rd year modules at Dundee University I am to be developing a piece of software in a group using Agile (3 cheers for that one!). This includes Scrum for project management, Test Driven Development, aspects of eXtreme Programming (including Pair Programming) and a couple of other goodies as well.
This is a welcome change to the traditional waterfall methodology which I do personally feel is tedious and have a number of issues with, however this is not the post to be arguing Agile over Waterfall. I will say however that I do have a habit for treating all of my projects as pieces of professional work which has advantages and disadvantages. I always strive for a high standard in my work and there are times where that becomes impractical or even impossible. Still, I feel the only way I can really improve on this is to work on group projects where time is limited and there are others involved in the development process. After all, one of the goals of this project is to learn.
