For a small business with high dependence on customized or proprietary software and online tools, a good software developer can be a lifeline to better efficiency, growing\u00a0revenue and increased profit.<\/p>\n
But what happens when that software developer leaves the company?<\/p>\n
For some companies this can be a disaster.<\/p>\n
What were simple requests\u00a0before, now become profoundly difficult obstacles. Making basic\u00a0website updates, adjusting the troublesome customer’s account, or running the custom reports for the CEO now become almost impossible.<\/p>\n
It doesn’t have to be like that.<\/p>\n
With some basic planning, standards and consistent communication \u00a0you, the business owner or executive, can mitigate much\u00a0of this pain. Here are 5 ways to start.<\/p>\n
Make sure any developer that does work for you is keeping the software files for all projects in a source code repository that you own and control. It’s like a library for the files that make up your delivered software.<\/p>\n
The software that is created for your business should be treated like an asset so as to maximize it’s long term value return to the company. A good code repository helps protect that asset.<\/p>\n
There are many programs that act as software source code repositories. Systems such as\u00a0Atlasssian’s BitBucket<\/a>\u00a0or\u00a0Github<\/a>\u00a0are popular, loaded with features, inexpensive and conveniently online. You can also download and use local versions of systems such as\u00a0SVN<\/a>\u00a0or\u00a0Git<\/a>\u00a0for the more technically capable.<\/p>\n These systems facilitate modern, flexible source code control with many integration options for other parts of the software development and delivery eco-system.<\/p>\n If your software developer insists on keeping code on their local hard drive, its time to find another software developer. You can’t afford to have your software walking out the door when the resource decides to leave.<\/p>\n A ticketing system or issue tracking system is a tool to document\u00a0and\u00a0clearly divide units of requested work when used correctly. To a small business this may seem like a lot of overhead. However, a ticket tracking system is a way to more clearly communicate what needs to be done, who is doing it and track progress over time, and potentially across multiple developers.<\/p>\n Online systems such as\u00a0Jira<\/a>, Fogbugz<\/a> or Trac<\/a>\u00a0can be used at a reasonable cost. Also\u00a0Mashable<\/a> has a longer list<\/a>\u00a0of issue trackers you can use.<\/p>\n A ticketing system is also a way to maintain accountability and communication regarding specific tasks and requests. Many of the systems allow you to pull reports and see how things are going, how a project is progressing and measure quality metrics for your code.<\/p>\n Every small business should have a basic diagram\u00a0(could be paper or electronic) that shows where things are. Items such as key servers, locations, databases, internal tools should be shown along with what relationships there are.<\/p>\n As changes are made and systems are added or migrated, update the diagrams as part of your standard procedures. Review it from time to time to validate its accuracy. Adjust it as needed.<\/p>\n A simple diagram that shows where and how your systems\u00a0link together can save\u00a0hours of time in misunderstandings or unclear documentation. It can also make on-boarding of a new software developer or system administrator much easier and faster.<\/p>\n A developer will need access to systems to update code, release software and make fixes and changes.<\/p>\n The small business should own all the passwords and control of them. Allowing the software developer to be the only one who knows the admin passwords is a recipe for disaster.<\/p>\n In order to track a large number of\u00a0passwords I recommend using tools such as Lastpass<\/a> or 1password<\/a>. These tools allow tracking of passwords and provide online and mobile access for convenience. Alternatively you could store passwords in an encrypted file or disk volume (as long as it is backed up elsewhere) with the operating system you use.<\/p>\n The bottom line is that, as the owner, you need to be able to access these systems when the developer is no longer available for what ever reason. Tracking the passwords yourself helps guarantee that access.<\/p>\n This is perhaps the simplest\u00a0but most neglected area.<\/p>\n Business owners and executives get busy. It’s easy to forego the regular, sustained communication that facilitate shared understanding of a software project. Neglecting this communication\u00a0will cost you when it comes time to transition to a new developer.<\/p>\n Setup and keep a regular meeting schedule to discuss issues, progress, and review updates. This should be done at least a couple of times per week, or daily if possible. Once you get in the groove, these meetings are usually short.<\/p>\n Many teams who use the Agile methodology<\/a> have stand-up meetings<\/a> every day to discuss progress, issues and immediate plans. This quick, consistent communication helps educate you, as the owner of the software, and educate the developer to your expectations and needs and the systems evolve.<\/p>\n Force yourself to meet and talk. Ask questions and get answers without technical jargon and acronym soup. Any developer worth their salt can explain what they are doing, and show examples in terms any businesses person can understand. If they can’t, its time to upgrade.<\/p>\n The departure of your software developer can bring about loads of pain without proper preparation and planning. \u00a0But with preparation you can facilitate smoother transitions between developers and lessen your\u00a0companies downside risk.<\/p>\n","protected":false},"excerpt":{"rendered":" For a small business with high dependence on customized or proprietary software and online tools, a good software developer can be a lifeline to better efficiency, growing\u00a0revenue and increased profit. But what happens when that software developer leaves the company? For some companies this can be a disaster. What were simple requests\u00a0before, now become profoundly … Continue reading 5 ways a small business can protect itself from losing the software developer<\/span> 2. Use ticketing or issue tracking<\/h2>\n
3. Keep systems and software diagrams<\/h2>\n
4. Track passwords and access<\/h2>\n
5. Maintain regular communication<\/h2>\n
Summary<\/h2>\n