Stakeholder Onion Diagrams

"A project plan, according to the Project Management Body of Knowledge, is: "...a formal, approved document used to guide both project execution and project control. The primary uses of the project plan are to document planning assumptions and decisions, facilitate communication among stakeholders, and document approved scope, cost, and schedule baselines. A project plan may be summarized or detailed." ...
The objective of a project plan is to define the approach to be used by the Project team to deliver the intended project management scope of the project.
At a minimum, a project plan answers basic questions about the project:
Why? - What is the problem or value proposition addressed by the project? Why is it being sponsored?
What? - What is the work that will be performed on the project? What are the major products/ deliverables?
Who? - Who will be involved and what will be their responsibilities within the project? How will they be organized?
When? - What is the project timeline and when will particularly meaningful points, referred to as milestones, be complete?" [Project plan. Wikipedia]
The timeline diagram example "New business project plan" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Timeline Diagrams solution from the Management area of ConceptDraw Solution Park.

This enterprise architecture diagram sample was redesigned from the illustration of the NIH Enterprise Architecture website. [enterprisearchitecture.nih.gov/ Pages/ Framework.aspx]
"Enterprise architecture is a comprehensive framework used to manage and align an organization's Information Technology (IT) assets, people, operations, and projects with its operational characteristics. In other words, the enterprise architecture defines how information and technology will support the business operations and provide benefit for the business.
It illustrates the organization’s core mission, each component critical to performing that mission, and how each of these components is interrelated. These components include:
(1) Guiding principles,
(2) Organization structure,
(3) Business processes,
(4) People or stakeholders,
(5) Applications, data, and infrastructure,
(6) Technologies upon which networks, applications and systems are built.
Guiding principles, organization structure, business processes, and people don’t sound very technical. That’s because enterprise architecture is about more than technology. It is about the entire organization (or enterprise) and identifying all of the bits and pieces that make the organization work." [enterprisearchitecture.nih.gov/ Pages/ what.aspx]
The example "NIH IT enterprise architecture framework" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Enterprise Architecture Diagrams solution from the Management area of ConceptDraw Solution Park.

The cycle diagram sample was created on the base of the figure illustrating the webpage "2. POLICY & STRATEGY" of "Scottish Police College Primary Inspection 2006: A Report by Her Majesty's Inspectorate of Constabulary" from the Scottish Government website.
"Strategic Planning.
2.1 The planning process for the College currently follows a structured approach, starting in April and extending through the financial year. The planning cycle is illustrated in figure 2. ...
2.2 The College recognises the need to consult with its customers and stakeholders in the process of setting objectives and directing the training programme. The planning cycle to date refers to force visits, environmental scanning, the course planning process which involves consultation with all forces and other common police services, as well as to a survey of external providers.
2.3 The information from consultation feeds into an EFQM framework from which the College has identified four key policies, namely:
(1) developing and delivering quality training;
(2) developing our people through lifelong learning;
(3) continuous improvement of our service; and
(4) embracing the changing environment.
2.4 The objectives set at divisional level are designed to contribute to delivering these policies. HMIC found that whilst the selected objectives were presented in line with the structure, not all could be considered to meet SMART (Specific, Measurable, Achievable, Relevant and Timed) criteria. This failure indicates that while the process appears suitably structured to deliver a robust result, some of those involved could perhaps have a better understanding of the process." [scotland.gov.uk/ Publications/ 2007/ 02/ 15134652/ 8]
The cycle diagram example "Strategic planning" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Target and Circular Diagrams solution from the Marketing area of ConceptDraw Solution Park.
www.conceptdraw.com/ solution-park/ marketing-target-and-circular-diagrams