Contents
Prologue: What the Mess Is and How We Got into It
The problem we’re trying to solve.
Introduction: What You’re in for When You Read This Book
Intentional business change, banning IT projects, and how they’re two sides of the same coin.
The shift from IT projects to intentional business change starts with redefining shared assumptions, attitudes, and perspectives.
2 The New Business/IT Conversation
Don’t ask about requirements. Ask how business managers want to run their part of the company differently and better.
Agile beats Waterfall for successful project completion. Now, we need to fix Agile so the projects it successfully completes are the right kinds of projects.
IT Operations isn’t a business with internal customers. It’s an integral part of business operations.
Now that you’ve achieved competence at intentional business change, you’ll need to decide what business changes you should achieve intentionally.
Most of the big strategic business threats and opportunities start with newly available technologies. Who better than IT to envision how the business should respond to them.
7 The Seven Change Disciplines
To achieve excellence in conceptualizing, planning, and executing intentional business change, organizations must be skilled at seven disciplines: leadership, business design, technical architecture management, application development or integration and configuration, organizational change management, implementation logistics, and project management. Here’s a quick sketch of each of them.
When it comes to achieving intentional business change, don’t listen to anyone who starts the conversation by saying, “All you gotta do is …”
Glossary: Irreverent Definitions
Because you aren’t an expert until you’re FBC (fully buzzword compliant).