Quality development takes time. But when you’re short on that particular resource, having a few tricks to speed up the process can be invaluable. Even something as simple as defining your deliverables and sticking to them can help. Nine tech executives from Forbes Technology Council offer their best tips for speeding up the development process when you’re in a pinch.
To paraphrase Kent Beck: software delivers no value apart from runtime. Ideas take physical form in hardware, virtualised only part of the way down, and someone other than the developers makes the ideas manifest. So then: ops folks are the crop’s caretakers; developers design the seeds.
Well, of course this isn’t true. Developers don’t turn pie-in-the-sky maths into socially constructive maths that sysadmins then make useful. No: developers write code that makes things happen. We care about runtime just as much as ops, so we need to know how our software is helping people in reality — and how it can do a better job — in order for us to refine both the ideas and the implementation.
Software development is evolving. Agencies are moving from more traditional development methodologies to those that can more directly tie to strategy and mission success -- thanks, in part, to cloud technology. Waterfall has evolved to agile, and agile to continuous integration/continuous delivery and deployment (CI/CD). DevOps is the next step in that evolution.
DevOps is a buzzed-about industry term, yet many companies are still trying to figure out how to start the journey to a DevOps transformation. Each organization’s journey will be different, but planning and starting the journey always should include assessing the current state of a company’s software delivery process, quantifying the objectives and plotting the “route.” This begins with a discovery process.
As agile development practices mature and DevOps principles infiltrate our corporate cultures, organizations are realizing the distinct opportunity to accelerate software delivery. However, when you speed up any process, immature practice areas such as testing and roadblocks become much more pronounced. It’s the difference between driving over a speed bump at 5 mph vs. 50 mph … at 50 mph, that speed bump is going to be quite jarring.