Archive for May, 2010

Don’t Tell Anyone I Switched to a Mac for my Agile Planning

May 28th, 2010 by brad hart

How did it come to this?  I still can’t believe it myself.  I started as an Intel + MS-DOS guy (was I the only one that was thrilled when DOS 6.22 was released??).  My first deviation from the Intel / Microsoft platform was Solaris, strictly via the shell.  I refused to deal with the Solaris windowing environment.  No fancy frills for me, just give me the CLI and leave me alone. Windows came along and it opened a whole new way of working with computers for me.  Then came Cyrix & AMD and I haven’t owned in Intel processor since.  Finally, Linux hit the world by storm, and I found my new favorite platform (Linux on a PC).

The one constant in all of this change? No Mac…never, ever, ever. I refused. I didn’t like their products, didn’t like their messaging, and couldn’t stand their image. I always said: “Macs are for art students and kindergarteners, PCs are for doing real work”.  Yet despite all the goodness I heard regarding OS/X, I refused to believe Macs were finally running a real OS. Plus, every time I walk by an Apple store and see the “genius bar,” I can’t stop laughing.

As the Product Owner at AccuRev, the problem I began hearing more and more from customers I really respect was they love developing software on their Macs, but their AccuRev/Mac experience could use some improvement.  Given that AccuRev is a leading provider and integrator of Agile Software Development Tools, I put my Agile Product Owner hat on and visited some of our Mac users to see if we needed to do some agile planning and shape up the backlog a bit to support the Mac better.

All I can say is I was definitely blown away watching the Mac experience in action. These brilliant engineers were showing me areas where both the AccuRev GUI and our AccuBridge for Eclipse and IntelliJ integrations can be improved upon as part of the natural Mac UI.   In my next agile planning session, I prioritized Snow Leopard support right to the top of the backlog. (Which by the way is so great about agile; being able to adjust or course correct your plans after each sprint is powerful, thus allowing you to react to your customers so much better.)

I had to make a tough decision: either take our customers’ word for it, or experience it myself. I figured what better way to see what needed fixing than to have a Mac affect my daily use. So I took the plunge and bought a MacBook.

Testing Agile Planning on the Mac

So I am sitting here as I type this with 2 Chrome windows open (23 tabs total), Firefox open (11 tabs), Safari open (5 tabs), Eclipse, AccuRev, 5 bash terminals running, simultaneously running Windows 7 and Ubuntu VMs (via VirtualBox), 3 Word docs and 4 Excel spreadsheets open, and 6 Finder windows. The MacBook is basically laughing at me as if to say “keep it coming”…  I am still in disbelief.

New Picture Dont Tell Anyone I Switched to a Mac for my Agile Planning Here is AccuRev’s WebUI running inside of Eclipse on Mac with AccuRev’s Eclipse integration enabled. I can do all my agile planning, process management and development right from within Eclipse!

So that’s it…I’m a Mac fan now. Don’t expect me to be growing a ponytail anytime soon though.

Rational ClearCase Problems: Going Agile

May 25th, 2010 by AccuRev

Is this rational?

Visibility in an Agile Environment

May 13th, 2010 by clucca

Amazing fact: The lookout crews for the RMS Titanic were without binoculars. Due to a last minute change in personnel, the team member who was in charge of spyglasses, binoculars and other optical equipment was not on board the ship, and all of this equipment was unfortunately locked away, crew members unaware of the location.

We all know the rest of the story; by the time that the lookout crew saw the iceberg, the opportunity to change course already passed.  There was not enough time for the crew to respond to the problem and correct it. They had no visibility (literally).

Agile is about adaptation. It’s not about sticking to the plan; it’s about exposing and responding to change in your development cycle. But how can you respond to problems if you don’t know what they are?

Our last blog post was about “inspecting and adapting”, and I don’t want to get these 2 success factors confused. The real point that I’m trying to get across is that visibility in an Agile environment allows your teams the ability to inspect and adapt to impediments.

Why is Visibility in an Agile Environment Important?

Information in an Agile environment is viewed more often, and scrum teams  need to see this information on a daily basis in order to change course if necessary. Visibility in an Agile environment allows teams to use information in their stand-ups, sprint reviews, demos and retrospectives.j0336214 Visibility in an Agile Environment

Visibility also needs to happen on a large scale, and everyone needs to be involved. Just think, if we gave only one pair of binoculars to the entire look-out team on the Titanic, it would have been much less effective than if each team was equipped with the proper visibility gear. Everyone needs to be aware of the problem in order to change courses.

But here’s the real trick. Centralize this information, make it visible to everyone and all your tools.  If you do this, you can integrate with all of your processes. This guarantees the information in the tools is correct. For example, if you have an integration in your SCM tool to your project management tool, you can see what changes correlate to what iteration, guaranteed. You can also integrate your build, test and deploy tools to provide tractability on all levels of the stack. Centralization also provides a single place where everyone can see what’s happening. Scattering the information against multiple tools that aren’t “Agile aware” will only confuse the process.

So having a global visibility can help re-route a ship that’s traveling on a disastrous course. It can also help your development teams change course when they need to.

Wouldn’t it be beneficial to get your whole team some binoculars?