Archive for category tools

Distributed Video Standup

Distributed Video StandupDistributed Teams need high bandwidth bidirectional communication to succeed, and the organization should provide these tools for collaboration. Luckily for us, Video Chat and Broadband are becoming more and more affordable so this is no longer an unrealistic goal.

With a decent Video Chat setup you can teleconference with teams around the world and pick up on body language that you’d otherwise miss using only the phone or chat.

So why is it that some Distributed Teams sit around a conference table while on Video Chat?

In short, they shouldn’t.

The Scrum Master needs to do everything in his power to ensure that the teams have an area to stand up for their Daily Scrum on Video Chat. Just because you are thousands of miles away, it does not mean that you can be lazy. If you lead your Daily Scrum sitting behind a desk using Video, it’ll be harder to keep team members from pontification. It’ll also become much more difficult to change the team’s behavior later on down the line.

So fellow Distributed Scrum Masters, please stand up when facilitating the Daily Scrum over Video. Encourage others to stand up if they are reluctant, and try your best to make those visual connections early. It’ll keep the team focused and you won’t start your day by dismissing one of the key aspects of your Scrum!

Tags:

I’ll Pet Him and Squeeze Him and Call Him Agile

IBMominable Maturity ModelI’ve read through Scott Ambler’s IBM blog about the Agile Process Maturity Model several times, and his points are lost on me. His over engineered solution is the antithesis of agile.

I do find some comfort that Kent Beck, Dave Thomas and others are not blindly adopting it either.

IBM seems to be posturing for an APMM, but why?

My perspective on this is that if IBM manages to convince people they need their think tank and software suite to implement agile, it would be another revenue stream to add to their collection. My fear is of the damage they’ll do in the process by strangling the very fundamentals of inspect and adapt.

Let us hope they lose focus and continue tilting at agile windmills.

Tags: , , ,

Cut the MS Project Cord Already

In a recent discussion over on the AgileSoftwareDevelopment.com Blog, I raised my concerns about the mind boggling need for expert MS Project skills in Agile/Scrum job postings. Laszlo Szalvay’s response was an enlightening one:

I think of the top 3 agile tools on the market (v1, scrumworks and rally) only ScrumWorks does not have a MS Project integration – namely because we don’t understand where the touch points would be…

So why are we still tethered to MS Project?

Here’s an exercise to help determine whether MS Project is truly being of value to you in your Agile project:

  1. Open your MS Project plan for a release that is already in progress.
  2. Identify the date in which you can deploy, to Production, working software.

I’ve yet to see a valid example of how true Agile/Scrum fits into MS Project. I realize there are MSF templates, and people cram it in there by either ignoring 99% of MS Project features or tasking “Development Resources” at 500%, but how is this helpful?

Does anyone have real world Agile implementations in which MS Project has provided value?

Tags: , , , , , ,