Many Adaptive Path projects have been successes, such as the recent acquisition of Measure Map by Google. But in each successful career happened mistakes that led to an understanding how not to be successful. Leading heads of Adaptive Path give examples how projects went wrong because of their personal mistakes. But, best of all, you also get to hear what they learned from that failure. You can understand by example what they understood by painful failure.
One of the biggest mistakes, already addressed by the existence of this panel, is not allowing people to communicate failure. Where failure is non-existent, less questions are asked. Some failures might even be inevitable, such as bold goals in an early stage of the project. They might never be reached in time, but they help you to get started.
Communication can be a source of mistakes in software projects. There is always the danger of not listening to critics or warnings. But, maybe even worse, you might be listening to the wrong people. Or you might be talking to the wrong people. The panel encourages to cultivate criticism, communicate in the open and identify the true stakeholders before too much work and money has been spent. Furthermore, they arrive at statements some might find too bold for everyday business, but could pay off in the long term: Do not take over every project. Instead, develop guidelines other than earning money that help you decide. You can also try to consider the emotional attachments some stakeholders might have to the status quo.
view more