Remove CTO Hire Remove Design Remove SCRUM Remove Workshop
article thumbnail

7 Highlights from Lean Startup Week

Startup Lessons Learned

And the effort was reflected by the 140 speakers and mentors who took the stage and ran workshops over the course of the seven-day conference. The result is a combination of design thinking, Lean Startup, and Agile Scrum, and Ignacio’s innovation team includes 25 coaches who train employees in PACE best practices.

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. No more, no less. September 15, 2008 9:19 PM James said. Amazon PostRank

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. When its receding, we rescope. Do you have a spec? Do you do hallway usability testing?

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. And wait until you see a "non-technical" designer writing simple code to try and speed up a release.