Agile Development Team Review San Francisco 
Startup Lessons Learned
FEBRUARY 20, 2009
Take the example of a design team prepping mock-ups for their development team. Give the dev team your very first sketches and let them get started. And over time, the development team may be able to start anticipating your needs. That frees up even more development resources, and so on.
Startup Lessons Learned
JULY 13, 2009
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 5, 2008
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. 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.
Startup Lessons Learned
NOVEMBER 8, 2008
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. Expo SF (May.
Startup Lessons Learned
NOVEMBER 29, 2008
The technical interview is at the heart of these challenges when building a product development team, 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.
Startup Lessons Learned
OCTOBER 20, 2008
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.
Startup Lessons Learned
OCTOBER 16, 2013
One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. The result was a new process of four-week iterative cycles all about throttling new code.
Expert insights. Personalized for you.
161 
Let's personalize your content