Startup Lessons Learned
MARCH 16, 2009
Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. XP and Scrum don’t have much to say - they punt. Both Scrum and XP had a role which you could happily call by the modern title "Product Manager".
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. Great blog! Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. No more, no less. Good stuff.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
DECEMBER 6, 2008
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. At IMVU, we found 60 days was just about right.
Startup Lessons Learned
OCTOBER 5, 2008
Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. Ive written about it on our development blog at [link] October 6, 2008 3:34 PM Chris Hondl said. Startup Lessons Learned season one : Every post from the blogs first year in print form.
Startup Lessons Learned
APRIL 9, 2009
Answering that question is what Im striving to do on this blog (and at future webcasts and workshops ). Loved your W2E talk and included it in my Girls in Tech blog as the #1 session at W2E! Startup Lessons Learned season one : Every post from the blogs first year in print form. No engineering team. Thanks for sharing Eric.
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. Startup Lessons Learned season one : Every post from the blogs first year in print form.
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. Startup Lessons Learned season one : Every post from the blogs first year in print form.
Expert insights. Personalized for you.
111 
Let's personalize your content