Austin Continuous Deployment Marketing SCRUM 
Startup Lessons Learned
MARCH 16, 2009
XP and Scrum don’t have much to say - they punt. What’s worse is that as you grow you’ve probably developed some pretty bad habits as far as setting priorities and strategy: like thinking you’re a genius - just because you got funded - and that genius is what allows you to *know* what the market wants.
Startup Lessons Learned
SEPTEMBER 15, 2008
My belief is that these lean startups will achieve dramatically lower development costs, faster time to market, and higher quality products in the years to come. I would add -- think of your development and running your business like a PM/Developer uses Agile or Scrum in software development. No more, no less.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
APRIL 9, 2009
blader : @ericries my #1 takeaway from #leanstartup : "No marketing team. So instead of having sales, marketing, and business development, we have a problem team implementing customer development. Well be discussing in greater detail the three techniques I highlighted at the Expo: continuous deployment, split-testing, and five whys.
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
When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
OCTOBER 5, 2008
But I have a special sympathy for the "product manager" in a startup that is bringing a new product to a new market, and doing their work in large batches. 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.
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. Take a look and let me know what you think.
Expert insights. Personalized for you.
111 
Let's personalize your content