Archive for June, 2009
Daily Scrum 25 – 27.6.2009
Work done
- Results Chapter 3 article:
- Proof-read the article
- Made corrections and revisions
- Inserted the Scrum diagram
- Submitted the article
Issues
- None at the moment
Will work next on
- Integrating the article texts to the dissertation manuscript
Estimated Sprint work left: 2.0
Add comment June 27, 2009
Daily Scrum 24 – 26.6.2009
Work done
- Produced new version of the dissertation manuscript
- Written the remaining parts of the res3 article:
- completed the introduction
- lit. review: experimental process control
- results – chapter beginnings
Issues
- None at the moment
Will work next on
- Proof-read the article
- Make corrections and revisions
- Insert the Scrum diagram
- Submit the article
Estimated Sprint work left: 2.5
Add comment June 26, 2009
Daily Scrum 23 – 19.6.2009
Work done
- Produced new version of the dissertation manuscript
- Written parts of the res3 article:
- abstract
- lit. review: defined process control
- results – PC and game design activities
- conclusions
Issues
- None at the moment
Will work next on
- Converting the article to tex
- Writing the article: lit. review: experimental process control
- Digging up the citations from se and process control references
Estimated Sprint work left: 4.3
Add comment June 19, 2009
Sprint Review and Planning
The previous Sprint had many difficulties. Most of them were related to the tight schedule and my reluctancy to trust Scrum practices and instead to try to push the envelope in order to make all my deadlines deespite the fact that my current velocity suggested that this was probably too much.
In the end I got the most important stuff done in time, thanks to the MindTrek deadline being moved one week further. But this was at the expense of the other article that I was writing. I had made too optimistic plans on what I could do on that article at the same time the other article deadline loomed.
These scheduling differences were magnified by my “absences” related to being sick. I guess it is only natural that a one-man Scrum cannot maintain a stable velocity due to real-life related random stuff — hence the optimum team size for Scrum.
I also noted that I have reached top velocity when not pressurized by too much work or deadlines. It is difficult to just work as quickly as I can when having the manager role also — but I’ll try to be more indifferent about the deadlines in the future. This does not mean I won’t try to make them — I’ll instead just plan my Sprints according to them and let the Sprint structure (reaching the goal and modifying the Sprint backlog according to velocity) to handle reaching the goals instead of panic and crunch working.
But, on to the next sprint: I’ll make this one a bit longer as I’m having my vacation on July (so less work days then, one’s got to rest for a change). The Sprint deadline is the end of my vacation on July 26th and the Sprint goal is to finish the second article and incorporate the text of the two articles to the result chapters of my dissertation manuscript.
Add comment June 18, 2009
Daily Scrum 22 – 18.6.2009
Work done
- Sprint review, Sprint planning
Issues
- None at the moment
Will work next on
- Produce new version of the dissertation manuscript
- Write res3 article:
- abstract
- results – PC and game design activities
- Start on conclusions
- Convert the article to tex
Estimated Sprint work left: 5.3
Add comment June 18, 2009
Daily Scrum 21 – 12.6.2009
Added this after the fact…
Work done
- wrote most of the result chapter of the res3 article.
- wrote case project descriptions.
- that effectively finished the first version of the res3 article.
- Sprint ends.
Issues
- No audience for the res3 article (Digra abstract was declined)
Will work next on
- Sprint review, start new Sprint.
Estimated Sprint work left: 1.7 (not crucial, back to project backlog)
Add comment June 18, 2009
Daily Scrum 20 – 7.6.2009
Work done
- submitted the res2 article
- started working on the case project descriptions
- looked for other places to submit the res3 article
Issues
- No audience for the res3 article (Digra abstract was declined)
Will work next on
- finish the first version of res 3 article
Estimated Sprint work left: 2.7
Add comment June 12, 2009
Daily Scrum 19 – 31.05.2009
Crazy times here, first I was sick and then flooded up with work and tooth-ache (auch!) so I haven’t been able to update. But, on to the DS:
Work done
- did not have as much time as estimate due to illness
- made a shortened version of the res2 article
- did not submit the article due to deadline extension
- changed the Sprint deadline to 15.6. (two week sprint is bogus)
Issues
- No audience for the res2 article (Digra abstract was declined)
Will work next on
- submit the res2 article
- make first version of res 3 article
- case project descriptions
- process control in case projects
Estimated Sprint work left: 4.5
Add comment June 5, 2009
