ctotodevelopers.blogspot.com

JULY 11, 2012

I cover several topics including agile software development, software startups, web 2.0, The implementation and architecture can also suffer if the team under or over invests engineering time, implementation of standards, or testing discipline in the wrong areas. Social, Agile, and Transformation. and business transformation.

Agile 40

Agile Architecture Offshore Software Developers 40

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. And this was a huge product, which took years to develop.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. Startup Lessons Learned - the Conference (April 23.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

NOVEMBER 14, 2013

Jonathan Irwin will lead a workshop on advanced interview skills , including the different kinds of customer interviews, how to develop questions, and how to apply the answers to an actual decision around a product. Often the biggest problem is building up trust between the developers and the people who deploy and operate the systems.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

www.lanceglasser.com

MAY 13, 2012

Metrics for cyclical businesses. Product development. Queuing theory and product development. The Essential Product Investigation Phase Gate. For how to manage that see, for instance, Queuing theory and product development or take some time to investigate resource management tools.)

CTO 40

CTO CTO Hire Technical Review Architecture 40

Startup Lessons Learned

AUGUST 8, 2009

And as Kapor himself points out, the core ideas have even older origins: The Roman architecture critic Vitruvius advanced the notion that well-designed buildings were those which exhibited firmness, commodity, and delight. Yet a huge class of modern software projects are being developed in a very different context.

Software Review 87

Software Review Design Software San Francisco 87

crowdSPRING Blog

OCTOBER 20, 2010

Why marketer misuse of metrics may be an addressable cultural issue – [link]. Legal Contracts for Software Developers Who Hate Contracts (w/free contract template tco use today) – [link]. 30+ Fresh Icon Sets for Web Designers and Developers – [link]. Crowdsourcing Your Marketing Activities – [link].

Social Media 91

Social Media Small Business Design Media 91

Startup Lessons Learned

DECEMBER 28, 2009

Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better. In a successful startup, the development team is also growing.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

JUNE 17, 2010

Even more surprisingly, the engineering team was equally vocal about their contention that adding rounded corners would add weeks of development time to the project, which would have pushed it out way past its hard deadline, effectively killing it. The engineering team wasn’t happy either. The engineering team wasn’t happy either.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

SEPTEMBER 8, 2008

You dont need to invent a new architecture, and you dont need to even build your architecture up-front. You can turn your entire application infrastructure investment into a pay-as-you-go variable cost, and bring new products to market at speeds an order of magnitude faster than just 10 years ago. yeah, its awesome.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. The goal of iterative development is to give us guard rails so we dont veer off to either extreme. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

JUNE 15, 2009

If youre looking for resources on getting started, see " Continuous deployment in 5 easy steps ") The goal of continuous deployment is to help development teams drive waste out of their process by simultaneously reducing the batch size and increasing the tempo of their work. How severely is failure punished?

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

OCTOBER 5, 2009

It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems. Why do they harbor that paranoia?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

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. and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. what happens if we have a pipelined architecture?

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

DECEMBER 7, 2008

I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. When the architecture needs modifying - why do we need a meeting? Building a good application architecture is not just coding. The "just fix it" mentality is counter-productive here. Just change it.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

NOVEMBER 13, 2008

Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. You can even read a cool paper one of our engineers wrote on this approach).

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. Support multiple sharding schemes. Easy to understand.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

FEBRUARY 16, 2009

This is one of the most powerful aspects of web architecture, and it often gets lost in other client-server programming paradigms. The system would monitor their data and if it looked within norms gradually offer the release to a small number of new users (who had no prior expectation of how the product should work).

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

SEPTEMBER 8, 2009

I started my last company with 100% off-shore resources because I could never have completed Customer Development at a reasonable cost of money or regulatory burden had I employed US Citizens. Government IT solutions can be iterative, they don't have to be designed down to the last detail by architecture astronauts before implementation.

DC 90

DC Washington San Francisco SBIR 90

Scalable Startup

FEBRUARY 1, 2013

In the last five years, there’s been this sort of acknowledgment of the consumerization of the enterprise, which is consumer product development, design methods applied to business software, of which SaaS and cloud and all these things are examples. It became very hard to get businesses to adopt new stuff.

Software Review 22

Software Review Startup Venture Capital Stock 22

Startup Lessons Learned

JANUARY 30, 2009

Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. Even a great architecture becomes inflexible.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture. Doesnt that sound good?

San Francisco 79

San Francisco Lean Continuous Deployment DC 79