Avoiding a Leaky Scope Bucket

July 1, 2014

There’s a hole in the bucket, dear Liza, dear Liza,
There’s a hole in the bucket, dear Liza, a hole.
– children’s song, Bergliederbüchlein (c 1700)

In my prior article, I introduced the concept of a scope bucket to explain the concept of project scope to your stakeholders.  In this article, I continue the theme with some tips for managing and delivering the scope in your project scope bucket.

Read more



Open Group Boston 2014

May 28, 2014

We are happy to announce that we will be presenting again at the Open Group Conference, this year in Beantown, July 21-22. We will be presenting in the Health Care track with a colleague, Al Zannini, Director of Architecture and Design at Blue Cross Blue Shield of RI. Al and I will be sharing our journey to re-launch an Enterprise and Solution architecture capability, but more on that later… Read more



A Bucket of Scope

May 13, 2014

An architect relies on a clear understanding of scope.  In prior articles we have discussed the business context diagram, a great tool for establishing solution scope.  We also provided a technique for setting expectations regarding the scope of architecture activities.  In this article, I intend to expand on the importance of understanding (or establishing, if you are in a project lead role) the scope of a project.

Read more



Identify Indirect Stakeholders with System Context Diagrams

April 16, 2014

A Systems Flow consultant has skills that tend to fall in the triangle of technical, business and organizational excellence. One common and repetitive case of project dysfunction where this overlap brings real benefits is that of the “Operational Business Stakeholders Missing from Business Requirements.” Here’s how it usually goes:

  1. Architect is engaged to design project’s solution architecture (using the Investigative Architecture™ method)
  2. He/she is provided business requirements to review and comment on, to ensure they are fit for high-level design
  3. The requirements (hopefully) clearly state the end-user and product/service-centric objectives
  4. But how the end-users and the new/enhanced product or service will be supported operationally is completely missing
    Read more


Next Page »