Skip to main content

Agile Entrepreneurs, Part 3 of 3: Agile Software Development

The Agile entrepreneur has a choice all too common these days.

Implement it yourself. Or hire smart people for equity only- easier to do in the Silicon Valley than anywhere else (it's amazing what a single ad in Craigslist can do). Or pay young, super-smart programmers in India for a fraction of your monthly salary- you may not be able to afford it for a whole year, but we're talking about 3 weeks (i.e. iterations) here at a time.

Regardless of the approach, practically every software entrepreneur in the US now has the ability to incrementally implement the features defined by the customer(s) , one iteration at a time. And get valuable feedback. And sooner or later, you'll have a paying customer as long as you stay true to the principles of Agile- "The Customer Is Always Right At The Beginning Of Each Iteration" (apologies to Sam Walton and Kent Beck:).

Alternately, the customer(s) might realize soon enough and declare that the product doesn't have as much value for them as they initially thought - and led the entrepreneur to believe. That is, either they won't buy or the price is not worth the effort for the entrepreneur.

No big deal. The entrepreneurial itch has been scratched, definitively, affordably. He can move on to better things in life, like, umm ... another product?

Software entrepreneurs no longer have to choose either risking getting burnt in order to find out whether their idea has merit or living for the rest of their lives wondering what if.

For more tips for Agile Entrepreneurs, go to www.AgileEntrepreneurs.com

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