Manage Learn to apply best practices and optimize your operations.

Outside-in Software Development: A Practical Approach to Building Successful Stakeholder-based Produ

A software development approach that redefines who stakeholders really are, outside-in development (OID) encourages teams to work together to benefit these stakeholders. This free chapter explains the basics of OID.

As a registered member of, you're entitled to a complimentary copy of Chapter 1 of Outside-in Software Development: A Practical Approach to Building Successful Stakeholder-based Products written by Carl Kessler and John Sweitzer and published by IBM Press. " Introducing Outside-in Development" explains the basic elements of outside-in development and how OID is more of a framework and an approach than it is a software development model. Chapter 1 also includes brief outlines of each of the book's chapters.

Outside-in Software Development: A Practical Approach to Building Successful Stakeholder-based Products

Book description:

Build software that delivers maximum business value to every key stakeholder. Imagine your ideal development project. It will deliver exactly what your clients need. It will achieve broad, rapid, enthusiastic adoption. And it will be designed and built by a productive, high-morale team of expert software professionals. Using this book's breakthrough "outside-in" approach to software development, your next project can be that ideal project.

In Outside-in Software Development, two of IBM's most respected software leaders, Carl Kessler and John Sweitzer, show you how to identify the stakeholders who'll determine your project's real value, shape every decision around their real needs, and deliver software that achieves broad, rapid, enthusiastic adoption. The authors present an end-to-end framework and practical implementation techniques any development team can quickly benefit from, regardless of project type or scope. Using their proven approach, you can improve the effectiveness of every client conversation, define priorities with greater visibility and clarity, and make sure all your code delivers maximum business value.

Coverage includes:

  • Understanding your stakeholders and the organizational and business context they operate in.
  • Clarifying the short- and long-term stakeholder goals your project will satisfy.
  • More effectively mapping project expectations to outcomes.
  • Building more "consumable" software: systems that are easier to deploy, use, and support.
  • Continuously enhancing alignment with stakeholder goals.
  • Helping stakeholders manage ongoing change long after you've delivered your product.
  • Mastering the leadership techniques needed to drive outside-in development.

>> Read Chapter 1: Introducing Outside-in Development.

>> Buy the book

Full title is: "Outside-in Software Development: A Practical Approach to Building Successful Stakeholder-based Products" by Carl Kessler and John Sweitzer; Copyright 2008 by International Business Machines Corporation. All rights reserved. Published by IBM Press, September, 2007.; isbn: 0131575511

This was last published in December 2007

Dig Deeper on Software Development Fundamentals



Find more PRO+ content and other member only offers, here.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.