One of the key pillars of Agile is trusting teams to self-organise. In practice, this often looks like teams picking their own tools to use. While it might sound like a scary, messy concept, if you have good talent they’ll be motivated to stay organised and on track with whatever solution they choose - or roll over to a better one when they find it.
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.
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.
Developing your own app is an important thing to get right, whether it’s for use within your own business, client-facing, or for the general public. One of the first decisions to make when developing an app is the choice whether to develop for the browser (web app), or for native use (downloaded to computer or mobile).
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.
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.