Up and Running
SEPTEMBER 28, 2015
Kanban: a method used to control production. To get things rolling, we’ll turn to the industrious nation of Japan. The word kanban means “signboard” or “billboard” in Japanese, and it’s a concept most commonly applied to “lean” or “just in time” production. Kanban is a scheduling system for “just in time” production.
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. 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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.
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. Lets start with the most important thing you can do to help product teams succeed: make them cross-functional.
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
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. He wrote it in 2000, and as far as I know has never updated it. Do you have a spec?
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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?
Expert insights. Personalized for you.
60 
Let's personalize your content