This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Many CEOs of software-enabled businesses call us with a similar concern: Are we getting the right results from our software team? We hear them explain that their current softwaredevelopment is expensive, deliveries are rarely on time, and random bugs appear. What does a business leader do in this situation?
I’ve been having discussions with several people recently about the role of the CTO (ChiefTechnologyOfficer) in very early stage companies. In December 2007, I described how I commonly take on an Acting CTO Role in a Start-up. That’s why Roger Smith puts the focus of the CTO on programming for the earliest stage.
It was like having a bunch of mini- Free Startup CTOConsulting Sessions all in one room. Structure development contracts appropriately or directing the in-house team appropriately. Review the code being built. This is exactly the kind of thing I'm doing as a Part-Time CTO or Technical Advisor for startups.
Specifically, they should know about, and help with: Asking and answering the 53 Questions Developers Should Ask Innovators Knowing when and how to bring on development talent ( Hiring Developers Before Product/Market Fit? , They look at the code produced on a regular basis to ensure that it’s high quality and right for you.
Equity-Only CTO and Equity-Only DevelopersTechnology Roles in Startups Want to Know the Difference Between a CTO and a VP Engineering? Review the code being built. The "Questions" post is probably the most important. Plan for past the initial MVP.
The innovator/developer relationship needs to be a conversation. Still, if you’re a business leader and your developers haven’t asked you these questions, look for a FractionalCTO to help navigate the critical early stage of development. How big is the anticipated development team? Fulfillment?
I just got an email asking about exactly this: I''m with a new company that needs some software built, but doesn''t need (or have the resources for) a large staff of softwaredevelopers. Do not fall into the trap of Startups and a Common Misunderstanding in Agile SoftwareDevelopment. have you seen the offices?)
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content