To be successful, a company needs to become an agile enterprise. In this article Dragan Jojic explores “the agility challenge”: A company where employees are able to sense and respond to external inputs without managers having to tell them what to do, know what they are trying to achieve, understand why, be able to decide by themselves how to best do it and genuinely care that it gets done.
This is the last of three articles exploring the culture and practices that makes Menlo Innovations such a joyous workplace. This article examines their approach to user experience and requirements - a set of practices they call High Tech Anthropology®
Creating digital products is different from building traditional telco products: the uncertainty is much higher, the way of creating value for the customer is totally different and lifecycle is much faster says Susana Jurado Apruzzese. Telefónica adapted Lean Startup to their processes, culture and organization to make it work.
Gerald Weinberg shares his observations of the agile movement "where it came from, where it is now, and where it's going" in the book Agile Impressions.
This article shows how to prioritize your backlog using an enhanced quality model using Maslow’s hierarchy of human needs. Search for most valuable features using the Need-Feature-Capability matrix 2
The book Scenario-Focused Engineering describes a customer-centric lean and agile approach for developing and delivering software-based products using a fast feedback cycle.
A mix of existing robust hardware development ideas, plus a few newly taken from Agile software are being used now by real teams, even to get around or through the challenge of doing fast iterations.
The book "Agile! The Good, the Hype and the Ugly" provides a review of agile principles, techniques and tools. It explores the agile methods Extreme Programming, Lean Software, Scrum and Crystal. 4
The three-horizons model explains how companies can work on the right things to ensure sustainable growth. Visual portfolio management can integrate the different types of work into a coherent system. 2
This is a case story of how a supplier cooperated with a client to develop a huge project in an Agile way, by cutting it into smaller pieces and prepare a matching contract based on mutual trust.
One of the largest areas of development waste are poorly formed requirements. This post presents a very simple technique that can be applied to all user stories to improve quality and reduce waste. 3
In an interview with InfoQ Karl Scotland explains the kanban canvas and explores how it can be used to create shared insights and decide upon the approach to intervene in organizations. 1