Waldemar,
More complicated you say, sure, in essence it is the same good old stuff. Maybe with couple of remarks - in today’s world you have to pay attention to growing complexities of globalization, BPO, multinationals, multiculturalism and so on. A chain is only as strong as its weakest link, nowadays, you can not take lightly any aspect of project management: stakeholders management (matrix organizations, customers, vendors., customer vendors), team management (telecommuting virtual teams all over the globe in different time zones), procurement and vendor management (outsourcing, SaaS), business case and value management (competition is tough - cost savings, value for money, ROI), legal and compliance (numerous data protection laws different from country to country), you name it.
Back to the real life project example - here is an orgchart of SAP project. As you can see it mostly had PRINCE2-compliant structure (Steering Committee = Project Board).
And now the interesting part. Project Management approach was in general following company-wide PRINCE2 standard rather than ASAP. For example:
- There was a project board established with Exec, SS and SU. Project governance (roles and responsibilities, escalation procedures, approval gates etc) mostly was according to PRINCE2
- Product Delivery (work packages authorization, acceptance etc) was following PRINCE2 approach, because organizational processes around vendor management and staffing were also aligned with PRINCE2
- Change Control and Risk Management were based on PRINCE2 approach, because change advisory/approval boards and risk assessment committees within the organization were built in accordance with PRINCE2
- Business Case and Value Management were based on PRINCE2 approach (even though in ASAP you probably find even more detailed information on value management).
At the same time:
- Project phasing (or staging in PRINCE2 terminology) was taken from ASAP (preparation, blueprint, realization …), because it was SAP project, so, it would be impractical not to use ASAP phases
- Particular work packages/tasks (like HW sizing, Interface Inventory, RICEFW design and implementation, Legacy Data Migration etc) were taken from ASAP – again, it was SAP project and we had to deal with Business Process design, RICEF design, data migration etc and PRINCE2 does not bother itself with those details. PRINCE2 also is not concerned with testing strategies, production cutover, end user training, so we used (mostly) ASAP guidelines in those areas
All in all, in my case, ASAP and PRINCE2 coexisted peacefully and complemented each other nicely.
Cheers,
Alexey