Development Team Review Metrics New York Technical Review 
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. Hes just as comfortable writing code as racking servers, debugging windows drivers, or devising new interview questions. All is not lost, though.
Startup Lessons Learned
FEBRUARY 20, 2009
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. And over time, the development team may be able to start anticipating your needs. That frees up even more development resources, and so on.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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. No amount of fixing is making any difference, because the fixes arent pinned in place by tests, so they get dwarfed by the new defects being introduced with new features.
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!
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. Seeing whats possible. Building and testing prototypes.
Expert insights. Personalized for you.
94 
Let's personalize your content