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
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. The product manager was clearly struggling to get results from the rest of the team. October 6, 2008 12:17 AM r& said.
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. And over time, the developmentteam may be able to start anticipating your needs. That frees up even more development resources, and so on.
We have been using LinkedIn for both sourcing recruits and reviewing backgrounds for recruits. Its been great to zero in on very specific skillsets. The level of resumes we get through our LinkedIn networks is top notch. Technology Advisor Technology Roles in Startups Pricing Customer Acquisition Sunk Costs and More -.
Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? Our goal in product development is to find the minimum feature set required to get early customers. In order to do this, we have our customer developmentteam work hard to find a market, any market, for the product as currently specified.
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. And if you neglect maintenance, you may not have a business left at all.
Lessons Learned by Eric Ries Sunday, December 7, 2008 The hackers lament One of the thrilling parts of working and writing in Silicon Valley is the incredible variety of people Ive had the chance to meet. At the end of the day, the product developmentteam of a startup (large or small) is a service organization. Great article.
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. That’s because many of our reports feed us vanity metrics: numbers that make us look good but don’t really help make decisions. Too much of this data is non- actionable.
Saturday, February 16, 2008. The CTO should not manage developers. The head of development spends his or her time working to keep the developmentteam on track against a set of product plans. But if it’s wrong, the CTO has solid documentation to review. On the Use, and Misuse, of Software Test Metrics.
The idea of leverage is simple: for every ounce of effort your product developmentteam puts into your product, find ways to magnify that effort by getting many other people to invest along with you. It allowed me to assess the market demand for that offline product before I had the final product baked.
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. October 20, 2008 9:34 PM Nivi said. October 20, 2008 10:36 PM Nathan said.
Lessons Learned by Eric Ries Saturday, November 29, 2008 The ABCDEFs of conducting a technical interview I am incredibly proud of the people I have hired over the course of my career. 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.
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 developmentteams across industries and sectors. Wow, great review!
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