program and portfolio

Things to remember:

* Hierarchy of Strategy:Portfolio:Program:Project:Subproject
* Different goals and different methods of management at different levels of hierarchy
* PMO is a centralization of common skills and resources aimed at optimizing the management of a number of projects.

Things to remember:

* Triple constraint of Time, Scope and Cost with quality being the result.
* A PM who goes from soup to nuts holding the Iron triangle in hand.
* 6 Process areas - IPEMCC (to be covered in more detail later)
* Professional responsibility and adherence to both "Code of Ethics" and "Code of Professional Conduct"
* Risk - it is a risk until it happens. (don't get crazy ideas about asteroids hitting the earth though)
* The PM owns establishing project objectives and accomplishing them. Make them CLEAR and ACHIEVABLE (see the part about PM accomplishing them).

taking from http://zo-d.com/blog/archives/taking-the-pmp-exam.html

PMP notes

This is my personal notes on my way to be certified or not.

I try to un-confuse myself with all this terms;

1. Project scope statements, project statement
2. Traceability matrix - The requirements traceability matrix ties requirements to project objectives, business needs, WBS deliverables, product design, test strategies, and high-level requirements and traces them through to project completion.

3. project scope baseline? - The WBS, approved project scope statement, and WBS dictionary

4. statements is true regarding brainstorming and lateral thinking - alternatives identification techniques, which are a tool and technique of the Define Scope process.

5. You are ready to create the WBS. All of the following are true

• The WBS can be structured using each product as a level-one entry.
• The WBS should be elaborated to a level where costs and schedule are easily estimated. This is known as the work package level.
• Each level of the WBS represents verifiable products or results.

6. poor job of defining the scope, the project costs could increase, there might be rework, and schedule delays might result.

7. Each element in the WBS is assigned a unique identifier. These are collectively known as the code of accounts . Typically, these codes are associated with a corporate chart of accounts and are used to track the costs of the individual work elements in the WBS.

8. The work package level is the lowest level in the WBS and facilitates resource assignment and cost and time estimates.

9. Building a work breakdown structure - must read beb

4.2 Dev Project Management Plan (revisit)

ok, there is money available somewhere, free money look at grant. Look at the grant purpose eg. if it for R&D, commercialization increase contents, uplifting social digital interaction etc.
Wow free money isn't,
well not really free and easy, you got to work on it, first let start by an idea. Will the idea support the grant objective and requirement, will the idea fulfill the existing needs.
Grant sponsors if not a projectize organization, most of them are very much a strong matrix organization.

Than we need to look at the requirements, or study the grant charter, what make them give you this free money and (what area to twist). This is well by filling all forms and in general how we will spend the money to meet the stakeholder requirements. In a way we are creating project requirements.

Than 5.2 Defining Scope, the statement to show the area of grant development, can be the functionality scope, geographical implementation or by target group that will be benefitting the product.

5.3 Create WBS - work breakdown structure is subdividing the project deliverables and project work into smaller more manageable components.

Above are all well under Project Scope Management. Disclaimer this might not be relevant to PMBOK 4th Ed. pg 47, I just type to keep my thinking process going in relation to what I am doing right now.

Key words that might need clarification like
RTM
Statement of Scope
EEF

Direct & Manage project execution

>

4.2 Develop Project Management Plan

Doc arrangement to prepare & integrate subsidiary plan
http://en.wikipedia.org/wiki/Project_management_plan



http://www.pmhut.com/developing-the-project-management-plan




PM Plan constrains;
Time
scope
cost
scope
quality
Risk
HR
Communication

4.1 Develop Project Charter

Does project charter is requirement study?

PC is higher level than Req study. Req study can consist of objective and detail project requrements. PC is like high level of stakeholders agreement of the project objective. It is stakeholder's vision.

Develop Project Charter is the process that formally authorizes a project or project phase.

This process also defines the project need and what the project aims to achieve. Clear descriptions of the project objectives are developed and documented, including why a specific project has been initiated or selected and how the project will address the organization's business need. The customer needs and requirements also get documented in the project charter. A good understanding and documentation of these is essential in deciding the course of the project.

http://www.projectsmart.co.uk/writing-the-project-statement-of-work.html
http://tapuniversity.wordpress.com/2009/09/16/enterprise-environmental-factors/
http://pmtestcenter.com/organizational-process-assets/
http://blog.projectseminars.com/project_seminars/2009/02/creating-a-project-charter.html

PMP Group Processes & Tools

Project Management

Project management is the application of knowledge, skills and techniques to the project activities in order to meet or exceed stakeholers' needs and expectations from a project. It invariably involves balancing competing demands among: .... PMBOK PMI

mimosa pudica

Mimosa pudica (Sensitive Plant) (pudica = shy), is a creeping annual or perennial herb often grown for its curiosity value: the compound leaves fold inward and droop when touched or shaken, re-opening within minutes. The species is native to South America and Central America, but is now a pantropical weed.
http://en.wikipedia.org/wiki/Mimosa_pudica