Project log

Story Points (SP) are relative to the complexity of implementing a working copy of the Boids project from the Object Oriented Programming and Design course. The project is normalised to 10 SPs.

Sprint #1

Estimated team velocity: 50 SP SCRUM Master: Ronni Tester/Reviewer: ? Developer(s): ??

Sprint Planning meeting

Minute

The meeting was held at Praqma in Allerød from 9:00 till 12:00. The first part was to get an overall scope of the project, next we found items for the backlog in cooperation with Lars and Christian. For approximately 1 1/2 hours we divided the items into tasks with SP estimates and presented them. The tasks where not accepted at first as they needed details.

Lesson learned

We need to be more specific about the outcome of each task. Especially in the start we have a lot of research tasks and we need to make reports or something tangible such that the product owner will actually give us permission to do the tasks - especially if we believe they are must or should haves. e.g. A research task should have a goal stating explicitly what the product will be and why it should be made.

Sprint evaluation

Agenda

1. Discussion of the sprint, where goals met? What went good, what went bad?
2. Preparation for sprint demo, is there anything we need to finish?
3. Preparation for next sprint
4. Picking the new SCRUM master and test
5. Calculating velocity
6. Etc.
7. Etc.

Minute

All must have goals where met, although we didn't use as much time on research as estimated. This time however was focused on other learning goals such as setting up jenkins and getting to know the architecture. We didn't have a tester role, but due to the large amount of research it didn't make sense yet to have a tester this sprint. We will have one for the next sprint! We would like to have a calendar for the team. It will be a job for the next scrum master to create this and maintain it. Working hours where fine, and the workload too. All in all our effort pretty good matches the calculated velocity. Sprint master for next sprint is Andreas. Ronni is tester and analyzer. Andreas will try to optimise the structure of the wiki pages. Reports are kept on the wiki unless Praqma wish for printable documents. Esben is responsible for copying unresolved tasks from sprint #1 to the backlog.

Sprint #2 preparation

Completed SP: 35 Sprint #1 velocity: 35/50 = 0.7 Next sprint theoretical capacity: 83 Next sprint actual capacity: 58

Lessons learned from this sprint

• Smaller tasks as we have many big tasks where some of them where half done but they have no obvious result as it is right now.
• Research tasks are a bad idea, but are hard to avoid. Try making it a subgoal of an implementation goal
• The perfect size of the sprint log is up for discussion. And is an interesting topic for the report. (remember it!)