Remove Continuous Deployment Remove Design Remove Development Team Review
article thumbnail

Lessons Learned: Work in small batches

Startup Lessons Learned

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I dont think so.

article thumbnail

Lessons Learned: The product manager's lament

Startup Lessons Learned

I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe. The product manager was clearly struggling to get results from the rest of the team. These specs are handed to a designer, who builds layouts and mockups of all the salient points.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

The Principles of Product Development Flow

Startup Lessons Learned

Reinertsen is keenly aware of what makes product development different from other business functions, like manufacturing, that we sometimes use as a metaphor. Product development deals in designs, which are fundamentally intangible. Hence the need for partitioning our resources into a separate problem team and solution team.

article thumbnail

Lean Startup at Scale

Startup Lessons Learned

But we couldn''t have identified this without having clear metrics (that high bug count) to assess our development process. As Shutterstock has grown, there are a few key elements to our continued development speed: Small, autonomous teams: The more a team can do on their own, the faster they can go.

Lean 167
article thumbnail

Lessons Learned: What is customer development?

Startup Lessons Learned

You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Our goal in product development is to find the minimum feature set required to get early customers.

article thumbnail

Lessons Learned: The ABCDEF's of conducting a technical interview

Startup Lessons Learned

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. Still, a startup product development team is a service organization. Case Study: Continuous deployment makes releases n. What is customer development?

article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

Most of the other processs changes - mandatory design reviews (prelimninary, critical, etc), - documenting all our procedures, and so on - were to support those two factors. It might be more precise to categorize them of two kinds of flaws: flaws in implementation, and flaws in design. Im keen on the two-kinds-of-bugs thing.