It’s quite common these days for organisations to allow external access to their intranets using an SSL VPN, but it can be a bit of a pain if you’re trying to follow a ‘normal’ intranet hyperlink (eg from an e-mail) – you have to paste the URL into a box on the VPN homepage and have it converted.
To make it easier I’ve created a bookmarklet to do the conversion. It may not work for all sites, as I’m only constructing the new URI based on a simple inspection of a couple of pages.
There’s an excellent article about the Toyota process on fastcompany.com. Most of the behaviours described are also desirable or necessary in teams or organisations trying to be[come] agile, but the key point is in the conclusion:
Ever since I started work, people have had big blue (or more recently black and red) books that they wrote stuff in. I’ve always called them lab books, but that seems to cause amusement to some people, presumably because I don’t work in a lab.
Some of the things that were written were notes from meetings, to do lists, or rough design notes. The most important ones though, the ones that you kept referring back to (if you could find them), were the little snippets of secret knowledge that everyone accumulates as they learn the intricacies of their particular job, whether it’s useful unix commands or instructions for using a particular build system.
Agile teams tend to favour whiteboards for instant collaboration when discussing design etc, but if you’re working in a pair you might not always want to keep walking over to one on the wall. The answer? A4 whiteboards!
They only cost a couple of pounds each (including a pen), and at the risk of attracting ‘XP isn’t for grown-ups’ comments, the best place to buy these seems to be primary school suppliers – for example Class Ideas or EasyTeach. At that price, you may as well have two or three each.
[tags]agile, tools[/tags]
Of late, I only carry cards in my pocket to write on, and that’s an entirely different thing. In particular, there’s no continuity. That can be a good thing, or a bad thing.
The big advantage to the cards is that I read somewhere, many years ago, that you can recognize important people by the fact that they don’t carry anything. They don’t need to carry anything, because whatever they need, they just are, and because they have other people to carry their things for them. So I stopped carrying things, in hopes of being mistaken for someone of consequence. You have to start somewhere.
I too have taken lately to carrying a bunch of index cards around in my back pocket for occasional scribbling, and I rarely take a notebook to those meetings I fail to avoid (on the basis that someone’s bound to hand out some kind of printed material that I can write on).
Of course, the main difference is that Ron is ‘someone of consequence’!
Actually number one is quite a big one, so perhaps I’ll stop there.
When people talk about large organisations making major changes to their core processes or values, sooner or later someone will compare the process to steering a supertanker – if you turn the wheel now, you’ll have travelled quite a distance before there’s any noticable change in course.
This analogy falls down when you’re trying to introduce agile software development. If you want to be agile, a supertanker just won’t do the job any more. It’s time for small teams to jump into the lifeboats and set off in their own directions, leaving the heavy old legacy systems to continue their progress on their predictable course. The lifeboats are far nimbler and can react much quicker to changing conditions. Of course (and that sound you hear is the analogy stretching close to breaking point) they would still be in radio contact with the captain, so you wouldn’t lose sight of the overall strategy.
Personally, the lifeboat I was in until Christmas now has a new crew and is sailing under a flag of convenience out of Mumbai. I have no idea what I’ll be doing in the new year, or whether we’ll remain as a team, but at the moment it feels very much like we’re being dumped back on the supertanker, and while we’ve been off charting new territories, the ship’s only turned by a degree or two.
[tags]agile, enterprise[/tags]
Now that rspec runs under jruby, and with a few hours to spare, I thought I’d have a play.
[Update:] I’ve simplified the import of java.util.Date following a suggestion in a comment (from Charles Oliver Nutter, no less!). I also noticed that I wasn’t using rspec’s setup properly (or at all), so I’ve tweaked the samples a little. I haven’t got the code here to try out, so there may be typos.
Jeremy Stell-Smith’s says, in a post about Stand ups as Huddles:
I’m actually not a big fan of the traditional yesterday – today – issues format. I find that too often it becomes a status meeting – this is what I did yesterday, doing more of the same today, and no issues.
We’ve found the same thing, and tried (with limited success) to apply some of the traditional retrospective questions to the daily stand-up, so What did you do yesterday? should include What did you learn yesterday, and What’s holding you up? should include What’s still puzzling you?.
The other important thing is to jot down things you think of during the day that you want to mention at the stand-up, otherwise (particularly if you have a memory like mine) you end up going round the circle and waiting while everyone says “I’m sure I did something yesterday… let me think…”.
[tags]agile, stand-ups[/tags]
A couple of other neat features that have made me glad I switched:
You can mark individual items in your subscribed feeds as ‘shared’, and they become available on a public page. Like-minded people can then subscribe to your shared items feed, instead of you having to keep forwarding them links. I’ve added a link to my shared items over there on the left.
Like many of you (I’m pretending here that people actually read this: humour me!), I keep a bookmark folder where I drop things that look interesting but that I don’t have time to read straight away. The problem is that it doesn’t help much when I see something at work that I want to read properly at home (or vice versa). Since most of them come from RSS feeds, all I need to do is click the star next to the item in Google reader, and it goes into a list that I can come back to later, rather than trying to remember which feed it was from. I guess many standalone RSS readers have a similar feature, but it comes into its own when you can access the list from anywhere.
[tags]Google reader, RSS[/tags]