Blog Continuous Deployment SCRUM 
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! Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 10, 2008
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. Can you make a build in one step?
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. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
APRIL 9, 2009
Answering that question is what Im striving to do on this blog (and at future webcasts and workshops ). Well be discussing in greater detail the three techniques I highlighted at the Expo: continuous deployment, split-testing, and five whys. Loved your W2E talk and included it in my Girls in Tech blog as the #1 session at W2E!
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. If the team is continually falling behind, it would seem that these teams were no fully aware of their expectations to begin with.
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. Case Study: Continuous deployment makes releases n.
Expert insights. Personalized for you.
111 
Let's personalize your content