Sanjay V Sharma

It is common for a software product to transition from one development team to another during its lifetime. Different stages of the product may call for a different type of development team: a consultancy to build the initial version, a solo  freelance developer  to maintain it, an in-house team to bring it to scale, or a professional designer to add some “pop”. Despite how often this occurs, many non-technical founders and product owners find themselves unprepared and scrambling when the time comes to bring on the next team. This often results in an inability for the new team to make fast progress, wasted time, and frustration for everyone involved. If this sounds like it could be you, either now or in the future, then you should be somewhat concerned. Luckily, we are going to walk through the steps you can take to prepare for this eventuality and make the transition as smooth as possible. Passing The Torch: Onboarding A New Development Team In this article, I will provide yo...

One of the most amazing things about  working in software development  is the ability to work in many different industries - especially if you’re a consultant. Most software development skills you learn while working within one industry are directly transferable to any number of other industries, companies, projects, and niches. I’m speaking about topics like database design,  design patterns ,  GUI layouts , event management, etc. Then, of course, there are topics specific to one particular industry, company, or project. SME Meets IT, Knowledge Transfer Begins This is where the Subject Matter Expert (SME) comes in. A SME will typically be very involved in the design stage of the project. The SME has been working within the industry for a long period of time, knows the lingo, and understands the business logic behind the coding. The SME may have some understanding of software development, but this is not necessary for the project to succeed. For many projects, unless...