Remove Cloud Remove Lean Remove SCRUM Remove Web
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

Startup Tools

steveblank.com

Poplytics – online surveys and analytics AskYourTargetMarket – market research surveys SurveyMonkey - granddaddy of on-line surveys Amazon Mechanical Turk – you can set up a question and get answers PickFu – A/B testing $5 for 50 opinions Collaboration Dropbox – store, sync, and, share files online.

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.

article thumbnail

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

Startup Lessons Learned

This is still an essential practice, especially on the web. There was a time when "web content" was considered "not code" and therefore not routinely source controlled. There are several ways to make progress evident - the Scrum team model is my current favorite. Lets start with the original list: Do you use source control ?

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

The most valuable lessons I learned from managing a virtual team

The Next Web

Solution #1: At least once a week have a scrum meeting that absolutely everyone prioritizes. After the scrum, if time allows, hang out and catch up. Solution #2: Put everything in the cloud where the whole team can access it. Lean methodology runs on measurements as well so it was a complementary system to implement.