Find Resources & Connect with members on topics that interest you.

AI - Acquire and Implement

PO - Plan and Organize

DS - Deliver and Support

Please sign in to see your topics.

You must be logged in to join this group.

PO10.5 - Project Scope Statement

This topic is intended to enable collaboration and sharing of information to facilitate a better understanding and approach to implementing this COBIT control objective based on the risk, value and guidance provided by its corresponding control practices.

COBIT Control Objective PO10.5 - Project Scope Statement is contained within Process Popup Manage Projects.

Learn more about COBIT and related publications.

Click “Join This Community” to be able to actively participate in discussions and contribute content. You must be an ISACA member to join this topic. Join ISACA now.

This Topic Has:
7 Members
0 Online
3491 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!

Badge: Energizer

Project Scope Statement

Define and document the nature and scope of the project to confirm and develop amongst stakeholders a common understanding of project scope and how it relates to other projects within the overall IT-enabled investment programme. The definition should be formally approved by the programme and project sponsors before project initiation.

View value and Risk Drivers  help

Hide value and Risk Drivers help

Value Drivers

  • Baseline provided against which the progress and, ultimately, the success of the project can be measured
  • Accountabilities including those of key business stakeholders assigned and clarified
  • Effective use of resources for the projects
  • Preparation of a master project plan facilitated
  Risk Drivers
  • Misunderstanding of project objectives and requirements
  • Failure of projects to meet business and user requirements
  • Misunderstanding of the impact of this project with other related projects

View Control Practices  help

Hide Control Practices  help

  1. Provide to the stakeholders a clear, written statement defining the nature, scope and business benefit of every project to create a common understanding of project scope amongst stakeholders.
  2. Ensure that key stakeholders and programme and project sponsors within the organisation and IT agree upon and accept the requirements for the project, including definition of project success (acceptance) criteria and key performance indicators.
  3. Ensure that the project definition describes the requirements for a project communication plan that identifies internal and external project communications.
  4. With the approval of stakeholders, maintain the project definition throughout the project, reflecting changing requirements.

Discussions: 0 total

Must be a Topic member to contribute

No Results Found

Documents & Publications: 68 total

Must be a Topic member to contribute
View All »
Posted by ISACA 1447 days ago
Posted by ISACA 740 days ago
Posted by ISACA 845 days ago
Posted by ISACA 855 days ago

Events & Online Learning: 13 total

Journal Articles: 232 total

Volume 3, 2107
by Jayakumar Sundaram, CISA, ISO 27001 LA
The SoA is a continuously updated and controlled document that provides an overview of information security implementation.
Volume 6, 2106
by Venkatasubramanian Ramakrishnan, CISM, CRISC, CHFI
Bayesian networks can capture the complex interdependencies among risk factors and can effectively combine data with expert judgment.
Volume 2, 2018
by Ofir Eitan, CISM, CCSK, CTI
In the wake of the Target breach, the threat of cyberattacks using an enterprise’s supply chain as a delivery vector has become a common concern within the information security community.
Volume 2, 2018
by Robert E. Davis, DBA, CISA, CICA
Innovation is the process of transforming an idea or concept into a functional and marketable value proposition reflecting creative opportunity.
Volume 2, 2018
Until a few years ago, many organizations did not adopt new technologies unless they were proven, stabilized and in use.
Volume 2, 2018
by Indrajit Atluri, CRISC, CISM, CISSP, HCISPP, ITILv3
Cyber insurance, along with cyberrisk, has become a very common agenda item on the boardroom discussion list in recent times.

Wikis: 2 total

Blog Posts: 148 total

La Tecnología de la Información (TI), en todas sus áreas (base de datos, seguridad de la información, desarrollo de software, redes, etc.), debe tener como objetivo primario el apoyo a los Procesos del Negocio (PN) de la organización. Sin embargo, es comú...
Posted By : emorro | 0 comments
Have you experienced ransomware attack so far and, if yes, what did you do to resolve? I set up Twitter poll here: It lasts for seven days. Thank you for taking part in the poll.
Posted By : Dragan Pleskonjic | 5 comments
Bitcoin Trade a Bubble! Block Chain Technology Useful .ISACA Members whats your Take on Bitcoin Trade, Is its a bubble that wont last long.Block chain Technology is useful and its continuously growing to as form of secure record  management and secured us...
Posted By : MUGAMBI865 | 1 comments
There is no doubt with our current business environment, we will be experiencing more cyber breaches in the next few months.  The latest threat is an architectural design flaw in newer CPU's.  These design vulnerabilities could allow attackers to intercep...
Posted By : Fred586 | 1 comments
There are some math models for business that MBAs are taught. Just like assembling burgers for fast food or call wait queue management in a call center, vulnerability patching is a time based business opportunity. Leadership can be expected to use this ...
Posted By : Don Turnblade | 1 comments
My personal thoughts after listening to C-level executives at the CxO Roundtable Series sponsored by Intel, IBM, HyTrust & ReedSmith. For an invite, please reach out to me. Data Protection under the GDPR For past few months, I’ve been helping to org...
Posted By : Thomas152 | 1 comments