Skip to main content

Scrumming the night away

Today I decided to do a small experiment.

I was scribbling up a tiny todo-list when I thought "Hey, why don't I do some rough estimation on how long these things will take?". This is what the list looked like at first (at 18:00):
  • Short bike trip - done at 18:30
  • Do some planning for Objectware-uni (training for the new folks) - done at 19:00
  • Fiddle with personal bank-stuff, bills, etc - done at 19:30
  • Write this blog entry - done at 20:00
  • Do some maintenance programming for a customer - done at 22:00
So off I went on my little bike trip, trying out those new bike-shoes that click on to the pedals (did I mention that I cycle to work and I think everybody should do the same?). Naturally, I bumped into my neighbour that I had to help out with moving a fence, and neighbour-chat with for a while. By the time I got back it was 19:20.

Darn. So I had to re-arrange my estimate:
  • Bike and neighbour - done at 19:20
  • Objectware-uni - done at 19:30 (would have to be quick!)
  • Bank business - 20:00
  • Blog - 20:30
  • Programming - 22:00 (1/2 hour less than originally estimated)
On I went to wiki down the uni-plans. Was I quick about it? No. It is very hard to rush stuff that involves thinking. In fact I was so enticed with the state of the wiki that I blew off half-an-hour cleaning and moving stuff around on the wiki. By the end, the time was 20:00. Re-estimating:
  • Bike and neighbour - 19:20
  • Objectware-uni - done at 19:30
  • Wiki-stuff - 20:00
  • Bank - 20:30
  • Blog - 21:00
  • Programming - 22:00 (1 hour less than originally estimated)
[In the moment of writing, it is 21:30, the deadline for my latest blog estimate, so I will have to hurry up now.]

The bank stuff went pretty quick (10 minutes). But then I felt hungry. I eat extremely slow, and I eat a lot (much to the annoyence of fellow lunchers and diners). I made dinner, ate (while reading TheServerSide discussions) and was ready to move on at 21:00.

New estimate:

  • Bike and neighbour - 19:20
  • Objectware-uni - done at 19:30
  • Wiki-stuff - 20:00
  • Bank - 20:30
  • Dinner - 21:00
  • Blog - 21:30
  • Programming - 22:00 (1,5 hours less than originally estimated)
And now my time for blogging is up. Spending a half hour programming doesn't seem very worthwhile, so I'll rather spend the rest of the evening relaxing and planning tomorrows bike-trip to work (lotsa logistics involved there).

Conclusions:
  • Keeping a plan like that made me work more efficiently
  • I quickly discovered things I wouldn't have time for
  • I always discover new tasks I'll have to squeeze into the program
  • I'm easily distracted by these new tasks (will have to work on that)
  • Food takes time and must be planned for (will have to work on that too)
  • Your plan will continously be disturbed by people who want to chat on MSN/IM
Overall, the best thing about Scrum is that it makes you more aware of what you and your team is doing, and what steps can be taken to improve your development process. The next best thing is that it allows you to break estimates and openly admit it without anyone yelling "Sue these guys!"..
Labels:

Comments

  1. Jon29/6/07 09:06

    You are as crazy and hard working as I know you to be.
    If anyone would put scrum into his personal space it would be you!
    Love your little experiments.

    ReplyDelete

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant
6 comments
Read more

Considerations for JavaScript in Modern (2013) Java/Maven Projects

Disclaimer: I'm a Java developer, not a JavaScript developer. This is just what I've picked up the last years plus a little research the last days. It's just a snapshot of my current knowledge and opinions on the day of writing, apt to change over the next weeks/months. We've gone all modern in our web applications, doing MVC on the client side with AngularJS or Ember , building single-page webapps with REST backends. But how are we managing the growing amount of JavaScript in our application? Yeoman 's logo (not necessarily the conclusion of this blog post) You ain't in Kansas anymore So far we've just been doing half-random stuff. We download some version of a library and throw it into our src/main/webapp/js/lib , or we use it from a CDN , which may be down or unreachable when we want to use the application.. Some times the JS is minified, other times it's not. Some times we name the file with version number, other times without. Some
Post a Comment
Read more

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o
Post a Comment
Read more

What I've Learned After a Month of Podcasting

So, it's been about a month since I launched   GitMinutes , and wow, it's been a fun ride. I have gotten a lot of feedback, and a lot more downloads/listeners than I had expected! Judging the numbers is hard, but a generous estimate is that somewhere around 2000-3000 have listened to the podcast, and about 500-1000 regularly download. Considering that only a percentage of my target audience actively listen to podcasts, these are some pretty good numbers. I've heard that 10% of the general population in the western world regularly listen to podcasts (probably a bit higher percentage among Git users), so I like to think I've reached a big chunk of the Git pros out there. GitMinutes has gathered 110 followers on Twitter, and 63, erm.. circlers on Google+, and it has received 117 +'es! And it's been flattr'ed twice :) Here are some of the things I learned during this last month: Conceptually.. Starting my own sandbox podcast for trying out everythin
Post a Comment
Read more

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --
12 comments
Read more