Continuous Deployment Management Product SCRUM 
Startup Lessons Learned
OCTOBER 5, 2008
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. Frustration is mounting.
Startup Lessons Learned
MARCH 16, 2009
In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next. But, over the years I’ve realized that the toughest problem - the one that matters most and was consistently the most challenging - was figuring out what the product backlog should be.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 10, 2008
I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. For more on continuous deployment, see Just-in-time Scalability.
Startup Lessons Learned
DECEMBER 6, 2008
Lessons Learned by Eric Ries Saturday, December 6, 2008 The four kinds of work, and how to get them done: part three Those startups that manage to build a product people want have to deal with the consequences of that success. And still being a startup means continuing to innovate as well as keep the lights on.
Startup Lessons Learned
SEPTEMBER 15, 2008
The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. My belief is that these lean startups will achieve dramatically lower development costs, faster time to market, and higher quality products in the years to come. No more, no less.
Startup Lessons Learned
APRIL 9, 2009
But that team may also include product marketers or other in-house customers who can give insight into the impact that solution trade-offs might have on customers. Its not good enough to hit product milestones and conduct usability tests. Metrics are people too" is a reminder I constantly needed when I was a manager.
Startup Lessons Learned
SEPTEMBER 22, 2008
Heres something I can relate to: We used assembla for subversion, scrums, milestones, wikis, and for general organizational purposes. Scrum reports would come in once a month, nobody was actually responsible for anything. While simple, it is easy to manage. Case Study: Continuous deployment makes releases n.
Expert insights. Personalized for you.
158 
Let's personalize your content