Skip to main content

First month of work done!

So! As I blogged about previously, I've begun working at a new company right after New Year's. I figured I'd get some thoughts out on how the first month has been.

Usually, when someone begins in a new job they're excited, nervous and above all very humble towards the existing practices that exist in the new workplace. Of course, I had these feelings, but being an agile fanatic, I was pretty sure that I would be able to find some improvement points. Here are some of the specific steps I took during my first weeks.

Step 0: Start writing a diary

I don't think an honest worker was ever harmed by being transparent in his work. A practice I've been doing ever since I started working is The Diary. Basically, just a personal wiki-page where you note down a few lines each day on what you're working on. Apart from being a good way to keep focus throughout the day and being a nice place to paste notes and code, it sends out a message: that you're interested in letting others know what you are working on. I'm going to be asking people what they're doing a lot, so being transparent in my own activities is a good start.

Step 1: Get Continuous Integration set up

One of my first reactions when I went to work on the code was a certain sense of claustrophobia. Here there were about twenty developers working on the same code base, and I really didn't have any feeling of who was committing what when. I first tried to get commit-mails set up, but due to some issues with commit-hooks in their Subversion setup, we couldn't get that working right away. So I turned to set up continuous integration with Hudson. My hope was that the CI changeset pages could work as a temporary commit-mail replacement, and since there already was a ViewSVN installation running, this worked out quite nicely.

From Drop Box
Note that the screen shot is not from our place, but from Sonatype's CI farm (tip o' the hat to Alf!).

Not long after that we were able to also get a nightly deployment of the build to the testing server, so now testers and designers can always experience the latest running on some local servers.

Note that getting this far in a couple of weeks would never had been possible in a traditional company (in my experience). The credit of this smooth setup belongs to some of their developers and admins, who put together the necessary scripts and server setup in record time. They actually had a continuous integration already, running the build each night as a cron-job. All I did was drop in the idea of using Hudson, and running the build on every commit.

Step 2: Do some agile preaching

I wanted to give the other developers some agile 101 very early, and luckily a slot opened up in our second weekly team meeting. I did this somewhat critical presentation on Scrum, so now when I accidentally throw terms like velocity and backlog around, they will have an idea of what I'm talking about.

Step 3: Whiteboards, whiteboards, whiteboards!

One of the things I did the first week was to get some large whiteboards ordered. I am of the opinion that you can never get enough whiteboards, and management agreed to spend a small fortune on this (again, something that wouldn't be easy in a traditional company). They finally arrived last week, and on Friday we finally got our team-lounge set up:

From Blogger-bilder
It's quite neat, I think. My plan so far is to use the far-left one for backlog stuff, the two horizontals for Sprint-charts, and the one on the right for anything else people would like to draw, be it architecture or obscenities ;)

It will be quite interesting to see how this works out. Some of the developers were speculating that the setup will be working for the first few weeks, and then fade away and people won't bother any more. Well, if people don't need this amount of communication in order to work efficiently, we will of course not force people to participate. I think everyone is better off if they spend 10 minutes of their day with the rest of their team on a daily standup in front of these whiteboards, but if people still don't like it after giving it an honest try, we'll remove the practice. After all, that's what being agile is all about.

Comments

  1. Anonymous1/2/09 11:14

    Boobs are still there - I told you they were worth it ;-)
    Anyway, great to have you on board - I'm looking forward to the things you bring to the company outside of the development team.

    ReplyDelete
  2. Anonymous24/3/09 18:10

    Exiting to read real life stories about how an agile guy can come into an organization and (maybe) turn it up-side-down. Keep it coming...

    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

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

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

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

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 --