Tech Entrepreneurs - Problem of the CTO

Focus on the development process

The biggest problem is not money or resources, it is lack of knowledge in undertaking the development process. Effort should be focused on creating an "open-source" development process for web-start-ups with a complete series of artifacts for them. Most web-start-ups that get past the concept phase, fail not due to lack of resources, rather they are unable to use the resources they have effectively. Most software projects are problematic, and for start-ups the problem of getting software developed in a efficient, painless way is a major problem. Little time or effort is spent in the specification phase and hence what is developed is often not what is required. We should develop an open-source framework which guides the development process.

How will your concept support web entrepreneurship?

Entrepreneurs will have a proven process to follow, which will allow them to reliably take thier concept through to creation. This will allow them to focus more on the business and remove uncertainty and risk from the "creation" phase.

What kinds of resources will be needed to get this concept off the ground and scale it?

WIll need expereinced consultants and entrepreneurs who have worked with the software and business development processes. Large technology consultancies compaines like IBM, Accenture etc might want to collaborate as they have already a large library of artifacts that would be very useful to the entrepreneur. These large organizations might also fund such an innitiative as it gives them credibility in the market and brings them very close to the "innovation" happening in the UK and elsewhere.

Interested, register at http://opencto.com

How could we get started?

A simple concept website (launched currently at http://opencto.com) and the structure of an open-source project would be needed and a comitte of credible industry leaders who could apprach other thought leaders and eperienced entrepreneurs. This committe with thier advisors would need to establish a roadmap and in a co-ordinated fashion start the collation of information, which will lead to the establishment of a number of artifacts and processes that entrepreneurs can later leverage. The goal is to create a standardized set of development processes and documents for all to share.

Comments

Post a Comment

Please post your comments, I am interested in your views

Popular posts from this blog

The pitfalls of share options in the technology startup

Draft 1 PLEASE NOTE: I  am a simple engineer and this document should not be taken as legal advice in any way whatsoever.  Please feel free to comment or relate your stories here. All feedback is more than welcome Over the last few weeks I have been involved in trying to get a fair outcome for some options that I have in one of the many startups I have worked with over the years. As I continue to push my case forward I thought I would write some thoughts whilst fresh in my mind.  Many of us are attracted to startups due to the promise of shares or share options in the company we are joining. Many people work at reduced rates or no pay in exchange for these contracts, with the hope that one day they will materialise into some value for us. For startup companies, options are a vital currency. Initially cash is tight and using options is a means to attract the right people to help launch the company or take it to the next stage in it's evolution.  In recent weeks, I hav...
Read more

Hire for Engineers not for Frameworks

I have been faced with hiring great engineering teams on a number of occasions, I am constantly amazed at home many hiring managers and recruiters seem to focus on particular technologies and experience in those technologies. My experience has taught me to hire engineers and I have always viewed the technology as a secondary consideration. I always focuses on a grasp of engineering fundamentals and not on information about some current or past technology. In our current world these technologies are out of date by the time the ink on the contract is dry. Recently, I was approached by a leading company for a very senior role. The in-house recruiter laid on his wonderful resume with world leading software companies before affording me the chance to explain my career-to-date. He then proceeded to ask me a number of questions on specific Java libraries and how they were used. This is all information that is readily available on reference sites and in API documentation and does not ...
Read more

Insights & Suggestions For Effective Software development

I decided to note a few observations on software development based on my experiences with a number of clients over a long career, this is work in progress and would appreciate any further input or comments. Topics Data science needs systematic approach Without Specification you are in trouble Interview for excellence Agile does not mean "do nothing" Devops first is not always productive Too many resources is as bad, or worse than too little Design before Develop, before Deploy 1. Data Science needs a `Systematic Approach` We live in a `Data Science` age, it's a buzz word. We have always had data science in some form or another, it's just that the availability, techniques, compute power and volume has exploded over the last few years. Principles are not new, they are standard engineering practises, however, in the new generation of `Data Science` these standard practises are often overlooked. Here are some general rules-of-thumb I have noted down : It makes no sense to...
Read more