All Posts

Parkinson’s Law “Work expands to fill the time available for its completion.” Example: You give someone 7 days to do a 2-day task → they take all 7 days to complete it. Similar to Student Syndrome, it leads to: Inefficient use of time Artificially long durations Resource waste Goldratt’s Theory of Constraints (TOC) Every system has one constraint (bottleneck) that limits performance. Improving that constraint improves the whole system. Connection to Student Syndrome: Student

Key Points Example Purpose Proactively manage expectations and influence. Local residents concerned about night‑time concrete pours. Activities Identify → Plan Engagement → Manage Engagement → Monitor Engagement Stakeholder register prioritises “High Power / High Interest” municipality. Techniques Salience, Power–Interest grid, Stakeholder Cube, Personas Artefacts Stakeholder Register, Engagement Plan, Issue Log Putting It All Together – Mini End‑to‑End Example Scenario: Mid‑

Key Points Example Purpose Obtain goods/services from outside the org. Façade curtain wall via fixed‑price design‑build contract. Activities Plan Procurement → Conduct Procurement → Control Procurement RFP → bidder conferences → technical + commercial evaluation → contract award. Contract Types FP (FFP/FPIF), Cost‑Plus (CPFF/CPIF), T&M, BOOT, etc. FPIF façade with SAR 200 k fee ceiling. Artefacts Procurement Mgmt Plan, SOW, Bid Docs, Agreements, Claims Log What is a Procureme

Key Points Example Purpose Identify, analyse, and prepare for uncertainty (threats & opportunities). Tower‑crane breakdown risk P 30 %, I SAR 1 M; opportunity: bulk steel price drop. Activities Plan Risk → Identify → Qualitative → Quantitative → Plan Responses → Implement Responses → Monitor Risks Monte‑Carlo predicts P90 schedule = 26 months; buy spare crane motor (mitigate). Responses Threats: Avoid, Mitigate, Transfer, Accept  •  Opportunities: Exploit, Enhance, Share, Acc

Key Points Example Purpose Ensure the right info reaches the right people at the right time. Weekly dashboards to sponsors; daily stand‑up on site. Activities Plan Comms → Manage Comms → Monitor Comms Stakeholder A prefers Arabic e‑mail summary; investor wants KPI dashboard. Artefacts Communications Matrix, Performance Reports, Meeting Minutes Formula Channels = n(n‑1)/2. Team = 10 → 45 possible lines. Types of Conflict Resolution Techniques Technique Also Known As Style When

Key Points Example Purpose Get and keep the right people, equipment, materials. Two tower cranes, 180 site staff, outsourced façade crew. Activities Plan → Estimate → Acquire → Develop → Manage → Control Resources RACI for façade package; resource levelling avoids crane clash week 18. Artefacts Resource Mgmt Plan, RACI, Resource Histogram, Team Performance Assessments Theory Maslow, McGregor, Herzberg (tested in People—but apply here).

Key Points Example Purpose Ensure outputs fit purpose and prevent defects. Client demands LEED Gold + 0.01 mm façade tolerance. Activities Plan Quality → Manage Quality (QA) → Control Quality (QC) QA: Audit supplier QA plans; QC: 10 % welds ultrasonic‑tested. Tools/Concepts PDCA, Cost of Quality, Cause‑and‑Effect, Control Charts, Benchmarking, Design for X Artefacts Quality Mgmt Plan, Metrics, Test Reports, Verified Deliverables Seven Basic Quality Tools Name Purpose Cause-an

