What is the best Agile Product Management tool?

Here’s a question that’s been bugging me, that I’d like to put out there: what tool(s) would you recommend for Agile Product Management — as opposed to Agile Project Management. Here’s the challenges that I’d like to address:

1. There are many project management tools out there, but as far as I can tell, they are “market ignorant” — they don’t help a product manager (as opposed to project manager) define the scope of a release/iteration, or prioritization of a backlog, based on various market factors. They take scope and prioritization as a given and don’t help the inbound product manager. They don’t help a product manager synthesize all the market inputs to make informed decisions about feature prioritization. In this group I’d include Jira, Bugzilla, TargetProcess, Rally, and VersionOne.
2. As far as I can tell, agile project management tools are “sales ignorant”: they don’t enable a sales engineer to understand which features have been built, and what sales tools are available to enable a SE to sell that feature, and don’t automate outbound product management activities. There is no simple “Roadmap View” that an SE can look at, which cuts out all the developer-oriented functionality but still shows dates and descriptions and related sales collateral. Nor is there a notion of an Internal Roadmap versus External Roadmap that has less detail, and leaves out the more embarrassing bug fixes.
3. There are Agile Product Management tools out there, like those from Accept Software and Ryma, but (as far as I can tell) they don’t sync with some of the popular project management / bug tracking tools, such as Bugzilla, TargetProcess, and Jira. By “sync” I mean bi-directional data sync.

Given these challenges, what Agile Product Management tool would you recommend?

Product management tools & techniques for 2009

Product Management tools and techniques are continually evolving. Here are some that I’ve found to be especially useful recently:

Agile Product Management requires that you setup up a backlog to track storycards. While there are more expensive solutions out there, Google Spreadsheets are a surprisingly good way to get started with backlog management. It’s easily viewable by an entire team, and can be edited simultaneously by team members. You probably will outgrow your spreadsheet after it gets to 100-200 storycards and will want to move to something more sophisticated, but for getting started, Google Spreadsheets is hard to beat.

Do “live” note taking during customer calls with Campfire. Other participants on the call, developers and other team members can see notes as they are written, and can write in their own follow-up questions in real time. Plus it’s all searchable for later. I’ve seen development teams that live in Campfire, so putting the notes straight into there means that the customer feedback actually reaches the engineers it’s intended to influence.

You can also use Campfire to enable team members to communicate what they’ve done and what they’re working on. This practice goes a long way towards eliminating the “status updates” part of staff meetings, which are generally not all that productive. Yammer’s another good tool for this purpose, if you are not already using Campfire.

Beta customer recruitment is very much a numbers game, a sales process conducted by the product manager. My rule of thumb, based on experience, is that you need about 30 beta program leads for every one active beta user that provides meaningful feedback. Since even a small beta will want at least several active beta users, there’s a significant lead management issue. To address this, use Highrise for managing beta customer recruitment, if you don’t have access to your company’s CRM system or are not allowed to use it for beta programs. Highrise has a free option which is great for getting started.

I know, I’m started to sound like a shill for 37Signals… on to other tools!

Use Google Video Chat to talk with remote developers. Most communication is nonverbal and you get more of this form of communication conveyed with video chat than with a phone call. Unlike the phone, you never have to worry about reaching out to a developer late at night if they’re online. I found it much easier to get Google video chat working than Skype video and iChat video.

Make it a point to connect with all your active customers over IM. When developers come to you with urgent questions that require customer input, you’ll be able to ping several available customers over IM to make an informed decision. For this reason, IM is a huge enabler of Agile Product Management. It’s also great when scheduling meetings and dealing with conference call logistics. Adium (Mac) and Pidgin (Windows) work across all the major IM networks.

Use Google Alerts, Friendfeed, and Twitter Search to stay on top of your market, find beta program prospects, get feedback on your product, and keep up with competitors, standards and events. Get the corresponding RSS or Atom feeds for each search into Google Reader — not necessarily to read every last post — but so you have large, searchable database of what’s happening in your market.

Before meeting with a customer, do your homework on them: what they care about, what challenges they face, and so on. A number of sites let you do this. Currently lesser-known resources for doing this this include Pipl and Twitter. Better known sites include Google Blog Search, LinkedIn, and Facebook.

If your company doesn’t provide you with conference calling and web conferencing, or if you just want to save some money, use DimDim and Free Conference Call. These services are both free and work great.

What do you think? What product management techniques and tools are you planning to use this year?

Can Twitter streamline Agile Development?

I’ve been thinking about if and how Twitter can be used by businesses to streamline their operations. Specifically, for software businesses, which is where my experience lies.

It seems to me that it can. Here’s one way:

Product development teams can use Twitter as an an "accelerator for Agile Development". Let me explain. One best practice of Agile Development is to a have a daily meeting, called a scrum. The meeting typically lasts ten or 15 minutes. It’s very informal. Every member of the development team briefly explains what they’re working on that day, and any blockers they face.

For instance, a developer might be waiting for product management to clarify a requirement. Or a tester might be waiting for a developer to check in a software component.

It sounds simple, but daily scrums are very effective in making problems known to the entire team, and consequently, getting problems fixed faster. With scrums, a blocking problem is unknown for only 24 hours max.

Now, what if a product team used Twitter to maintain a "continuous scrum status stream" — or scrum stream for short? Update your Twitter status once a day to declare what you’re working on. Update your Twitter status whenever a blocking issue comes up.

You would still need a daily scrum meeting, of course, to give everyone a live forum for raising issues. To be clear, I’m proposing Twitter to be used as a way to complement, not replace, existing Agile practices.

I think there would be at least two benefits to this use of Twitter.

Product team members would know about blocking issues even quicker. Problem resolution time would drop.

And, scrum meetings would be shorter, since they’d focus on exceptions, not day-to-day reporting of status.

In terms of security, Twitter already lets you restrict you can see your updates. So, if an engineering adopted Twitter to provide scrum streams, they would not have to worry about everyone on the web seeing those messages.

What do you think? Are there other ways you think Twitter can be used to make businesses work better?