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. Both Scrum and XP had a role which you could happily call by the modern title "Product Manager". Embedded in that assumption is why startups fail.

Agile 111
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. At IMVU, we found 60 days was just about right. Try About the author.

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: 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. 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. Great blog!

Lean 168
article thumbnail

Lessons Learned: The product manager's lament

Startup Lessons Learned

They exchange countless emails, and hes being constantly interrupted and being asked to clarify exactly what the spec means. The fourth spec exists only in these emails, which are changing the design in an ad-hoc fashion. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more.

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. We had all the tools in place but we didn’t actually practice agile development. Want to learn more about me?

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? Want to learn more about me?

article thumbnail

Lessons Learned: Built to learn

Startup Lessons Learned

I have been using various forms of Agile development -- mainly XP and Scrum -- for many years, but only recently came across "customer development" which makes a whole lot of sense to me. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF.