Cofounder Continuous Deployment Email SCRUM 
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 15, 2008
I would add -- think of your development and running your business like a PM/Developer uses Agile or Scrum in software development. Mark Montgomery Founder Kyield Initium VC September 12, 2009 4:21 AM Mark Montgomery said. Case Study: Continuous deployment makes releases n. No more, no less. Good stuff. Great blog!
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
APRIL 9, 2009
sachinrekhi : "Visionary customers are as smart if not smarter then the founders" #leanstartup Theres no skipping the chasm. My cofounders and I would hash out nuances and details almost every day, re-drawing diagram after diagram on the whiteboard. Heres the promo; more information is available on their site. Excellent post.
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
OCTOBER 5, 2008
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.
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. At IMVU, we found 60 days was just about right.
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