Skip to main content

Micro-lending for Agile Entrepreneurs

These are indeed exciting times for the bootstrapping entrepreneur! If you haven't already, please join our self-help networking group, Agile Entrepreneurs where entrepreneurs help each other with a variety of issues in a format borrowed from the Toastmasters club.

And if you're in a tight spot for money, you should join our group on Prosper.com, an excellent people-to-people lending web-site that I wish had found six months ago. In fact, I wish I had founded this group a year ago! I had certainly been talking about the concept- my friend Pravin can attest to that fact.

Regardless, I've dived in and created a closed group in Prosper, called Agile Entrepreneurs. I intend to invite other entrepreneurs to join the group and use it to raise small loans until they are able to generate cash flow or get funding.

And if you're looking to make money while helping out your fellow entrepreneurs, you should support Agile Entrepreneurs on Prosper.

You make money on the interest that is set by an eBay-style bidding, based on the borrowers credit history. Most people make multiple loans of small amounts to diversify and reduce their risk. Note that Pierre Omidyar, the founder of eBay is an investor in Prosper!

So far Prosper seems to have had excellent results for both lenders and borrowers.

Check it out!

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