Use PRINCE2 to Improve the Success of your Enterprise Architecture Project

Can PRINCE2 and Enterprise Architecture (EA) work together? I would think so. In fact, I would say that they can work well with one another. There’re areas of similarities and also areas that PRINCE2 can complement an EA project.

EA projects are after all projects and hence would benefit from using PRINCE2 in managing.

Like any other projects, EA projects are also susceptible to scope creep and for customers new to EA, they typically do not know what to expect out of the project. Or sometimes it is just a matter of differences in expectations.

I believe the following would help add clarity and improve the success rate of EA projects.

1. Product Based Planning
2. Project Product Descriptor and Product Descriptor
3. Managing by Stage

Just by adopting these, quite a fair bit of the common issues encountered in lesser successful projects could be mitigated, if not resolved.

Before the start of the project, it is important to plan and breakdown your products/deliverables. What do you need to produce/develop in order to successfully completed the project. This will set the scope clearly. Anything not within the product breakdown potentially are out of scope.

The Project Product Descriptor and Product Descriptor helps to give clarity to everyone involved in the project. There will be no ambiguity in what qualifies the product as fit for purpose. Customers/users will know what to expect and whether is it what they want/need. No longer do customers and enterprise architects need to argue over what is acceptable or not since the acceptance criteria are mutually discussed and agreed upon.

Lastly, by managing the project in stages, it gives us flexibility and control. Is it practical to plan for anything longer than a year? Or maybe even 9 months? By planning and executing in stages, we have logical breaks to evaluate the viability of the project, to make resource changes and to adapt to the changing environment. Resources are only required in the stages that they are involved instead of the entire project.

And by planning the delivery of products at end of stages, we can logically suspend or end the project.

EA projects can sometime spread over years and one typical grouse is that it takes too long to taste success. By breaking the long period into shorter and more palatable stages whereby quick wins can be demonstrated, this improves the confidence of the customers.

There’re certainly more things that one can adopt from PRINCE2. In fact, if there are no obstacles, one can simply run EA project as PRINCE2 project.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: