Agile Methodology

Warning Signs Your Agile Product Studio is Not Agile After All

Warning Signs Your Agile Product Studio is Not Agile After All

Many people often confuse Agile with Ad-hoc. Or they simply continue to practice traditional project management frameworks such as waterfalls, but use a couple of agile techniques such as daily stand ups and the use post-it notes for brainstorming sessions and call it ‘Agile’. In this post, we talk about what it means to be truly Agile and how to recognise an Agile Design/Tech Studio.

The Near-Perfect Making of an Agile Team

The Near-Perfect Making of an Agile Team

Agile is the most effective and adaptable project methodology to manage constant change. This is because it consists of cross-functional teams working collaboratively in creative and complex environments. Teamwork is essential to delivering great digital products. This collaborative team environment focuses on a “we” rather than an “I” mindset. There is nothing more rewarding than building software that really matters with other like-minded team mates.

What Dual Track Agile is, and how it's done successfully

What Dual Track Agile is, and how it's done successfully

Dual Track Agile is an agile software development and organisational model that separates the effort to discover the best solution from the effort to deliver working software. It consists of two tracks of activity: discovery and delivery. This sees a bringing together of Lean UX and Agile Scrum delivery.

The objective of the discovery track is to validate ideas quickly and efficiently, while the objective of the delivery track is to build, test and deploy production-ready code. By leveraging Dual Track Agile, teams are more focused, reduce their rework and significantly improve their ability to plan while still retaining their agility.