How I became a certified Scrum-master in two days...

I'll asume that most readers are somewhat familiar with Agile methodologies. Scrum is one of these, as is eXtreme Programming and Crystal. It is a framework that avoids taking too much control over how you do projects, but adding a few core ideas and rituals that could be of use to any kind organization. If you aren't familiar with Scrum or any other agile method, read up on it now. Here's enough to get you started :

Scrum Alliance's intro

Now, for us that have the privilege of working in a company that can see the long-term benefits of spending a decent fortune sending you off on a two-day course, we kickstarted our Scrum-ways by doing Jens Østergaard's course for becoming certified Scrum-masters (cool title, eh?). It is not an expensive course by itself, but it costs the company alot to take us all of our projects for a whole day (the course was friday and saturday).

Before the course, I honestly figured I knew enough of Scrum to do fine without it, but it would be nice to have the title, and maybe widen horizons a bit.

I'm not going to go through the content of the course, but I can tell you that Jens is an excellent presenter, I learned some Scrum basics I've missed along the way (especially about project roles). I learned a few wise steps to take for introducing Scrum into a project or organization.

I would definitely recommend the course for people who want an introduction to Scrum, and also people who are going to "sell Scrum", meaning getting their customers to accept it instead of horrible traditional project plans. You can read/practice yourself up to the same knowledge (after all, Scrum principles are easy, and mostly it is about using common sense), but this course was a nice compressed version for those who do not have time/resources to educate themselves into Scrummers.

Funny how many of those Agile web-sites seem to be powered by Rails Studio. Pretty clear that the Ruby on Rails community seems fairly connected to the Scrum one. Noticed all those nice urls ;)

One of those little funny coincidences of life; this is a graph over last weeks visits (RSS hits excluded). Look familiar?

But honestly, I can't write any more. Still recovering from yesterday's St. Patrick's Day celebrations.

Comments

Git-SVN Mirror without the annoying update-ref

This post is part of a series on Git and Subversion . To see all the related posts, screencasts and other resources, please click here . So no sooner than I had done my git-svn presentation at JavaZone , I got word of a slightly different Git-SVN mirror setup that makes it a bit easier to work with: In short, my old recipe includes an annoying git update-ref step to keep the git-svn remote reference up to date with the central bare git repo. This new recipe avoids this, so we can simply use git svn dcommit directly. So, longer version, with the details. My original recipe is laid out in five steps: Clone a fresh Git repo from Subversion. This will be our fetching repo. Set up a bare repo. Configure pushing from the fetching repo to bare repo In the shoes of a developer, clone the repo Set up an SVN remote in the developer's repo In the new approach, we redefine those last two steps: (See the original post for how to do the fir...

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

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be...

Git-SVN Mirror for multiple branches

This post is part of a series on Git and Subversion . To see all the related posts, screencasts and other resources, please click here . This extends the posts where I explained how to set up a git-svn mirror for a single directory. NOTE: If you just want to use Git against a SVN repo on your own, stop reading ,now, and stick to the git-svn basics. However, if you want a setup where you can share a Git repository with colleagues and friends while still interfacing with Subversion, keep reading. I'll show how to set up a git-svn mirror for a standard Subversion project with trunk , branches and tags . It's a bit like the single directory mirror, but in order to keep all branches in sync, it's a bit more fiddling. The good part is that this setup enables us to cherry-pick commits from one branch to the other. This is slightly smoother than using svn merge . First of all, let's repeat how our Subversion and Git-repositories look physically (roughly the sa...

Git-SVN mirror product: SubGit

Just a quick mention for you people who can't be bothered with my somewhat intricate Git-SVN mirror setup , there now is a now is a solution packed into a product: SubGit . I tried it out on a little local SVN repo recently, and it worked just fine. It delivered pretty much perfect two-way syncing/bi-directional mirror (which I've earlier deemed to be very impractical with git-svn ). The bad parts are: It's new (use at your own risk, in other words: DO NOT install it in your main-line subversion repo used by a 100 devs). It's closed source, so you're at the mercy of the SubGit devs for fixing any feature that you need in your special repository. It requires instrumentation on the Subversion repository installation. If the repository is beyond your control (hosted externally, or by some separate department), you're stuck with my old setup . The good parts: Super-sweet functionality! I mean, bi-directional Git/SVN is highly sought after. Seems to...