Tearing up the spreadsheets....our move to Rally Software

Wednesday, August 29, 2007 10:24:23 PM (Mountain Daylight Time, UTC-06:00)

I'm not a huge believer in tools for tools sake.  And, I'm really not a big believer in big tools for project management, especially when you’re going Agile.  However, since we started scrumming, we have been using spreadsheets to manage our product, project, release, and sprint backlogs.  As our projects grew and our team embraced Scrum, our spreadsheets became increasingly complex.  We were using Excel to not only create backlogs, but also to create "executive" dashboards, developer dashboards, team utilization reports, actual time keeping for tasks, etc.  The spreadsheets were turning into a relational database of sorts...and they were getting unwieldy.  While the team was really enjoying what we had created in Excel, the ScrumMaster (that's me), was working behind the scenes to "manage" the spreadsheets.  It was taking a few hours every Sprint just to update the spreadsheets, create the correct linkages, generate the reports, etc.  In addition, as we tried to link multiple projects across Excel workbooks for utilization reports, timekeeping, and other assorted TPS type reports, things grew even more complex.

So, we thought, "We're a group of developers, let's turn this into an application."  I sketched out a database schema for the back-end and started putting together estimates for building our own custom solution.  At the same time, I began evaluating COTS solutions.  I looked at several vendors' products.  Some were desktop applications and others were web apps.  When I finished my evaluation, it looked like our costs to design, develop, and implement our own solution were easily going to be in the six-digit range.  Now, we work for a consulting firm and internal R&D/dev projects don't usually get funded at that level.  So, we turned our sights back to the COTS products and did a more rigorous evaluation.  We narrowed the field down to two solutions and trialed them both for a month.  At the end of the trial, it was clear that Rally Software had the solution that fit our team the best.

Rally is a web based solution that is completely hosted on Rally's servers.  This meant ease of maintenance and no worries about up-time, updates, database maintenance, etc.  Overall, we concluded that Rally hit about 95% of the functionality we were looking for as well.  Rally offers three different flavors of its solution: Rally Community, Rally Program, and Rally Enterprise

  • Rally Community is free for up to 10 users and supports single project, single release teams.  It offers basic Agile project management and integrated defect management as well. 
  • Rally Program supports Agile project management across multiple teams, multiple programs and projects, and multiple releases.  It has options for integrated defect management and test management, as well as an available web API.  It runs $39/month for the core package, and an additional $8/month for each option ($10 for the API). 
  • Rally Enterprise is a full blown project management solution which has everything the Program solution has, plus all of the options and premium support.  It runs $65/month. 

We selected the Rally Program solution.  We also purchased the defect management option, and we have a trial license for the Web API.  We found the Rally sales team to be very helpful in getting started up.  They're support has been good so far and they even gave us a 1 hour into to Rally for the entire team. 

We just started using the application this week on one of our biggest projects.  We found it very easy to import our existing user stories and backlog items from Excel into Rally using their CSV import templates.  Once we had our backlogs populated, it was simple to create Projects, Releases, and Iterations within the program.  Moving a backlog item into a Release or Sprint is as easy as dragging and dropping it from the backlog into the Release or Sprint backlog.  Creating Tasks within a Sprint backlog item is also extremely easy.  We were able to assign Tasks to team members and instantly see how each task affected individual utilization for the Sprint.  In addition to creating backlog items, etc., we also imported our existing defect lists from our SharePoint site using Rally's defect CSV templates.  Again, totally easy operation. 

In the short time we've been using Rally, the entire team has been completely impressed with the functionality and great performance.  We can't believe how fast the app works.  You won't even realize it's a web app after a few minutes of using it.  Our seasoned developer team has stated that they think Rally is one of the best web apps they've ever seen, and that's saying a lot.  The Team has been jumping right in and taking advantage of everything Rally has to offer.  And I have been taking it a little easier now that I don't have to spend countless hours maintaining our old spreadsheets!


Check out Rally Software at http://www.rallydev.com/.  You can get a free trial, or start using their Community solution if you have a single release project.  For a comparison of all of the features each solution offers check out http://www.rallydev.com/product_editions.jsp.

  Logo: Rally Software Development


 

 

Thursday, August 30, 2007 11:05:11 AM (Mountain Daylight Time, UTC-06:00)
What was the other solution that you evaluated?

Be cautious when you are using the API. We have written several tools to use it, and their frequent software upgrades have broken our tools more than once.

The Rally team is very friendly and they try to be helpful, but they have not been particularly responsive to our feature requests.

They also have told us that they don't have any human QA engineers, and that's reflected in the Rally workflow: it's very difficult to track the work of a QA team that's working with your development team.

It is definitely one of the best products available for agile teams, but it's not perfect, and many of the benefits of a hosted application have to be balanced with the risks that the next upgrade will break your home-grown tools, introduce new defects, and take away features that you were relying on. If you were hosting it yourself, you would at least have the option to stay on a stable release.
Rally User
Friday, August 31, 2007 1:51:45 PM (Mountain Daylight Time, UTC-06:00)
(Disclaimer: I'm a product manager at Rally.)

It's true that in the past we did release upgrades that changed the web services API. It turns out that many SOAP clients are brittle and even additive changes can break SOAP integrations. (REST doesn't have this problem as much). So earlier this year we wrote infrastructure to version the web services API, allowing customers to stay on old versions when we release. As far as I know, since we did this we haven't had any customers complain that a release broke their integration.

We have increasingly large numbers of customers who are still doing extensive manual testing and who want more features targeted towards this. Based on customer feedback, we have a number of features in progress to make things easier for traditional QA teams.

Our new community site, Agile Commons (http://agilecommons.org) has a section for Rally customers only that provides visibility into our backlogs and roadmap. We're also making it easy for customers to vote up and down certain features. The goal of this is to improve feedback and help customers see why we chose the enhancement requests we do.

Personally, I like the SaaS model because it allows us to respond much faster to widespread customer requests, allows better feedback from customers as we build new features, and forces us to worry constantly about compatibility and migration. We're not perfect, but we're getting better at this with every release.
Comments are closed.