Startup Lessons Learned

SEPTEMBER 15, 2008

My belief is that these lean startups will achieve dramatically lower development costs, faster time to market, and higher quality products in the years to come. I would add -- think of your development and running your business like a PM/Developer uses Agile or Scrum in software development. No more, no less.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 10, 2008

There are several ways to make progress evident - the Scrum team model is my current favorite. If you have a true cross-functional team, empowered (a la Scrum) to do whatever it takes to succeed its likely they will converge on the result quickly. When its receding, we rescope. Do you have a spec?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JULY 29, 2009

Although it costs to pay down the principal, we gain by reduced interest payments in the future. In addition, third-party services and API’s enabled us to do more with less, but at a cost: taking on the technical debt of products and teams outside our direct control. For example, how fault tolerant should it be?

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

APRIL 9, 2009

I have been using various forms of Agile development -- mainly XP and Scrum -- for many years, but only recently came across "customer development" which makes a whole lot of sense to me. Inspired me to expand on the "whiteboard iteration" idea with some similar lessons that ive learned. link] April 11, 2009 10:24 PM Daniel Prager said.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132