Software Development Life Cycle (SDLC)

Software Development Life Cycle (SDLC)
Any best practices for comparing ISO standards for software development?

Top Answer: Sorry, but we do not use ISO standards for software development

Related Tags
What's your philosophy on developer ownership, and how do you instill that in your team?

Top Answer: I push developer ownership very strongly. Ownership begins at the beginning of discussions with product, even before defining. We try to provide insights around what we are looking for and the direction that we are going to take, at least for the engineering leads. When things are more mature, that's when we start pulling in the developers on the team. We explain to each team what we're trying to achieve, and then there's a big push to product. For product, you need to define whys rather than try to bring in a solution right away. You can propose something but don't introduce a solution if you can’t answer the why, because then we can't elaborate or change. We can't know if what we are doing is achieving the goal if you’ve already defined it. That leaves little room for us to do anything.  I've been through phases at a number of companies where QAs were extinct. But when quality assurance is gone, that causes a bottleneck. Then when it goes to product, you create a cycle in which you’re always getting stuck. You can't move forward or move continuously. So much of this process needs to happen beforehand. It could be a matter of just switching our approach, so we make small changes and deploy all the time. Having that continuous deployment means that the developers are in constant communication with UX to understand whether what they did is correct. They’re always talking to product to see if they missed something. Once they are certain, that is where the ownership comes in. They need to be certain that they built something that's reasonably good and is achieving the goal. The developers will move forward, we’ll provide tools, and they will go and deploy. They put their code into production, and monitor to make sure that they deliver the expected value to the customer. And if things don't go perfectly, then we iterate again.

There has been a buzz around Low-code or Zero-code which pitches for building systems without writing code i.e. with the help of configurations, settings and UI based mappings, plug and play of blocks.Though it is not new to me as various CMS and CRM have been existing which offer same but never referred as low-code solutions. What is your take on this proposition? have you implemented any such low-code tool which has reduced development efforts without compromising the expectations from Product and Business?

Top Answer: In the previous company I used to work for, we’d created an ERP only using Amazon Honeycode. We did it in 3-months time and it was the solution we were looking for, since the company was a last mile company with 320+ drivers and 21 staff employees. So the ERP was used in desktop as well as mobile devices. It might not seem that low-code would fulfill a company needs, but it was a solution that worked really well and it provided the results we were expecting.

Related Tags