Continuous Deployment Development Team Review Technical Review 
Startup Lessons Learned
FEBRUARY 20, 2009
Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. Take the example of a design team prepping mock-ups for their development team. Give the dev team your very first sketches and let them get started.
Startup Lessons Learned
DECEMBER 7, 2008
Its common to find a hacker at the heart of almost any successful technology company. When a startup encounters difficult technical problems, this is the guy you want solving them. As the company grows, hes the go-to person for almost everything technical, and so hes very much in demand. All is not lost, though.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
NOVEMBER 17, 2008
Playing with new technologies. Now its time to start to think seriously about how to find a repeatable and scalable sales process, how to position and market the product, and how to build a product development team that can turn an early product into a Whole Product. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
OCTOBER 20, 2008
Heres my diagnosis of his problem: He has some automated tests, but his team doesnt have a continuous integration server or practice TDD. And has the tension goes down, it will be easier to get the whole team (including the MBAs) to embrace TDD and other good practices as further refinements. Excellent post Eric.
Startup Lessons Learned
JULY 13, 2009
He shows how the actions of people inside traditional systems are motivated by their rational assessment of their own economics. Reinertsen does not speak about startups specifically - his book is meant to speak broadly to product development teams across industries and sectors. Wow, great review!
Expert insights. Personalized for you.
161 
Let's personalize your content