Schedule Management Key Points Example Purpose Provide a realistic timeline & track slippage. Primavera P6 baseline: 24 months; critical path runs “Foundation → Structure → Façade → Fit‑out → Commission”. Activities Plan → Define → Sequence → Estimate Durations → Develop Schedule → Control Schedule Half‑month look‑ahead meetings; update schedule variance weekly. Calculations Float = LS‑ES; SPI = EV / PV; ES (Earned Schedule). Week 20: EV = SAR 60 M, PV = SAR 75 M SPI = 0.8 (b

Key Points Example Purpose Define what  will be delivered and only that. Hotel must deliver 200 keys, spa, and wellness centre—no casino. Activities Plan Scope → Collect Requirements → Define Scope → Create WBS → Validate Scope → Control Scope Workshops with operator produce 120 user stories; WBS Level‑3 “Spa‑Wet Area‑Tiling”. Artefacts Req. Traceability Matrix, Scope Statement, WBS & Dictionary, Accepted Deliverables, Change Requests Tools Interviews, Focus Groups, Decomposi

The Project Charter is a formal document that authorizes the existence of a project and gives the project manager the authority to apply organizational resources to project activities. It is one of the first documents created in project initiation and serves as a high-level agreement between the project sponsor, key stakeholders, and the project team. Key Elements of a Project Charter Project purpose or justification Measurable project objectives and success criteria High-lev

Servant Leadership A leader who serves the team by removing obstacles, providing resources, and enabling growth, putting the team's needs before their own. Characteristics:  Empowers the team Listen actively Focuses on personal development Build trust and collaboration When to Use: In Agile or self-organizing teams When team motivation and autonomy are priorities To create a safe, supportive environment Example:  As a Scrum Master, you help the team remove blockers (like tool

What is Agile? Agile is a mindset and framework focused on delivering small, incremental value quickly, with continuous customer feedback and flexibility to change. Agile favors collaboration, responding to change, and working solutions over documentation-heavy planning. It is especially suitable for uncertain, fast-changing environments. Agile Manifesto – 4 Core Values Individuals & interactions over processes & tools Working software over comprehensive documentation Custome

Project Integration Project Charter – high‑level scope, ROI, authority. Example : Charter states ROI = 14 % via early hotel opening for Hajj season. Project Management Plan (PMP) – subsidiary plans + baselines. Tip : Show how change control board (CCB) fits inside. Scope Collect Requirements – user stories or requirement traceability matrix. WBS – deliverable‑oriented; level‑2 = “Super‑structure”; level‑3 = “Columns L1–L5”. Validate Scope – joint walk‑downs with client sign‑o

Key Skill What You Need to Know Construction‑site Example Lead a Team Servant leadership, emotional intelligence, situational leadership styles. You notice the concrete crew is behind. Instead of commanding, you ask what’s blocking them. They need an extra pump; you expedite procurement—morale and productivity jump. Build a Shared Understanding Kick‑off workshops, team charters, RACI. In the hotel build, architects thought MEP rough‑ins would wait until level‑2; your Level‑0

Type Description Best For Predictive (Waterfall) Sequential and plan-driven Stable, well-defined projects Iterative Repeated cycles with evolving understanding Complex but scope can be refined Incremental Deliverables released in usable pieces Quick customer value delivery Agile Adaptive and flexible with short cycles High change and uncertainty Hybrid Combination of predictive and agile Mixed environments or complexity Predictive Lifecycle (Traditional / Waterfall) Scope, co

Typically, you need to understand the flow of a project lifecycle Initiation:  The project is formally approved, and high-level objectives are defined (Project Charter). Planning:  The detailed roadmap is created (scope, schedule, budget, risk plans). Execution:  The actual work is performed to create deliverables. Monitoring & Controlling:  This runs at the same time as Execution. It involves tracking progress against the plan and taking corrective action as needed. Closure:

This could assist and guide you to attend and pass the assessment. I personally scored 90% out of 100%. What does the project access level “Archive” mean for a company? (single answer) They can Receive/read mail and updated docs, but not send mail, upload or update docs They can Send/receive mail, receive, upload and update documents They cannot receive mail or updated documents and org not visible in project directory What are the three levels of Preferences available to an

The First thing you want to know is this chapter in PMP. The project lifecycle should be on your mind from the very first official document you receive, which is the Project Charter. You should decided and document in the Project Management Plan before the team begins any work on defining the detailed scope or schedule. Lets know what are the types of Lifecycles, which once is best to chose and why? in detail with an example. Type Description Best For Predictive (Waterfall) S

Project Team , Stakeholder and General Strictly adhere to the PMI code of ethics and professional conduct, alongside general ethical standards, in all project activities. Your suggestions and recommendations must be provided with impartiality and objectivity, free from bias or conflict of interest. Transparency is paramount throughout the entire project lifecycle. Maintain consistent, accurate, and timely communication within your team. Keeping them informed fosters trust, he

It is very import document which shall be prepared and submitted to the High level stakeholders and your management to let them understand how you will manage your project . These documents must be updated periodically when necessary and get a proper approval from your management upon each changes you made. Things to consider while preparing the document and the content must be very clear to the reader. Document Title Document History:  Mention the version of the update, date