Learning Agile

Streszczenie książki

Andrew Stellman is a developer, architect, speaker, project manager, and agile coach. He has over two decades of experience in the software industry. His clients include companies, corporations, and schools, like Microsoft, Bank of America, and MIT.

The solution to our earlier challenges is now clear: we should have involved customers earlier by providing them with the software to gather feedback and make adjustments, saving time, effort, and money. However, changing course mid-project is difficult and often met with resistance, especially when it feels like progress is being undone. The key lies in mindset—accepting that reassessing assumptions is essential to building valuable software and that pivoting, though frustrating, is better than delivering an ineffective product. Empathy also plays a role; customers rarely mislead intentionally, and acknowledging their efforts to correct mistakes can save time in the long run. Applying agile principles to our e-book reader project highlights the importance of adaptability. The initial failure stemmed from the lack of an industry-standard format, which was unavoidable at the time. By adopting an agile approach with iterative sprints, frequent feedback, and flexibility to incorporate new standards, the project could have evolved successfully. Unlike the rigid waterfall method, agile ensures continuous user engagement and responsiveness to changing needs, delivering functional, relevant software. Our primary mistake was resisting change, clinging to an outdated plan, and neglecting the flexibility required for iterative development. Reflecting on the evolution of e-readers, which took over a decade to mature, underscores the importance of adaptability. Early devices lacked the sophistication of today’s models, and a traditional approach to software development would have hindered their progress. A hypothetical scenario of a company using a waterfall process to develop an e-reader illustrates this point: despite meeting all initial specifications, the final product failed due to outdated features and incompatibility with new standards. This highlights the necessity of embracing change and iterative processes to create software that meets real-world demands.

Aby przeczytać resztę książki, możesz pobrać Bitely