Startup Lessons Learned

OCTOBER 20, 2008

When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JUNE 17, 2010

But according to the theory, this should have been covered by the various specs and documentation we were rigorous about producing. Instead, we spent time making sure the exact behavior of the tools were well documented – by engineers, naturally. Case Study: Continuous deployment makes releases n. Expo SF (May.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

AUGUST 8, 2009

We owe a lot to this seminal document. There's lots of information about performance and metrics out there, as well as a peer expectation that being concerned about those things is an important part of being a competent engineer. Case Study: Continuous deployment makes releases n. Expo SF (May.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

AUGUST 16, 2010

Designed for large businesses, the channels let a company share several types of documents, brand the channel with their own design elements, and then include display advertising, contest promotions, blog aggregation, social media integration and metrics reporting. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 5, 2008

You also need to know what each one cares about, which metrics they look at (or studiously ignore). Education Guideline Book (1st Edition) Sep 2006 View SlideShare document or Upload your own. Case Study: Continuous deployment makes releases n. What are the job titles of the people you need to convince? Expo SF (May.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

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. Continuous deployment: A key component of speed is to keep pushing out work.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

NOVEMBER 13, 2008

Each five whys email is a teaching document. We had made so many improvements to our tools and processes for deployment, that it was pretty hard to take the site down. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. Now, everyone is learning together - about your product, process, and team.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

MARCH 27, 2009

In fact, every single lean transformation documented in books like Lean Thinking took place in the midst of serious external threats. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Expo SF (May.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

APRIL 7, 2010

At least, not in the traditional sense of trying to squeeze every tenth of a point out of a conversion metric or landing page. Even if it shows improvement in some micro metric, does that invalidate the overall design? That was evident in the metrics and in the in-person usability tests. Let me illustrate.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

DECEMBER 6, 2008

The advantages of cross-functional teams are well documented, and for a thorough treatment I recommend the theory in the second half of Agile Software Development with Scrum. Case Study: Continuous deployment makes releases n. I want to focus here on one particular strength: the ability to operate semi-autonomously.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

JANUARY 12, 2009

And I think a bad choice, a bad library, a horrible API, lack of documentation etc. You forgot to mention how awesome the documentation on php.net is. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 11, 2009

I offered an educated opinion about the travesty called "profit based pricing" that the former "community manager" actually fabricated documents as the basis to forum ban me and threatened to permanently ban me as a means to censor the information I sought to share. Case Study: Continuous deployment makes releases n.

Community 158

Community Management Lean Software Review 158