Continuous Deployment San Francisco SCRUM 
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. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.
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. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. April 23, 2010 in San Francisco.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
MARCH 16, 2009
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.
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
JULY 29, 2009
To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuous deployment. Darn good - I have struggled in relevant conversations with our in house move to scrum/agile. April 23, 2010 in San Francisco.
Startup Lessons Learned
APRIL 9, 2009
Well be discussing in greater detail the three techniques I highlighted at the Expo: continuous deployment, split-testing, and five whys. How to Build a Lean Startup, step-by-step Get started with a detailed guide to three key lean startup techniques: continuous deployment, rapid split-testing, and root cause analysis (five whys).
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.
Expert insights. Personalized for you.
168 
Let's personalize your content