Remove Agile Remove Product Development Remove Programming Remove Restful
article thumbnail

A Startup CTO’s Take on Early Technology Choices & Tradeoffs

View from Seed

You always want to be careful with how tightly you schedule things to make sure you stay agile and responsive to evolving business needs, but you also need to make sure your overall journey makes sense and that you’re building things in the right order, as well as taking on risks in a measured way.

article thumbnail

Lessons Learned: Please teach kids programming, Mr. President

Startup Lessons Learned

Lessons Learned by Eric Ries Sunday, February 22, 2009 Please teach kids programming, Mr. President Of course, what I really mean is: let them teach themselves. See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding?

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Beyond the garage

Startup Lessons Learned

SLLCONF featured incredible entrepreneurs on stage to put those ideas to rest (watch, for example: Aardvark , Grockit , Dropbox , PBworks ). It may be hard to remember that there was a time when people in the agile software development community thought Lean Startup was incompatible with agile practices.

article thumbnail

Blowing up the Business Plan at U.C. Berkeley Haas Business School

Steve Blank

The disadvantage is that its methodology was based on the old waterfall model of product development and not the agile and lean methods that startups use today. It taught lean theory ( business model design , customer development and agile engineering) and practice. Seeing Is Believing. The Business Plan is Dead.

article thumbnail

Maybe not so much with the "optimization"

A Smart Bear: Startups and Marketing for Geeks

Now by all of the usual arguments for Lean, Agile, and minimimalism, I should have used boogers too: Boogers were already semi-standardized. User interfaces should follow the principle of "least surprise" — if people are used to a certain metaphor, icon, or behavior, you should honor that so people understand your product immediately.

article thumbnail

The Five Whys for Startups (for Harvard Business Review)

Startup Lessons Learned

And yet the key to startup speed is to maintain a disciplined approach to testing and evaluating new products, features, and ideas. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Read the rest of The Five Whys for Start-Ups. for Harvard Business Revie.

article thumbnail

Speed up or slow down? (for Harvard Business Review)

Startup Lessons Learned

This is the first post that moves into making specific process recommendations for product development. Read the rest of The Startups Rules of Speed - The Conversation - Harvard Business Review. Labels: product development Speed up or slow down? (for This is the speed-up-or-slow-down moment.