Skip to main content

RallyDev- Hosted Agile Project Management & Collaboration Tool

UPDATE: Feb 2010: I wrote the following in Jan 2006 before I had enough exposure to User Stories and before I got stuck in the quagmire that Rally - at least in that version - turned out to be. I stopped using it a month later. The problem was ironically the same problem Agile development evolved to solve- Rally itself was over-engineered, tried to do much and did the simple & important things not well enough-- if at all. To make matters worse, it was very slow and highly cumbersome to input info into- these were the early days of Web 2.0 and Rally seemed to be going overboard with use of AJAX. I've heard good things about Rally again lately but haven't validated it for myself. I'll do a separate blog post on this topic when I do.

I'm smitten by the Agile software development methodology. It's not as if I've heard about it only today, but now I have a tool that can (I believe) help me manage the CommuterStation product development in India more effectively.

The great thing about it is that it lets you- nay, it makes you - define your product's Features & Use-cases, Releases and Iterations, Resources and Tasks, so that they are all online, inter-dependent, and trackable and manageable. One of the cool things is about Rally is the integration with Eclipse and Fitnesse.

Check out the following for starters on Agile, if you want to get started.
Agile Manifesto
Agile Alliance

And of course, there's no substitute for simply Googling "Agile" or "Agile Project Management".
Labels:

Comments

Post a Comment

Popular posts from this blog

Splitting User Stories vs. Rally's "split" feature (that has nothing to do with it!)

Agile tool Rally has a "split" feature it recommends to handle "unfinished work" in a Scrum Sprint: Manage Unfinished Work - Split user stories ( new link ) Below are my observations on the "Split" feature in Rally (followed by a few excellent articles on Splitting User Stories):   This "split" feature in Rally has numerous problems: 1. Nothing to do with Splitting User Stories It has nothing to do with "Splitting a User Story" which is an advanced but fairly well-understood field in Agile, and a tool for Product Managers to use in one of the two scenarios: The Product Manager does it before an Iteration commences (i.e. during backlog creation or release planning) to create User Stories by business value that are right-sized, i.e. they can be comfortably implemented inside an iteration; The Product Manager does it in Iteration Planning or in the middle of an Iteration to reduce scope by removing/simplifying accept
Post a Comment
Read more

Entrepreneur Committee - Advisory Board of SVASE

For whatever it is worth, I would like to announce to my millions of would-be readers that I have been invited to join the Entrepreneur Committee on the Board of Advisors to the Silicon Valley Association of Startup Entrepreneurs . And I have accepted. If you're a hi-tech entrepreneur, I would love to hear your suggestions on what I can do in my "official" capacity to make SVASE a better organization for startups.
Post a Comment
Read more

Test Trimming: A Fable about Testing

While browsing the web randomly, I found this very cool article on the value of testing. Says the author, Gerald M. Weinberg: "Throughout my career, I've watched in dismay as one software manager after another falls into the trap of achieving delivery schedules by trimming tests. Some managers shortcut test work by skipping reviewing and unit testing in the middle of their project. Others pressure the testers to "test faster" at the end. And, most frequently, they just drop planned tests altogether, hoping they "get lucky." I've written several essays about the dangers of test trimming, but nobody seems to understand, so I asked myself, "What am I doing wrong?" Perhaps I wasn't practicing what I was preaching. Perhaps I was trimming tests myself. Perhaps my writing needed more testing! So, I wrote a story about taking shortcuts and read it to my granddaughter, Camille."
Post a Comment
Read more