Writings on building software delivery capabilities and delivering digital & technology outcomes for ambitious organisations.
It’s rare to encounter an organisation where software isn’t an important aspect of their day-to-day operation. Whether it’s a small business with a simple website, an international retailer with an e-commerce store and a Warehouse Management System, or a charity organisation collecting, storing and reporting environmental data, at some point, each of those organisations will need to engage on some level with a piece of software in order to ensure its smooth operation.
Recruiting the right group of people is one of the most important parts of building a top software delivery team. In this article, we take a look at some things you should consider whilst recruiting, and a few things that you should try to avoid.
It’s not a particularly well kept secret that there can be challenges organisations face when offshoring software development, both for greenfield builds and for products running in support and maintenance.
For many organisations with their own software application, whether it be a website, an internal tool or something else entirely, managing said application can be a source of frustration, particularly in the absence of an internal software team.
Code quality is a term that is often thrown around in the software engineering industry. And like the art of coding itself, it is very subjective and its true meaning will differ depending on an individual, or a team’s beliefs. But at its heart most engineers and teams would agree that good quality code is easy to read, well tested, and maintainable in the long term. But how do we achieve this?
Most software systems will suffer from a deterioration of quality over time. Codebases become bloated, software is changed to solve problems nobody knew existed when it was initially written, and the cost of change keeps increasing.
Morale is closely related to job satisfaction. When morale is high, your team is happier, more productive, and more likely to believe in your organisation’s vision. On the flip side, not enough (or any) praise for a job well done, dealing with a difficult clients, or heavy workloads can significantly lessen morale, and sometimes lead to higher employee turnover.
Both words, “agile” and “planning”, mean different things to different people. In this article I hope to provide an overview of agile planning without going into specific implementations like Scrum or Kanban whilst still providing practical advice for any implementation.
It’s a poorly kept secret that increasing levels of responsibility, particularly with knowledge workers, often correlates to an increase in performance.
As software engineers, we’re faced with new problems and challenges every day. No matter how well we know a programming language, how many projects we’ve worked on throughout our careers or how much time we’ve spent creating repeatable solutions to common problems, there will always be something new that requires critical thought.