Insufficient requirement gathering or the lack of design are often blamed at the early stage of a software project for all the unexpected changes you have to do down the road. While many are putting lots of energy into predicting the future and are consistently failing in doing it, agile teams don’t waste time and simply get the job done.
Do you feel your head explode each time you need to come up with the final design for a new big feature set? Have you experienced the moments of despair when you watch your design, once looking brilliant on paper, now falling apart after you’ve just started to implement it? Well, that happens when you try to make pigs fly. You’d better embrace Emergent Design.
Many organizations are afraid of designing and running experiments for product development. Validation of the assumption approach has not been widely spread in the industry as a standard. Hypotheses are taken as facts and they are turned into requirements and features without verification. In contrast, other companies seem to be more customer value-oriented and validate […]
Are you bored by hearing about Spotify’s Model, Basecamp’s Shape Up, or Netflix’s “No Rules Rules”? All of them do have something in common. They tailored something unique to match both their ambition and their strengths, while honestly acknowledging their weaknesses.