Executive Update

Project Start Architecture: Part I -- An Effective Way to Translate EA into Projects

Posted April 7, 2010 | Technology |

Many enterprise architecture (EA) departments struggle with the transition of EA to projects. The issue is how to make sure that EA deliverables are actually used. The idea is simple: project start architecture (PSA) provides a relevant summary of EA artifacts to projects. The value of the PSA is to ensure that the results of each project will adhere to the overall architecture and blend with the IT landscape.

About The Author
Paul Teeuwen
Paul Teeuwen is an independent consultant based in the Netherlands. He focuses on advising large international clients about IT strategy and architecture. Mr. Teeuwen previously worked for Nolan, Norton & Co., the consulting firm of Cutter Fellow Richard L. Nolan. His thinking is based on the Nolan Stages Theory, which guides the sequence of IT improvement projects in a large firm. Clients have included a wide range of banks and government… Read More
Tracey Berg
Robbert van Alen
Robbert van Alen is a practitioner and management consultant in project, program, and portfolio management. His focus is on organizational maturity and business case management. Since 1994, Mr. van Alen has worked for Sogeti Nederland B.V., for which he has been involved with various organizations in government, finance, retail, and transportation. He is a professor at the first Dutch Master of Project Management program at Hogeschool Utrecht… Read More
Joost Luijpers
Don’t have a login? Make one! It’s free and gives you access to all Cutter research.