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
After all, Gmail wasn’t taken out of beta until 2009 — five years after it was originally released. Automated testing assesses the designed boundaries of your product. Google is notorious for this, releasing many of its products in beta form — and sometimes even leaving them in that phase for years. What You Gain From Beta Testing.
Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. 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.
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. The product manager was clearly struggling to get results from the rest of the team. one more thought, where were the code reviews? October 6, 2008 12:17 AM r& said.
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 agiledevelopment. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Great post.
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 developmentteam that can turn an early product into a Whole Product. What is customer development? Using AdWords to assess demand for your new online.
Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the product developmentteam of a startup (large or small) is a service organization. I am basically a one-man shop.
Lessons Learned by Eric Ries Monday, June 8, 2009 Datablindness Most of us are swimming in a sea of data about our products, companies, and teams. You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. June 8, 2009 8:28 PM Geoff said. Great post and great ideas.
In the early days of the CMS we had major players such as OpenText (which didn't really have true CMS functionality until around 2002 ), Vignette (which was a separate company before being acquired by OpenText in 2009), and Fatwire (which was acquired by Oracle this past summer), among others. Note a trend here?
Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. April 27, 2009 10:54 AM DSarathy said. Great post!
These serve to ensure that everyone who ends up on the developmentteam knows what the system is for. More than one person can review it, but only one person can author. My experience says that if the developmentteam relies on mockups and documents created by customers then the team and the project are in a real trouble.
As I evolved my thinking, I started to frame the problem this way: How can we devise a product development process that allows the business leaders to take responsibility for the outcome by making conscious trade-offs? When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer.
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. The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation.
Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you.
How about reviewing some of the incredible work being done by the likes of Mark Rendle, Ben Vanderveen, Alex Robson, Jon Skeet, Chris Patterson, Glen Block, Rob Eisenberg or Steve Sanderson? I run a.NET developmentteam and before this gig I spent 4 years running a web app written in.Net. March 26, 2011 at 1:15 am.
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