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. In the case of C3, that was to run payroll for 87,000 employees, who were presumably receiving payroll before the project began. Thats pretty clear.

Agile 111
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. I would add, though, a further question: Do new employees write code on their first day?

Insiders

Sign Up for our Newsletter

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

article thumbnail

7 Highlights from Lean Startup Week

Startup Lessons Learned

Editor’s Note: We wrapped up the 2017 Lean Startup Week in San Francisco just a few weeks ago, and we’re excited to share with you some of the best lessons learned in entrepreneurship and corporate innovation. Instead, employees “were like, ‘Well, I don't know how to give my peer feedback. Second, don’t simply hire your buddies.

Lean 245
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. April 23, 2010 in San Francisco. Bring your questions.