L1R2. Carl Kessler & John Sweitzer, Chapter 1, "Outside-in Software Development", IBM Press, 2008

This book discusses the organizational context of design and the business, product management and ecosystem considerations that are completely missing from most design curricula

It focuses on the idea that there are always multiple stakeholders with different goals and constraints -- and the essence of good design is making tradeoffs to find the compromises among them

Don't be put off by the title of this book; the authors are executive-level software development experts at IBM, and the book has much broader applicability than just enterprise software

 

Guide Questions 

  • What does the concept of Outside-in Development mean?
  • What are the key things to consider when building software?
  • How can Outside-in Development be applied to business?

 

4
Average: 4 (1 vote)