Remove Lean Remove SCRUM Remove Washington
article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, September 8, 2008 The lean startup Ive been thinking for some time about a term that could encapsulate trends that are changing the startup landscape. After some trial and error, Ive settled on the Lean Startup. I like the term because of two connotations: Lean in the sense of low-burn.

Lean 168
article thumbnail

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

XP and Scrum don’t have much to say - they punt. If you look at the origins of most agile systems, including Scrum and XP , they come out of experiences in big companies. Notice that the unit of progress changes as we move from waterfall to agile to the lean startup. Embedded in that assumption is why startups fail.

Agile 111
Insiders

Sign Up for our Newsletter

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

article thumbnail

The four kinds of work, and how to get them done: part three

Startup Lessons Learned

The advantages of cross-functional teams are well documented, and for a thorough treatment I recommend the theory in the second half of Agile Software Development with Scrum. Scrum recommends 30 days; I have worked in one or two-week cycles up to about three months. The Lean Startup Intensive is tomorrow at Web 2.0.

article thumbnail

Lessons Learned: The product manager's lament

Startup Lessons Learned

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. Great to read posts about introducing lean approaches into more teams. Im currently introducing lean to my new team. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. for Harvard Business Revie.

article thumbnail

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

Startup Lessons Learned

Plus, as product development teams in lean startups become adept at learning-and-discovery (as opposed to just executing to spec), its clear that some bugs shouldnt be fixed. There are several ways to make progress evident - the Scrum team model is my current favorite. The Lean Startup Intensive is tomorrow at Web 2.0.

article thumbnail

Lessons Learned: Built to learn

Startup Lessons Learned

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. The lean startup focuses on situations where we have both an unknown problem and an unknown solution. The Lean Startup at Web 2.0

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. The lean manufacturing guys call this visual control and its very powerful. Expo SF (May.