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?
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.
Kanban, a concept created within Toyota’s Japanese production and manufacturing plant, oddly enough, has been a system that has gone on to take the world by storm. The Kanban card system allows “just in time” tasking; and is comprised of a board made up of cards that are moved along in a left to right fashion. Kanban is a system often utilized in Agile teams to help keep track of software development work, and ensure everyone in the team stays on the same page.
Do you have a task to achieve? There’s an app for that. Kanban software is now widely used in both businesses as well as in people’s personal lives. However, some of these software products are better than others - as is the case with any type of app! Today we outline our top picks for 2020.
Ah, the eternal debate: Agile vs Waterfall, Waterfall vs Agile. When dipping your toes into custom software development you’ll encounter these two terms. They are software development life-cycle models that outline how a project is to be completed.
When engaging a software development services provider, there are many aspects you should consider before signing on the dotted line - to avoid headaches down the track. One such aspect that you really should lockdown is a Service Level Agreement.
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