The Startup Magazine

APRIL 11, 2019

All of us know in software companies that scrum is the most significant agile methodology for handling software projects. In spite of its well-known advantages (flexibility, quick feedbacks, adaptability and better communication), we might be uncertain whether to use this framework or follow a traditional way for the development.

SCRUM 117

SCRUM Software Review Technical Review Framework 117

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. We''ve had to design and implement training programs to help on-board people to our culture and technology.

Lean 167

Lean Startup Software Engineering Agile 167

mashable.com

MAY 9, 2011

With development teams often based around the world, being the center of communication and progress can either lead to a tremendously successful strategy or a bottleneck that can slow down an entire company. Hire someone well-versed in communication between developers, customers and team members. Jesse Davis , Entrustet.

CTO Hire 73

CTO Hire Fractional CTO CTO Technical Review 73

www.readwriteweb.com

OCTOBER 7, 2007

These serve to ensure that everyone who ends up on the development team knows what the system is for. More than one person can review it, but only one person can author. My experience says that if the development team relies on mockups and documents created by customers then the team and the project are in a real trouble.

Web 40

Web AJAX Software Review Development Team Review 40

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.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

NOVEMBER 29, 2008

If done right, a programming interview serves two purposes simultaneously. 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.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

OCTOBER 20, 2008

When I was working my first programming jobs, I was introduced to the following maxim: "time, quality, money - pick two." 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?

Software Review 164

Software Review Engineer Management Technical Review 164

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.

San Francisco 158

San Francisco Management Software Review Product 158

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. Amazon PostRank

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

DECEMBER 7, 2008

TDD plus continuous integration works as a natural feedback loop: if the team is working "too fast" to produce quality code reliably, tests fail, which requires the team to slow down and fix them. Use pair programming and collective code ownership. Pair programming is the most radical, but also the most helpful.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

JUNE 8, 2009

You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. I suddenly lose my ability to judge if our marketing programs are being effective. So the product development team was busy creating lots of split-tests for lots of hypotheses. Use pilot programs.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

NOVEMBER 17, 2008

Now its time to start to think seriously about how to find a repeatable and scalable sales process, how to position and market the product, and how to build a product development team that can turn an early product into a Whole Product. What is customer development? Using AdWords to assess demand for your new online.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

APRIL 26, 2009

The idea of leverage is simple: for every ounce of effort your product development team puts into your product, find ways to magnify that effort by getting many other people to invest along with you. That engine of creativity has led to a catalog of something like 2 million virtual goods authored by a hundred thousand developers.

Product Development 88

Product Development Developer San Francisco Product 88

blog.expensify.com

APRIL 24, 2012

But it will definitely raise questions during the phone screen, for reasons that are best explained by simile: Programming with.NET is like cooking in a McDonalds kitchen. My example: I have mainly programmed _by choice_ in Python, Ruby, Scala, Haskell, C# and currently I’m doing Java. It’s so blinded, it’s shocking.

Java 107

Java PHP Software Review Coder 107

sivers.org

JUNE 25, 2010

They log in to translate the documents, one at a time, marking each finished when done, which sends the file back to the company for review.” Also important: Only go for providers who have great reviews from many past customers. Decline bids from providers without many great reviews. The translator rejects or approves.

CTO Hire 84

CTO Hire Hiring Software Review Technical Review 84