This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Continuous DeploymentDevelopment Team ReviewStartup
Its had tremendous impact in many areas: continuousdeployment , 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 developmentteam. Give the devteam your very first sketches and let them get started.
Guest post by Lisa Regan, writer for The Lean Startup Conference. As Lean Startup methods have been used now for a number of years, we’ve become increasingly interested in how companies use them to sustain growth. But we couldn''t have identified this without having clear metrics (that high bug count) to assess our development process.
Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. I met one recently that is working on a really innovative product, and the stories I heard from their developmentteam made me want to cringe.
And yet it is this same ephemeral nature that gives rise to the most difficult problems of product development: how to tell if were making progress, the high variability of most product development tasks (e.g. and the resulting extreme uncertainty that is, incidentally, the environment where startups thrive.
This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Heres the catch.
The technical interview is at the heart of these challenges when building a product developmentteam, and so I thought it deserved an entire post on its own. By far the most important thing you want to hire for in a startup is the ability to handle the unexpected. Those people also tend to go crazy in a startup.
Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. In teams that have a business culture, the MBAs pick time.
Lessons Learned by Eric Ries Monday, November 17, 2008 The four kinds of work, and how to get them done: part one Ive written before about some of the advantages startups have when they are very small, like the benefits of having a pathetically small number of customers. A "startup within the startup" feeling is a good thing.
You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. That’s what most startup decisions are like. Because of the extreme unknowns inherent in startup situations, we are all blind – to the realities of what customers what, market dynamics, and competitive threats.
Those who have the endurance are the ones that tend to lead teams and join startups, because you just cant be successful in a startup situation without empathy. When a startup encounters difficult technical problems, this is the guy you want solving them. I would characterize them as intolerant but not arrogant.
But I want to talk about a different kind of leverage, the kind that you can get in product development. Its a force that allows startups to build products at parity with much larger companies - cheaper and much faster. Its a key lean startup concept. Open APIs and data-oriented architecture (aka "web 2.0").
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content