Remove 2009 Remove Continuous Deployment Remove SCRUM
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. April 27, 2009 8:59 AM Anonymoussaid. July 15, 2009 11:18 PM markmontgomery said. Mark Montgomery Founder Kyield Initium VC September 12, 2009 4:21 AM Mark Montgomery said.

Lean 168
article thumbnail

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

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. March 16, 2009 11:18 PM William Pietri said. March 17, 2009 9:21 AM Eric said.

Agile 111
Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

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

Startup Lessons Learned

But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. May 15, 2009 1:17 AM neocoder said.

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. If the team is continually falling behind, it would seem that these teams were no fully aware of their expectations to begin with. Case Study: Continuous deployment makes releases n.

article thumbnail

Embrace technical debt

Startup Lessons Learned

Lessons Learned by Eric Ries Wednesday, July 29, 2009 Embrace technical debt Financial debt plays an important and positive role in our economy under normal conditions. Very much appreciate the suggested solutions (Five Why's, split testing etc) July 29, 2009 6:24 AM Kevin Gadd said. July 29, 2009 6:57 AM Heiner Wolf said.

article thumbnail

Lessons Learned: Built to learn

Startup Lessons Learned

Lessons Learned by Eric Ries Thursday, April 9, 2009 Built to learn Its been an exhilarating ride since the Web 2.0 Well be discussing in greater detail the three techniques I highlighted at the Expo: continuous deployment, split-testing, and five whys. Ill continue to post about additional events as I get them scheduled.

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. Case Study: Continuous deployment makes releases n.