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.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

SEPTEMBER 15, 2008

I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. I also owe a great debt to Kent Beck, whose Extreme Programming Explained: Embrace Change was my first introduction to this kind of thinking. (So No more, no less. September 15, 2008 9:19 PM James said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

DECEMBER 6, 2008

When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. At IMVU, we found 60 days was just about right. Amazon PostRank

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

OCTOBER 5, 2008

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. Labels: product development 8comments: Vincent van Wylick said.

San Francisco 158

San Francisco Management Software Review Product 158

adam.heroku.com

MAY 18, 2012

Everyone has to be a generalist and able to work on any kind of problem - specialists will be (at best) somewhat bored and (at worst) highly distracting because they want to steer product development into whatever realm they specialize in. The same principle holds for scaling a development organization. Stage 2: The first hires.

Developer 92

Developer Database Architecture API 92

ctotodevelopers.blogspot.com

JULY 11, 2012

Shifting to a Market, Program, and Platform Organization. agile software development. (46). product management. (23). Simple Agile Product Development. How to Kill Projects and Develop Agile Programs Pa. Trying to Develop a Death Star or a Flux Capacitor. Keys to Successful Product Definition.

Agile 40

Agile Architecture Offshore Software Developers 40