Design Product Development San Francisco SCRUM 
Startup Lessons Learned
MARCH 16, 2009
XP and Scrum don’t have much to say - they punt. Its by far the hardest part of the puzzle of shipping successful products and both recommend that you get a customer in the room and ask them to clarify what they want as you go. Labels: customer development , product development 8comments: Sarah Milstein said.
Startup Lessons Learned
OCTOBER 5, 2008
These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 15, 2008
The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.
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.
Startup Lessons Learned
JULY 29, 2009
Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.
Startup Lessons Learned
DECEMBER 6, 2008
Lets start with the most important thing you can do to help product teams succeed: make them cross-functional. To begin with, see if you can get designers, programmers, and QA on the same team together. Scrum recommends 30 days; I have worked in one or two-week cycles up to about three months. April 23, 2010 in San Francisco.
Startup Lessons Learned
APRIL 9, 2009
So instead of having sales, marketing, and business development, we have a problem team implementing customer development. And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. link] April 11, 2009 10:24 PM Daniel Prager said.
Expert insights. Personalized for you.
111 
Let's personalize your content