Skip to main content

Agile Entrepreneurs- Part 1 of 3: Agile Methods for Startups

Mark my words, it is going to start happening within a year. I can see it in my Crystal Ball :) And remember, you read about it here first- Friday, Jan 27, 2006!

Agile methodology, XP, and Hosted Agile Project Management tools (like Rally) are poised to take software entpreneurship and offshore outsourcing to the next level.

India is finally going to shake off it's mentality of servitude and take major steps towards fostering Silicon Valley style innovation.

How? Agile/XP approach of rapid, iterative development with customer feedback at its core is screaming from rooftops with a megaphone for very very v... early stage startups and budding software entrepreneurs to notice it. It's a marriage made in heaven!

I can't think of a more natural fit of a solution to a problem. Agile development is for software entrepreneurs what lithium is for bipolar disorder (ok, so I guess the analogy proves that I can actually think of a more natural fit).

... contd. in "Agile Entrepreneurs- Part 2 of 3"

Comments

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

Venture Quotes for a softening economy

Guess who said the following? "There's a lot of hot air and arrogance in the (VC) business that we all would be better off without" "...useless pontificating in front of entrepreneurs working harder than (VCs)..." "...VCs who constantly speak of deals and projects , reveal their self-interest and slight the labor and dreams of the entrepreneurs" If you think it's some disgruntled entrepreneurs who don't "get it", think again. In the past, I've made some pretty strong but heartfelt things, and I could have said the above, but I didn't . Read on here to learn who uttered these pearls of wisdom.

User Stories: you're not Agile without them

Failure to effectively transition to Agile development is often based on a fundamental failure to understand what a User Story is. Allow me to explain. The most important aspect of a User Story is that it's an independently *schedulable* unit of requirement (feature). The key to achieving the "independently schedulable" characteristic of a user story is that you express it in terms of how a "user" would use it. This leads you to a unit of functionality that's implemented end-to-end (UI to backend) that a user can actually interact with. Not surprisingly, because of the focus on how a user would think about a feature, a user stories are highly readable - and could very well be written by the users themselves. However, the other important and less obvious aspect of a User Story is the emphasis on communication with the end-user and getting confirmation on the acceptance criteria. Describing all the requirements as User Stories for a decent sized product is