Book Image

Open Text Metastorm ProVision 6.2 Strategy Implementation

By : Bill Aronson
Book Image

Open Text Metastorm ProVision 6.2 Strategy Implementation

By: Bill Aronson

Overview of this book

Open Text ProVision® (formerly known as Metastorm ProVision®) is an Enterprise Architecture (EA) solution allowing for effective planning and decision making throughout the enterprise. It enables an organization to have a central repository of information about the business, reducing organizational risks and better optimizing business resources. Implemented well, it enables better and more actionable decisions exactly when you need them.This book combines theory and practice to provide a step- by- step guide to building a successful customer- centric model of your business. The approach is simple and down to earth, and along the way, with various real-world examples, you will learn how to make a business case, use a framework, and adopt a methodology with Open Text ProVision®. This book draws on the experience of ProVision® experts around the world. By combining theory with practice from the field you can avoid common mistakes and develop a successful customer centric strategy for implementing ProVision®. Each chapter builds on the previous one to give you the confidence to implement a central repository, dealing with both the technical and human issues that you might face.
Table of Contents (16 chapters)
Open Text Metastorm ProVision® 6.2 Strategy Implementation
Credits
Foreword
About the Author
About the Reviewers
www.PacktPub.com
Preface
References
Index

Agile Management


One of the best governance structures for modeling can be derived from Agile or XP programming. So what is Agile and how did it develop?

When software development began, it copied the project management methodology of engineers. The problem is that their context, however, is completely different. If you are building a bridge, it makes sense to plan the design in great detail, so that when you actually start the work you know exactly what to do and can build it in the least possible time. As much as possible, the thinking is done up front. It's much cheaper to spend a couple of years thinking about the project, than have a lot of equipment on-site, people milling around with nothing to do, while you figure out the next step.

This approach is called the waterfall. Everything cascades down from the previous step, separate streams of work coming together to create a great river.

When the waterfall approach was applied to software development about 70% of projects failed. We covered...