Let’s say you’re dealing with a software development project. You’re trying to develop an app or any other software product. Here’s how the story usually goes:
Your project is approved. Check.
You’ve assembled your development team. Check.
You’ve allocated your Product Design budget… Have you?
While working in various IT projects I realized that regardless of all these ‘lean’ product development movements, many companies still encounter major issues in terms of product validation. In other words - it is hard for people to understand if the product they develop is what the market desires.
To help you with your validation efforts, I’d like to give you an inside look into the day-by-day product validation process for a live product that we have worked out with one of our clients. Let’s start by answering the fundamental question: What is product validation?
Being a CTO (Chief Technology Officer) takes insight and vision, in technology and business alike. Part manager, part software engineer and part entrepreneur, the CTO can benefit from a wide range of sources to brush up both on the newest developments in tech and to shape the software philosophy of the company.
We know it might be challenging to find useful reading material, or a strong starting point for newly-appointed CTOs - which is why we’ve created this list of must-read books for CTOs. Let’s begin!
They say that a job well begun is half done. Software development projects are no different.
Each software development project starts with a project kickoff. My work at STX Next involves quite a few of those, so today I’d like to share what you can do to ensure your kickoff is as productive as possible. I've also included a sample kickoff agenda and the checklist I use to measure kickoff success.