Startup Lessons Learned

SEPTEMBER 15, 2008

I would add -- think of your development and running your business like a PM/Developer uses Agile or Scrum in software development. You need an overarching vision and goal but just try to get to the next level, one iteration or sprint at a time. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 22, 2008

Heres something I can relate to: We used assembla for subversion, scrums, milestones, wikis, and for general organizational purposes. Scrum reports would come in once a month, nobody was actually responsible for anything. And wait until you see a "non-technical" designer writing simple code to try and speed up a release.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

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? Do you do hallway usability testing?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144