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. April 23, 2010 in San Francisco. No more, no less. Bring your questions.

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. April 23, 2010 in San Francisco. When its receding, we rescope.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

DECEMBER 14, 2017

Editor’s Note: We wrapped up the 2017 Lean Startup Week in San Francisco just a few weeks ago, and we’re excited to share with you some of the best lessons learned in entrepreneurship and corporate innovation. LESSON #3: Avoid these three hiring mistakes. First, do not hire someone just because they have the domain expertise.

Lean 245

Lean Startup CTO Hire Cofounder 245

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. April 23, 2010 in San Francisco. Bring your questions. Take a look and let me know what you think.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68