SOFTWARE QUALITY BOOK EXCERPTS
Outside-in Software Development: A Practical Approach to Building Successful Stakeholder-based Products -- Chapter 1, Introducing Outside-in Development
Carl Kessler and John Sweitzer
12.04.2007
Rating: --- (out of 5)
As a registered member of SearchSoftwareQuality.com, 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.
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. www.ibmpressbooks.com; isbn: 0131575511
|
|
Rate this Tip
|
To rate tips, you must be a member of SearchSoftwareQuality.com.
Register now
to start rating these tips. Log in if you are already a member.
|
 |
 |
| |
RELATED CONTENT
 |
Software Quality Book Excerpts |
|
Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?
|
|
The Software Project Manager's Bridge to Agility: Chapter 5, Scope Management
|
|
Software Security Engineering: A Guide for Project Managers -- Chapter 3, Requirements Engineering for Secure Software
|
|
Requirements Management Using IBM Rational RequisitePro: Chapter 1, Requirements Management
|
|
Implementing ITIL Configuration Management: Chapter 3, Determining Scope, Span and Granularity
|
|
Agile Software Development: The Cooperative Game, 2nd Edition -- Chapter 3, Communicating, Cooperating Teams
|
|
Inherent Quality Simplicity, Section V: The Evolution
|
|
Managing the Test People, Chapter 6: Keeping Your Beast Effective
|
|
Mastering the Requirements Process, 2nd Edition: Chapter 2, The Requirements Process
|
|
Geekonomics: The Real Cost of Insecure Software -- Chapter 1, The Foundation of Civilization
|
|
Methodologies |
|
Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?
|
|
Agile Software Development: The Cooperative Game, 2nd Edition -- Chapter 3, Communicating, Cooperating Teams
|
|
Inherent Quality Simplicity, Section V: The Evolution
|
|
Automated Defect Prevention: Best Practices in Software Management, Chapter 1 -- The Case for Automated Defect Prevention
|
|
The Economics of Open Source Software Development -- Chapter 1, An Introduction
|
|
Model-Driven Software Development: Technology, Engineering, Management -- Chapter 2, MDSD: Basic Ideas and Terminology
|
|
Implementing the IBM Rational Unified Process and Solutions: A Guide to Improving Your Software Development Capability and Maturity -- Chapter 2, Your First Steps
|
|
Scaling Software Agility: Best Practices for Large Enterprises -- Chapter 7, The Essence of Agile
|
|
Real-Life MDA -- Chapter 1, Introduction
|
|
DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.
|
|
|
|
|
|
|
