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

User Stories for Product Managers

I've previously said that User Stories are the most powerful construct in Agile methods, more than TDD, in my view. The challenge in using User Stories though lies in the fact that they shift the responsibility of getting things right - and quite fairly I might add - from the Engineering team onto the Product Owner/Product Manager. And unless you have strong buy-in from management, it's difficult to make it to the end of the Product Management process and to a point where you're cranking out iterations one by one. The key lies in efficiency in creating and managing User Stories, and tying them effectively to an evolving User Interface even as the product starts coming alive. I'm planning to share some of my experiences and thoughts on this soon. Meanwhile, I found this interesting article while searching the net for splitting stories along CRUD capabilities. Ways to split user stories .
Post a Comment
Read more

Agile Entrepreneurs Manifesto

The  Agile Manifesto  defines the 4 core Values that define "Agile":  " Individuals and interactions",  " Working software",  " Customer collaboration", and  " Responding to change" As I applied Agile requirements (user stories), engineering (XP), and process & project management (Scrum & Kanban) to my startups  (RideStation, and Agile Entrepreneurs)  starting from 2005 to now in 2018, I learned numerous lessons and shared them with my fellow entrepreneurs for the next dozen years. These lessons I have incorporated by "extending" the Agile Manifesto with two additional values pertaining to  Product (5th) and Startup/Business (6th)  -  that the services consultants who wrote it in 2001 probably didn't have to contend with as most (all?) of them were not founders of product startups:  "User Validation, Customer Traction, and Business Milestones" Agile Entrepreneurs Manifesto Us...
Post a Comment
Read more