Productivity in software development is typically tricky to measure. Is it how fast your team are doing something? It has been proven time and again that lines of code is a poor measure; are the number of modules an indicator? The degree of module reuse within a project, or from previous projects?
When we talk about wireframes, mock-ups, and prototypes, we are talking about graphical representations of software - how a system will look to end-users - and, in the case of the prototype, how it will work, too. This is generally in the form of an app (whether web, mobile, or desktop), although you might get clever with things like IoT and smart watch displays, too.
The allure of cloud computing isn’t just in its portability – its in the fact that you can wind up saving money on computing infrastructure and resources, too. Azure is Microsoft’s cloud computing platform, akin to Amazon’s AWS. If you are already running MS Office in your organisation, then considering rolling over some functionality to Azure holds quite the allure.
Wouldn’t it be awesome if developers could just code a piece of software perfectly the first time around and there were zero bugs, the software working flawlessly, forever? Development time would be fast and customers would be assured everything would always work.
With so many job titles bandied about these days - tech evangelist, brand warrior, code ninja - it can be difficult to tell what’s a ‘real job’ and what’s simply another name for a job that already exists. Product Manager and Product Owner are two job titles that sound very similar, yet have unique differences.
What a time to be alive! When cars can (almost) drive themselves, our phones can unlock just by showing our face, and Siri can schedule meetings for us… Isn’t life grand? And easy? Machine Learning is seeping into our everyday lives - it’s not just operating behind the scenes in business helping banks spot fraudulent transactions, bolstering against enterprise cybersecurity attacks, and helping allocate and deallocate computing infrastructure for reduced operational costs.
Fixed price contracts can be rather tricky in a Scrum environment. Classic software development and Agile software development are very different from one another, and things that work in one environment don’t necessarily work in another.
Read moreThe simple answer is, yes. Agile teams still need to adhere to the basics of testing, however, their approach allows them to go about it quite differently.
Read more