Remove CTO Hire Remove Founder Remove San Francisco Remove SCRUM
article thumbnail

7 Highlights from Lean Startup Week

Startup Lessons Learned

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
article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

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. Mark Montgomery Founder Kyield Initium VC September 12, 2009 4:21 AM Mark Montgomery said.

Lean 168
Insiders

Sign Up for our Newsletter

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

article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

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.

article thumbnail

You don't need as many tools as you think

Startup Lessons Learned

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. No departments The Five Whys for Startups (for Harvard Business R.