<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Debra Vo on Medium]]></title>
        <description><![CDATA[Stories by Debra Vo on Medium]]></description>
        <link>https://medium.com/@vothanhthuy2802?source=rss-146e8dd656fb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ADXBP-xCTv-A8wLT0qM_xQ.png</url>
            <title>Stories by Debra Vo on Medium</title>
            <link>https://medium.com/@vothanhthuy2802?source=rss-146e8dd656fb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 06:30:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vothanhthuy2802/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[BUSINESS REVIEW — Case 01: Organizational structure and Hierarchy]]></title>
            <link>https://medium.com/@vothanhthuy2802/business-review-case-01-organizational-structure-and-hierarchy-8f2ca73b5c6e?source=rss-146e8dd656fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f2ca73b5c6e</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[ceo]]></category>
            <dc:creator><![CDATA[Debra Vo]]></dc:creator>
            <pubDate>Tue, 07 Jul 2026 14:47:53 GMT</pubDate>
            <atom:updated>2026-07-07T14:47:53.385Z</atom:updated>
            <content:encoded><![CDATA[<p>I spent a great deal of time considering whether to write the case studies I had promised in my Project Management series. After much deliberation, however, I decided to create a series of articles that I simply call Business Review — a collection of ideas and insights that I find most meaningful and hope to share with anyone interested.</p><p><em>(And between us, I’ve done my best to keep each piece concise and thought-provoking. I wouldn’t want readers to endure the kind of endless theory that might have)</em></p><p>And if you’ve made it through the previous series, you’ve probably realized that managing a project is, at its core, not about following a single, fixed formula — or at least that’s how I see it, as someone who has never been overly devoted to the PMP playbook. What truly matters is the underlying mindset.</p><p>Now, imagine your project as a company, and yourself as its CEO. That shift in perspective opens the door to a broader, more multidimensional view — one that is, inevitably, far more challenging.</p><h3>The Challenge</h3><p>Because an organizational chart represents the distribution of authority and influence, it shapes how people think, feel, and behave — even during a company’s most stable periods. But when that structure changes, or even appears likely to change, the organizational chart can become a source of deep anxiety, particularly in organizations where political dynamics lead employees to worry about their personal standing.</p><p>Let’s see what happened when a highly respected former CEO allowed speculation — if not outright rumors — surrounding the word *reorganization* to linger.</p><p>Several years ago, Carly Fiorina concluded that Hewlett-Packard required a sweeping top-to-bottom transformation. She was firmly convinced that the reorganization had to be carried out with the utmost care and consistency, and she quietly shared that conviction with her senior leadership team.</p><p>Two months before Fiorina formally announced the restructuring, work across the company had already slowed dramatically — or stopped altogether. Employees no longer knew whether to look forward to the changes or fear them, uncertain about their future roles and reporting lines. Managers fared little better, becoming consumed by internal political maneuvering. Contractors also stepped back because no one knew who would ultimately lead which business unit after the reorganization.</p><p>Even after the new organizational structure was officially unveiled, valuable time continued to slip away as employees adjusted to new responsibilities and relationships. In total, the company lost twelve weeks — an entire quarter. Multiply those twelve weeks by payroll costs, then factor in the impact of weakened customer service and slower product innovation, and the financial damage becomes easier to imagine — even before accounting for the enormous opportunity costs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*SB9F-OQE6xnRlbSjm2D5OQ.png" /><figcaption>Generated from ChatGPT</figcaption></figure><h3>A closer look</h3><p>It would be unfair to place the blame entirely on Fiorina. After all, no leader can execute every decision flawlessly. Yet had she developed a more comprehensive plan, made decisions more decisively, and communicated them with greater clarity, HP employees would have understood not only the process itself, but also the rationale behind the change and their place within the future organization — instead of allowing speculation and fear to seep into every corner of the company.</p><p>This illustrates an important leadership principle: when a CEO fails to define the narrative around a reorganization, others inevitably will. Once uncertainty over restructuring is coupled with concerns about job security, reporting relationships, and new ways of working, an entire organization can slow to a standstill.</p><p>Consider another example. The CEO of a 150-person software company realized that a close competitor was steadily gaining ground, making it necessary to redeploy internal resources.</p><p>On a Monday morning, he gathered the entire company and addressed them directly:</p><p>“We’re in a battle for market share. I’m paid to win that battle, and so are you. Right now, however, I don’t believe we’re allocating our resources in the best possible way. That’s why we’re going to reorganize how our teams are structured so we can operate more effectively. Most of you will continue doing the same work, although some of you may report to different managers.” After presenting the new organizational structure, he glanced at his watch “It’s 10:45 a.m. You have until lunchtime to be frustrated — that’s a perfectly normal reaction. Pizza will be served at noon. By 1:00 p.m., we’ll all be back to work in our new roles.”</p><p>He concluded with a simple but powerful message: “I’m not trying to redistribute power. I’m trying to optimize our resources. I don’t want this change to be seen as a political event. I want it to be understood for what it is: a business necessity to remain competitive.”</p><p>I strongly agree with the view that the most effective way for leaders to think about organizational structure is to see it as a dynamic map of responsibilities — one that guides actions and ultimately shapes results. It should serve as <strong>a framework for aligning objectives and deploying resources effectively, </strong>not as an instrument for intimidating employees or diminishing their value.</p><h3>Key takeaways</h3><p>As for Fiorina, the first 48 hours following the announcement should have been treated as a leadership imperative. She could have convened a company-wide meeting and used every available communication channel to explain why the reorganization was necessary. More importantly, rather than allowing employees to focus on who had gained or lost influence, she could have brought everyone together to define clear priorities and concrete objectives for the next 60 days. Doing so would have reinforced a simple message: the new organizational structure existed to enable better execution — not to serve organizational politics.</p><p>Admittedly, every comparison has its limits. Reorganizing a 150-person software company is fundamentally different from restructuring a global enterprise like HP. Yet one principle remains universal: <strong>the value of clear, honest, and decisive communication grows exponentially with organizational scale</strong>. In fact, large organizations can often move through transformation far more quickly when their leaders refuse to inflate political narratives — or allow others to do so.</p><p>I wish you every success!</p><p><em>Reference sources : HBR’s 10 must Reads on Conmunication</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f2ca73b5c6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project management methodology — Part 5 + 6 : Monitor-control and Close the project]]></title>
            <link>https://medium.com/@vothanhthuy2802/project-management-methodology-part-5-6-monitor-control-and-close-the-project-84d4fbdab706?source=rss-146e8dd656fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/84d4fbdab706</guid>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Debra Vo]]></dc:creator>
            <pubDate>Sun, 29 Mar 2026 10:19:35 GMT</pubDate>
            <atom:updated>2026-04-25T09:47:39.851Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BZvFVak2OiCUIUpBb1e6OQ.png" /></figure><p>When all plans begin to fall into place, the project manager (PM) immediately transitions into the Monitoring and Controlling Project Work , which means focusing on tracking, reviewing, and reporting progress to meet the performance objectives defined in the project management plan. In this article, following the same spirit as the previous chapter, I will not go deeply into how to monitor or control each specific plan, but instead I would like to share several points that I believe are fundamental to help you perform this process more effectively. The rest depends on practice, experience, and the insights gained from real-life situations.</p><p><em>The content presented in this article has been simplified based on the author’s personal perspective, and the primary purpose of this write-up is for reference and knowledge sharing only.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_-iEtP8t2C3esdjT3z2dgA.png" /></figure><h3>Monitoring and controlling</h3><p>Evaluate project performance</p><p>Project performance here includes all 10 domains shown in the table above (they can be selected depending on different purposes and audiences). Each domain will have different evaluation needs, and accordingly the factors to be considered are also different.</p><p>For example, for Scope, in order to evaluate and maintain the scope baseline and avoid scope creep, people may look at the Percentage of Work Completed or the number of Change Requests.</p><p>Therefore, measurements are established to support this. Measurement is mainly represented in several forms. These are:</p><p>- <strong>Key performance indicators (KPIs)</strong> : are quantifiable measures used to evaluate the success of a project (usually associated with business objectives).</p><p>- <strong>Metric</strong> : a description of a project or product attribute and how to measure it.</p><p>- <strong>Baseline</strong> : the approved version of a work product used as a basis for comparison to actual results.</p><p>- <strong>Dashboard</strong> : a set of charts and graphs showing progress or performance against important measures of the project.</p><p>Within each type of measurement, there are different indicators and units for measurement. For example, for cost, performance can be measured through indicators such as:</p><p>· <em>Cost variance (CV)</em> the difference between the earned value (EV) and the actual cost</p><p>· <em>Cost performance index (CPI)</em> : indicates how efficiently the work is being performed regarding to budgeted cost of the work</p><p>Next, in order to evaluate project performance from these measurements, we need to visualise these metrics into dashboards or information radiators. Depending on the project management approach, dashboards will use different chart types. The project manager may visualize task boards, Burn-down or Burn-up charts, or Kanban boards for Adaptive projects.</p><p>Manage issues/impediments</p><p>In general, managing project issues is most clearly reflected in the Risk domain. You can review the definition in Part 3 — Plan the Project.</p><p>For impediments, obstacles, or blockers, the first thing is to recognize them. Not every risk becomes an issue, and not every issue needs to be resolved immediately. After that, continuous reassessment is necessary to make sure, or simply to stay aware of, the status of the issue as well as any secondary risks that may arise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*fiIfv8Gl1tQN97N8AuQ8qA.png" /><figcaption><em>Figure 1 — Manage project issue cycle</em></figcaption></figure><p>On the other hand, in reality, many troubles do not arise from the project work itself but from people and communication within the project. Recognising and managing people is therefore an inevitable part of project management.</p><p>Manage changes</p><p>As mentioned in Part 3 — Plan the Project, “A large part of project management involves managing and controlling changes throughout the project execution.” Whether the project follows a Predictive or Agile approach, appropriate change control management is always required (you may want to review the comparison table in Part 3).</p><p>Below is a flow that I designed for a basic change control management process that most projects can apply. For Agile projects, it can also be tailored to fit, since generally no changes are allowed during a sprint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*87ChWgIVZ_QXd5P0g2_tjQ.png" /><figcaption><em>Figure 2 — Change control management process</em></figcaption></figure><p>Regarding scope, change control here is simply at the project level. The project manager may depend on the appropriate level of involved stakeholders. Decisions made by the Change Control Board (CCB) are also influenced — if not mostly influenced — by business relationships or the organisation’s strategy toward external factors (such as the market, people, or natural disasters).</p><p>Change management requires leaders to have a broader vision and better information in order to make decisions that impact the operations and portfolio of the organisation. If you are interested, you can learn more in the book ITIL v4 Foundation by Axelos.</p><h3>Closure</h3><p>After all, the primary and initial mission of a project is to create business value for the organization (including both the customer and the company itself). When entering the final phase, depending on the type of project and stakeholder requirements, there may be various closing activities, which are usually stated in the signed contract terms.</p><p>In general, the closing phase will basically include the following activities:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ln-W2K7l6VG0JDRJp84S-w.png" /></figure><p>At this stage, as a project manager, you should be careful of the trap called “no more work” and delaying the closing activities. A fairly common mistake of project managers or some team leaders is poor communication. There are cases where a project finished 2–3 weeks ago but some stakeholders were still not aware of it, or worse, they did not feel that the project delivered value (not to mention some subjective cases).</p><p>If the kickoff is the whistle that signals the start of the match, then the final report is the decisive strike that concludes the match. It not only demonstrates the success of the project but also shows respect for and recognition of the team’s achievements as well as the project manager’s own efforts. It is also an important milestone for both parties to proceed with acceptance and payment procedures if applicable (depending on the contract type).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a03Zei56ACle7qdZ3sgutg.png" /><figcaption><em>Figure 3 — Final report content : Summary of project/phase performance result</em></figcaption></figure><p>I hope this series is helpful. Wishing my colleagues bigger and more successful projects in the future.</p><p><em>End of the series.</em></p><p>Coming up in Case study (TBD)</p><p><em>Reference sources :</em></p><p>· <em>PMBOK Guide seventh edition</em></p><p>· <em>Project Management Institute (PMI)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84d4fbdab706" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project management methodology — Part 4: Execute the project]]></title>
            <link>https://medium.com/@vothanhthuy2802/project-management-methodology-part-4-execute-the-project-1e58287fe9e9?source=rss-146e8dd656fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e58287fe9e9</guid>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[project-manager]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Debra Vo]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 15:13:13 GMT</pubDate>
            <atom:updated>2026-03-02T15:13:13.491Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5lSvUpWBCO4ZP5Sf.png" /></figure><p>Execution is the phase where the project team begins carrying out the work in accordance with the plan that has been previously developed and approved. In an ideal scenario, everything would run smoothly — where all team members and stakeholders proactively initiate their responsibilities and align effortlessly with the project direction. However, in reality, this is where the role and accountability of the Project Manager become most visible. The PM is expected to take the initiative, mobilize the team into action, and serve as a bridge between project members, customers, and other stakeholders.</p><p>This raises an important question: even with a well-structured and comprehensive project plan, what must a Project Manager do to initiate action and translate that plan into outcomes — especially when the PM is not the one directly performing the technical work? I refer to this process as Direct and Manage Project Work.</p><p><em>The content presented in this article has been simplified based on the author’s personal perspective, and the primary purpose of this write-up is for reference and knowledge sharing only.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yjGCryyMo-hJrFCwVP0L9w.png" /><figcaption>Figure 1 — Project management framework</figcaption></figure><p>If you look at the framework above, in the Execution phase (highlighted in orange), you will see the typical activities that a Project Manager needs to carry out based on the approved plans.Naturally, most plans — or at least some of them — must be put into action immediately to avoid delays. However, in this article, I will not go into detail about how to execute each specific plan that has been carefully developed beforehand. It would be redundant to elaborate on how to develop and manage the project team or manage communications, since every project plan is different and priorities depend heavily on the specific context and circumstances.</p><p>Instead, I would like to focus on three key factors that, in my personal view, have a significant impact on how effectively those plans are executed.</p><h3>1. Craft your leadership styles</h3><p>In my view, one of the first things you should do after completing project planning is to reflect on your leadership style for that particular project (It will not take much of your time, yet the benefits may truly surprise you). But why focus on leadership rather than management? Simple put, <em>Management</em> : directing actions using a prescribed set of behaviors. And <em>Leadership</em>: guiding the team by using discussion and an exchange of ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/1*JvSPoRW80t7KC7wUivliGQ.png" /><figcaption>Figure 2 — Managers and Leaders</figcaption></figure><p>Although it is called Project Management, remember that — somewhat exaggerating — 90% of a Project Manager’s time is spent on communication. Therefore, consciously shaping and refining your leadership style is clearly essential.</p><p>Leadership skills are often regarded as key competencies, such as:</p><p>- Communication</p><p>- Conflict management</p><p>- Critical thinking</p><p>- Culture awareness</p><p>- Negotiation</p><p>- Meeting manegement</p><p>- Facilitation</p><p>- …</p><p>In today’s era, where individual freedom and personal values are highly emphasized, project managers are required to exercise a high level of sensitivity and adaptability — especially in Agile environments. In such contexts, a project manager is often expected to act as a servant leader, inspired by The Servant as Leader (1970) by Robert K. Greenleaf. While traditional leadership generally involves the accumulation and exercise of power by someone at the “top of the pyramid,” servant leadership takes a different approach. A servant leader focuses primarily on the growth and well-being of individuals and the communities to which they belong, shares power, puts the needs of others first, and helps people develop and perform at their highest potential.</p><p>Furthermore, regardless of which leadership style you choose, it can always be tailored to suit specific contexts, organizational cultures, and project objectives. Leadership is not about rigidly applying a single model — it is about adapting thoughtfully to achieve the best possible outcomes.</p><h3>2. Create collaborative project environment</h3><p>As mentioned earlier, approximately 90% of a project manager’s work revolves around communication. It can be argued that the ability to foster a collaborative project environment largely depends on effective communication. Healthy work environments are built on trust and respect, which serve as the foundation for ethical decision-making. Therefore, beyond having a well-planned communication management strategy in place, a project manager must</p><p><em>Build shared understanding</em></p><p>To create a healthy working environment, project team members must first align in direction and share a common understanding of the project’s purpose and objectives. A project manager can facilitate this alignment through a formal kickoff meeting, as well as through informal gatherings to reinforce project understanding and establish ground rules. These early interactions help set expectations, clarify roles, and build initial trust among stakeholders.</p><p>However, building shared understanding is not a one-time activity. It must be maintained consistently throughout the project lifecycle, with the frequency determined by the communication plan. Key project documents — such as the project charter, objectives, scope statements, and agreed ground rules — should be stored in a centralized and transparent location accessible to all team members.</p><p>After all, each individual has their own responsibilities and priorities, and without deliberate reinforcement, it is easy for people to lose sight of the bigger picture. Continuous communication ensures that everyone remains aligned, engaged, and committed to the collective goal.</p><p>Support team members performance</p><p>Supporting team members’ performance involves continuously tracking individual performance, providing constructive feedback, resolving issues, influencing behaviors, and managing conflicts effectively. This responsibility requires the project manager to possess strong observational skills, the ability to exercise appropriate control, and the capacity to genuinely engage with people. If these capabilities are not yet fully developed, they should be deliberately cultivated. A practical starting point may be to focus on key team members first, and gradually expand your engagement to the entire team. One-on-one conversations can be particularly effective for both the project manager and the team member. After all, the more insight you gain about your team — their motivations, concerns, and challenges — the better positioned you are to support performance and guide outcomes.</p><p>However, one of the greatest challenges to effective execution sometimes originates from the organization itself. Why is that?</p><p>The level of authority granted to a project manager is closely tied to the organizational structure. In a project-oriented organization, the project manager typically has high authority and autonomy, creating ideal conditions to fully exercise leadership and decision-making power. In contrast, in functional or weak matrix structures, the PM’s authority may be significantly limited. Not all organizations can operate under a project-oriented model. Traditional manufacturing companies or state-owned enterprises, for instance, often maintain rigid hierarchical structures where the role and authority of the project manager are constrained.</p><p>I strongly believe that awareness of organizational models and internal politics enables project managers to navigate complexity more effectively. Understanding these dynamics not only improves project outcomes but also helps PMs advance in their careers — regardless of the type of organization in which they work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1010/1*Em4qzyHq3ZQH7eJlxNBXKQ.png" /><figcaption>Figure 3 — PM authority in organization structure types</figcaption></figure><p><em>Empower the team</em></p><p>To achieve this, we must embrace diversity and have the courage to empower our teams so that project members can explore and fully develop their capabilities.</p><p>On the surface, empowerment sounds inspiring and noble. In reality, however, it is far from idealistic. I have personally faced consequences from misjudgments and flawed empowerment decisions. There are many factors that can lead to such failures — timing, readiness, competence, organizational culture — and perhaps the most valuable lessons come from experiencing them firsthand.</p><p>Yet, despite these setbacks, I have never abandoned this approach in the majority of the projects I have been involved in, whether serving as a leader or as a project manager. Why? Because empowerment is fundamentally about human development. It reflects a growth mindset — the belief that people can learn, adapt, and improve. More importantly, it creates new opportunities for others, just as previous leaders once created opportunities for you.</p><p>Empowerment may involve risk, but without it, there is no real development — neither for the team nor for the leader.</p><h3>3. Ensure schedule happended</h3><p>Dreams remain just dreams unless we take action. But how do we trigger that action? It may not be as difficult as it sounds — in fact, it might even seem like “a piece of cake.” Yet many of us still struggle with it.</p><p>Throughout the execution phase, there are numerous events — both large and small — such as sync-up or stand-up meetings, training sessions, improvement workshops, review meetings, and more. Each serves a different purpose and is conducted within different time frames: daily, weekly, biweekly, monthly, quarterly, or ad hoc, depending on customer requirements or management expectations.</p><p>So how do we ensure these events actually happen? The answer is surprisingly simple: the <strong><em>calendar</em></strong>.</p><p>Yes — intentionally scheduling events and formally inviting the relevant stakeholders makes a significant difference. Clearly defining the date, time, objectives, and expected outcomes strengthens commitment and accountability within the team.</p><p>How far in advance you plan depends on the project manager’s capability, project needs, and contextual constraints. Sometimes, schedules do not unfold as planned — and that is perfectly normal. Delays, cancellations, and adjustments are inevitable in real-world projects. What truly matters is persistence. Structured repetition, done wisely and consistently, transforms intention into action — and action into results. Because discipline in execution is rarely glamorous, but it is always powerful.</p><p>End of Part 4.</p><p>Coming up in Part 5 +6: Monitor/control and closure</p><p><em>Reference sources :</em></p><p>· <em>PMBOK Guide seventh edition</em></p><p>· <em>Project Management Institute (PMI)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e58287fe9e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project management methodology — Part 3: Plan the project]]></title>
            <link>https://medium.com/@vothanhthuy2802/project-management-methodology-part-3-plan-the-project-054bc692313c?source=rss-146e8dd656fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/054bc692313c</guid>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[project-manager]]></category>
            <dc:creator><![CDATA[Debra Vo]]></dc:creator>
            <pubDate>Fri, 30 Jan 2026 15:58:46 GMT</pubDate>
            <atom:updated>2026-01-30T15:58:46.498Z</atom:updated>
            <content:encoded><![CDATA[<h3>Project management methodology — Part 3: Plan the project</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BdZ1g8alVosM1d4B_Rm8oQ.png" /></figure><p>Continuing the Project Management article series, this part focuses on one of the most critical next steps: Planning.</p><p>As many of you may already know, planning plays a vital role in almost every aspect of our lives — from personal work to the operation of an organization or even a large enterprise. In fact, the quality and depth of planning often reflect the capability of a leader or manager. Project management is no exception. Effective planning is a core enabler of value delivery and project success. Even the topics discussed in Part 1 can be seen as early preparation, laying the groundwork for the planning process that follows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OdjhEXlFNzZWmUVw38WeCw.png" /><figcaption>Figure 1 — Project management framework</figcaption></figure><p>In general, regardless of a project’s size, a Project Manager (PM) needs to consider several core aspects when performing project planning, and tailor them based on the delivery approach or methodology that has been selected upfront. This also connects to the topic of project approach selection discussed in the previous article. Broadly speaking, there are three main project approaches: predictive, adaptive, and hybrid. Choosing the right and most appropriate project approach is a critical decision, as it has a direct and significant impact on how each aspect of planning is carried out.</p><p><em>The content presented in this article has been simplified based on the author’s personal perspective, and the primary purpose of this write-up is for reference and knowledge sharing only.</em></p><h3>1. Project management plan (high level plan)</h3><p>Project Management Plan (PMP) is a formal document that serves as the roadmap for a project, outlining how it will be executed, monitored, controlled, and closed. It integrates all necessary subsidiary plans (like scope, schedule, budget, risk, and communication) (PMBOK Guide 4th Edition)</p><p>Simply put, the project management plan defines <em>how</em> the work will be performed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*nU0RkBzx4dy4XXDxLz-fwA.png" /><figcaption>Figure 2 — Project management plan</figcaption></figure><h3>2. Scope</h3><p>Depending on the selected project delivery approach, the way scope is planned and managed can differ significantly (as will be discussed in the following sections). However, regardless of the approach, the primary purpose of scope management is to clearly define the work to be performed in order to deliver the intended outputs — such as a service, product, feature, or function. Scope management also provides a foundation for effective control and for validating outputs with stakeholders, while helping to avoid scope creep and gold plating.</p><p><em>2.1 Predictive approach</em></p><p>As the name suggests, under a predictive approach, the Statement of Work (SoW) is defined as clearly and comprehensively as possible upfront and then baselined before the project moves into the execution phase. In this approach, scope is largely fixed early, and changes are managed through formal control processes. To establish effective scope management, there are several fundamental areas that a Project Manager (PM) should focus on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*ek47kQDUmMYcEeUW4gEsIg.png" /></figure><p>- <strong>Collect requirements</strong> : This activity reflects the PM’s capability in communication, inquiry, and information synthesis. All project artifacts — such as documents, written materials, and even meeting discussions — are valuable inputs for requirements work. The PM typically performs elicitation → documentation → categorization → prioritization → specification and modeling, and then consolidates the outputs into requirements documentation and a Requirements Traceability Matrix (RTM). Common tools and techniques that may be used include expert judgment, interpersonal and team skills, brainstorming, interviews, focus groups, data analysis, voting, mind mapping, and prototyping, among others.</p><p>- <strong>Build project scope statement : </strong>This document defines the boundaries of the project outputs. It may include a scope description, acceptance criteria, deliverables, out-of-scope items and constraints and assumptions.</p><ul><li><strong>Create WBS :</strong> The WBS decomposes project deliverables and the Statement of Work (SoW) into smaller, manageable components, organized hierarchically from the highest to the lowest level. It is important to note that the WBS is not an organizational hierarchy; it focuses on what will be done, not how or when the work will be performed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*63HmtI3ZyNteVcXQWJWkkA.png" /><figcaption>Figure 3 — Work breakdown structure</figcaption></figure><p>At this point, depending on the specific requirements of the organization or the project, additional documents and tasks may be required. Once the scope has been approved and baselined, any changes are permitted only in accordance with the change management plan. From there, scope control and scope validation are performed throughout the project lifecycle as part of the Project Manager’s ongoing responsibilities.</p><p><em>2.2 Adaptive approach</em></p><p>Agile, Scrum, Kanban, Lean, and Extreme Programming are all development approaches that fall under the adaptive methodology. Each approach has its own strengths and limitations, and the choice depends on the specific context, project characteristics, and delivery objectives. However, despite their differences, they share several common characteristics:</p><p>- Collect requirement , scope defined and WBS are repeated for each iteration and throughout the project.</p><p>- Control and valid scope are repeated for each iteration and throughout the project.</p><p>- Deliverables are developed over multiple iterations where a detailed scope is defined and approved for each iteration when it begins ( rolling way planning )</p><p>The core principle of the adaptive approach is continuous improvement. As a result, planning in adaptive projects typically focuses on delivering a <strong>Minimum Viable Product (MVP)</strong> first, followed by additional features in subsequent iterations.For example, when building a car, Agile PM will follow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*vz33Lyln_EEqKu5-xxtM7A.png" /></figure><p>That said, this does not mean that planning is less important in adaptive projects. Making requirements as clear and visual as possible, and gaining stakeholder especially customer’s alignment, is still critically important and reflects the PM’s professional capability and maturity. The key difference is that planning in adaptive projects is more flexible and more iterative, fully aligned with the mindset of continuous improvement.</p><h3>3. Schedule</h3><p>To ensure that the duration of individual activities is well managed throughout project execution — and that the overall project completion timeline is met — the Project Manager needs to focus on establishing and developing the project schedule.</p><p><em>3.1 Predictive approach</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SCE94zazXMqz3pdpv61b_w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MeZ1DMDVFNUdKZvEoX5Q1A.png" /></figure><p><em>3.2 Adaptive approach</em></p><p>Returning to the adaptive approach, there are multiple ways to perform schedule planning. However, regardless of the technique used, they all aim toward a single objective: to deliver business value incrementally in the shortest possible time.</p><p>Below is Figure 4 — Overview of adaptive planning</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*bYjld_MpC3w3TJ7TCBqT5A.png" /><figcaption>Figure 4 — Overview of adaptive planning</figcaption></figure><p>- <strong>Release planning</strong> : The goal is to determine which user stories will be delivered in which iterations for an upcoming release. The Project Manager (PM) typically develops a release roadmap that prioritizes stories (e.g., Must-have, Should-have, Could-have). One of the most challenging aspects of planning at this stage is estimating the initial team velocity. The PM may use various approaches, such as consulting experienced experts or senior team members, or simply facilitating a team discussion by asking: “Based on each team member’s capacity, which of the top-priority backlog items for this release can we realistically commit to completing in the first iteration?”. Ultimately, the strength of this approach lies in its flexibility, continuous learning, and ongoing improvement.</p><p>- <strong>Iteration planning : </strong>Once the user stories have been identified through release planning, the PM works with the team to translate them into features to be delivered within each iteration. This includes defining the <strong>Definition of Done (DoD)</strong>, testing senarios for each story, and breaking the work down into executable tasks.<br> At this stage, estimation, task assignment, and scheduling are performed collaboratively and in real time<strong>.</strong></p><h3>4. Resources</h3><p>Having the right resources is a critical factor in ensuring that a project can be executed effectively and ultimately succeed. A well-defined Resource Management Plan should address the following key aspects:</p><p>- Identify resources ( both people and physical resource ) : Resource identification may be based on experience, knowledge, skills, and attitude, as well as international and contextual factors such as location, time zones, cultural considerations, and communication constraints.</p><p>- Acquire resources</p><p>- People’s roles and responsibility ( RACI)</p><p>- Project organization chart ( visual with resource categories and reporting relationship)</p><p>- Guidance on how to define, select, manage and release resources</p><p>- Team development ( training, recognition )</p><p>During the resource acquisition process, the Project Manager (PM) must continuously evaluate make-or-buy-or-borrow decisions. These decisions depend on factors such as project size and complexity, customer requirements, and the organization’s internal capabilities. Based on this assessment, a <strong>Procurement Management Plan</strong> is developed. In general, procurement can follow two primary models: centralized and decentralized. In a centralized procurement model, the purchasing, contracting, or legal department is responsible for the end-to-end procurement process — from bidding and vendor selection to contract and vendor management — with the PM providing coordination and oversight. In contrast, a decentralized procurement model assigns a dedicated contract or procurement manager to work directly within the project team.</p><p>A <strong>procurement strategy</strong> typically clarifies key elements such as the delivery method, contract payment types, procurement phases, and contract types. <em>(Further details can be explored through additional references and sources as needed)</em></p><h3>5. Budget</h3><p>Cost planning is highly critical and closely linked to resource estimation and activity duration. Based on my experience, regardless of the project approach being used, budget preparation must always be handled with a high level of rigor and discipline. The most noticeable difference lies in Agile projects, where teams typically collaborate closely with finance stakeholders to propose incremental budgeting ( Of course, there are also some exceptions). This is often more challenging compared to a predictive approach, as funding is requested and allocated in smaller increments rather than upfront. It is important to remember that organizational cash flow and budgets are not always readily available, nor are they always fully supported by all stakeholders. People are rational actors, and each role or group tends to protect its own interests and priorities. This is precisely why Project Managers need to identify, analyze, and categorize stakeholders carefully during the Initiate phase.</p><p>Below are some suggested practices for budget planning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6hpXVxG_3WkvPFFW_QPtJQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*6paJ1dZllhzOA279Ma8OKA.png" /><figcaption>Figure 5 — Budget planning</figcaption></figure><h3>6. Risk</h3><p>When people talk about risk, it is often associated with negative outcomes rather than positive ones.<strong> </strong>However, from a Project Manager’s perspective, it is essential to clearly understand risk concepts and what they truly represent.</p><p>First, risks originate from a wide range of known and unknown sources, both within and outside the business environment. Importantly, risks can be positive (opportunities) or negative (threats). Common risk categories include external, internal, technical, and business risks (which may result in loss or gain), as well as pure risks (loss only) and unforeseeable risks. Second, risk identification and assessment may vary depending on one’s role. For a Project Manager, risk is typically viewed at the level of individual project risks that may affect project objectives, as well as at a broader level from the project sponsor’s perspective, which focuses on overall project exposure.</p><p>Therefore, effective project risk management must consider both individual project risks and the sources of overall project risk. Identify risk as detailed as required to ensure unambiguous understanding commonly referred to as a risk statement. Example of structure risk can be used [ Posibility that has an effect on objectives/deliverables] caused by [cause] resulting in [consequence]. Below are some recommended practices for risk management.</p><p><em>6.1 Predictive approach</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RJF4zvf4cos9UvVGH6p4Gw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*411wPmL5AcDNozauNo_kiQ.png" /><figcaption>Figure 6 — Risk register sample</figcaption></figure><p><em>6.2 Adaptive approach</em></p><p>In some aspects, the adaptive approach is similar to the waterfall approach in that risk identification and risk handling are performed continuously and iteratively by the Project Manager and the team throughout the project lifecycle. However, in Agile projects, risks are often embedded within user stories or captured as part of backlog work items, and the team discusses and addresses these risks during planning meetings or as part of the normal flow of work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*0NdTdwcKrwE2lbUh0B990A.png" /><figcaption>Figure 7 — Risk planning in agile approach</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*SpvYeDvjdSonD3jBOSzWCg.png" /><figcaption>Figure 7 — Risk planning in agile approach</figcaption></figure><h3>7. Quality</h3><p>Delivery is more than just scope and requirements. Scope and requirement focus on what needs to be delivered. Quality focus on the performance levels that are required to met. There are some quality theories in the world such as International Standard Organization (ISO), Capability Maturity Model Integration (CMMI), Six Sigma,…Most of costs associated with quality are born by the organization and reflected in policies, procedures, and work processes. If your organization have no a quality policy, then your project needs to create one.</p><p>The cost of quality model introduced below help you know perspectives related to the cost of compliance and non-conpliance well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jdVp1LPcErQuG0hIhg3POg.png" /></figure><p>It would be an oversight to discuss quality concepts without addressing two key practices: Quality Assurance (QA) and Quality Control (QC). As a Project Manager, it is essential to clearly understand both the differences and the relationship between these two concepts. Quality Assurance (QA) focuses on prevention — ensuring that the right processes and standards are in place to avoid defects in the first place (for example, through quality audits). In contrast, Quality Control (QC) focuses on detection — identifying defects in deliverables after they have been produced but before they are released.</p><p>Therefore, in any project, effective coordination between QA and QC plays a critical role in achieving strong quality management, and ultimately contributes to the overall success of the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*1J9lhy2ngTHR2aPIbFCjXA.png" /><figcaption>Figure 8 — Quality control and Quality assurance</figcaption></figure><p>With Agile methods, it is often used on projects that are intangible without clear expectation. With frequent verification and validation, we’re checking to make sure things are working and progressing as they should, as well as looking for any mismatches in business requirements. In addition, short feedback loops and daily stand-up meetings themselves serve as powerful mechanisms that enable the Project Manager and project team to quickly detect issues and make timely adjustments when deviations occur.</p><p>Common quality tools that can be applied across different types of projects ( depending on the purpose and context) include cause-and-effect diagrams, flowcharts, check sheets, Pareto diagrams, histograms, control charts, and scatter diagrams.</p><h3>8. Change</h3><p>A significant part of project management involves managing and controlling changes throughout project execution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aV0fzwEpp3Cagj7tOTycNQ.png" /></figure><p>Last but not least is the <strong>integrated plan.</strong></p><p>Regardless of which project delivery approach is applied, there is always a need to consolidate all subsidiary plans into a coherent whole. This directly reflects the principle of “Thinking as a System” discussed in Part 1. It highlights that all the core aspects mentioned above are closely interconnected, mutually reinforcing, and in many cases complementary to one another. Just as an organization can operate smoothly only when its departments work effectively together, a project can succeed only when its management domains are well integrated. The model below illustrates the relationships among the different project management domains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*c6GH6jxH95lAQPqzWei8Yw.png" /><figcaption>Figure 9 — Project management domains relationship</figcaption></figure><p>End of Part 3.</p><p>Coming up in Part 4: Execute the project</p><p><em>Reference sources :</em></p><p>· <em>PMBOK Guide seventh edition</em></p><p>· <em>Project Management Institute (PMI)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=054bc692313c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project management methodology — Part 2: Initiate the project]]></title>
            <link>https://medium.com/@vothanhthuy2802/project-management-methodology-part-2-initiate-the-project-fdfd4182136d?source=rss-146e8dd656fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdfd4182136d</guid>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Debra Vo]]></dc:creator>
            <pubDate>Sun, 09 Nov 2025 05:28:23 GMT</pubDate>
            <atom:updated>2025-11-09T05:37:10.267Z</atom:updated>
            <content:encoded><![CDATA[<h3>Project management methodology — Part 2: Initiate the project</h3><p>Once you’ve developed the right mindset and grasped the fundamental management principles, the next step for a Project Manager (PM) is to seek opportunities to practice, refine, and enhance their professional skills through real-world application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BdZ1g8alVosM1d4B_Rm8oQ.png" /></figure><h3>Part 2: Initiate the project</h3><h3>1. Introduction</h3><p>To continue this series, I will provide a more detailed of project management practices, distilled from personal experience and summarized in the table below called Project management framework. Project Managers (PMs) can apply these principles to any type of project, regardless of its size or complexity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*qdInXtZGW7SK4uNNwFI3YQ.png" /><figcaption>Figure P2.1 - Project management framework</figcaption></figure><h3>2. Essential activities</h3><p>Project initiation marks the beginning — and one of the most crucial phases — in laying the foundation for future success.<br> I recommend focusing on <strong>three essential points</strong> that will help Project Managers (PMs) start off strong, equipped with sufficient information and an appropriate approach to managing the project.</p><h3>Identify and engage stakeholders</h3><p>The first thing a professional Project Manager (PM) should do upon receiving a request from upper management is not to immediately dive into creating management documents or contacting the client. Instead, the PM should take time to think about the project’s stakeholders.</p><p>Stakeholders are any individuals, groups, or organizations that may affect or be affected by the project’s decisions, activities, or outcomes.</p><p>Reflecting on this helps the PM clearly and comprehensively identify all relevant parties, enabling appropriate communication and reducing unnecessary conflicts. Through this process, the PM can also define project objectives more accurately and align them with the client’s real needs and expectations.</p><p>Below are the steps that can be applied:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*BDhFvE7TcRVp8mKsXckC_A.png" /><figcaption>Figure P2.2 - Identity and engage stakeholders flow</figcaption></figure><p><em>Identify stakeholders</em></p><p>Through project agreements and meetings, the Project Manager (PM) can identify and categorize stakeholders — from upwards, downwards, sidewards to outwards.It’s also beneficial to identify project team members early on. This helps the PM plan effectively, align with other departments, and allocate resources in a timely and appropriate manner.</p><p>Next, you should record this information in a document called the Stakeholder Register (a draft version is acceptable at this stage). This process should be carried out periodically throughout the project lifecycle.</p><p>A sample template is shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*hV34PR-SQnG5kBeMqkLbNA.png" /><figcaption>Figure P2.3 — Sample document of stakeholders register</figcaption></figure><p><em>Plan stakeholders engagement</em></p><p>Once you have identified who your stakeholders are, the next step is to develop an engagement plan for them. The goal is to create a strategic and actionable plan that enables effective interaction, ensuring stakeholders remain actively involved and provide ongoing feedback throughout the project. This plan should be developed based on their needs, expectations, interests, and potential impact on the project. These engagement strategies are then implemented through communication activities outlined in the <strong>Communication Management Plan document </strong>( consolidated in the planning phase).</p><p><em>Management and monitoring stakeholders engagement</em></p><p>This activity should be carried out periodically and continuously throughout the project lifecycle.. Communicating and working with stakeholders to meet their needs/ expectation , adrees issue as they occured and foster appropriate stakeholders engagement in project activities. It allow PM to increate support and minimize resistance which significantly improve the project success.</p><h3>Determine project approach</h3><p>Identifying the appropriate project delivery approach is a critical factor in ensuring project success. A Project Manager (PM) should take this decision seriously — consulting organizational process assets, historical documents, or experienced mentors when needed. Depending on the product characteristics, life cycle, requirement certainty, and delivery cadence, the PM should choose the most suitable development approach. This decision will also shape the management style the PM adopts throughout the project.</p><p>Three commomly used approaches are <strong>Predictive, Hybrid and Adaptive.</strong> These approaches are often viewed as a spectrum, from the predictive approach on one end of spectrum, to the adaptive on the other end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*-M_MqZX0hstC6suoIWHDBg.png" /><figcaption>Figure P2.4 — Common development approaches</figcaption></figure><p>As shown in Figure 4, these approaches compared based on their characteristics</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cYr-2WtV62rETvkcVO6wrA.png" /><figcaption>Figure P2.5 — Development approaches comparation</figcaption></figure><p>Among the 12 Project Management Principles mentioned in Part 1 — Fundamental Concepts, one key principle is “Tailor based on the context.” Indeed, deciding on the project life cycle and its phases is an example of tailoring the development approach. Additional tailoring can also be applied when selecting the development and delivery approach that best fits the project’s specific context.</p><p>A more detailed discussion of different approaches will be covered in another article, or you can refer to the PMBOK® Guide for further reference.</p><h3>Develop project charter</h3><p>The primary objective of this activity is to build a shared understanding among all project stakeholders with a clear vision and mission. At this stage, the Project Manager must focus intensively on consolidating project information from various sources, including the <strong>Benefit Management Document</strong>, <strong>Requirements Document,</strong> and even meeting minutes (MoM) related to the project, as well as proactively gathering relevant information through communication with stakeholders — who may be supervisors, colleagues, or clients involved and holding specific roles in the project. This process ultimately enables the creation of a comprehensive and accurate Project Charter.</p><p>The Project charter template may vary across organizations in terms of format, but it generally includes the following key points:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*u1yMba0MmCgBHanwPJyaFg.png" /><figcaption>Figure P2.6 — Project charter template</figcaption></figure><p>Once all preparations are in place, it is time for the Project Manager to organise the <strong>Kickoff Meeting</strong>, which serves as the official launch of the project. The primary objective of this meeting is to ensure that stakeholders have a clear understanding of the project’s goals, while also reconfirming previously agreed-upon agreements, expected outcomes, and constraints.</p><p>This meeting also provides the Project Manager with an opportunity to personally engage with stakeholders and facilitates initial networking and relationship-building, laying the foundation for smooth collaboration throughout the project lifecycle.</p><p>End of Part 2.</p><p>Coming up in Part 3: Plan the project</p><p><em>Reference sources :</em></p><p>· <em>PMBOK Guide seventh edition</em></p><p>· <em>Project Management Institute (PMI)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdfd4182136d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project management methodology — Part I]]></title>
            <link>https://medium.com/@vothanhthuy2802/project-management-methodology-part-i-d824a07eda6a?source=rss-146e8dd656fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/d824a07eda6a</guid>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Debra Vo]]></dc:creator>
            <pubDate>Sat, 04 Oct 2025 15:55:56 GMT</pubDate>
            <atom:updated>2025-11-09T05:30:08.207Z</atom:updated>
            <content:encoded><![CDATA[<h3>Project management methodology-Part I: Fundamental concepts</h3><p>This series of articles is intended for:</p><p>· Project Managers (those who have been or are directly involved in project management work) / PMAs</p><p>· Project Management Offices (PMOs)</p><p>· Anyone involved in any aspect of the project value delivery chain</p><p>· Individuals working on projects either full-time or part-time</p><p>· Those who are interested in project management and wish to gain insights into the project management mindset</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BdZ1g8alVosM1d4B_Rm8oQ.png" /></figure><h3>Part I: Fundamental concepts</h3><h3>1. Introduction</h3><p>According to the Project Management Institute (PMI) — a global, non-profit professional association that establishes standards for the discipline, and provides education and certifications — project management is defined as:</p><p>“Project management is the application of knowledge, skills, tools, and techniques to project activities to meet project requirements. It involves defining scope, planning, executing tasks, managing risks, communicating effectively, and overseeing the project to achieve specific objectives, deliver a unique result, and create value. A project is a temporary endeavor undertaken to create a unique product, service, or result.”</p><p>In <strong>Part 01</strong>, I would like to introduce two fundamental concepts that are essential not only in project management but also in general management:</p><p>- The System for Value Delivery</p><p>- Project Management Principles</p><h3>2. The system for value delivery</h3><p>At its core, business is about how an organization creates value for its stakeholders. When combined, these different sources of value form a value delivery system in which all elements interact with and support one another, aligned with the organization’s overall strategy.</p><p>This system is made up of various components such as portfolios, programs, projects, products, and operations. Figure P1.1 illustrates an example of a value delivery system that includes two portfolios, each containing multiple programs and projects. In addition, there are stand-alone programs and stand-alone projects that are not linked to any portfolio or program.</p><p>Within this system, any project or program can include or generate a product. Operations may directly support and influence any of these components . Collectively, these components form an interconnected chain of value that strengthens and reinforces one another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8HB9lM_DilBOD-X7WB8uqQ.png" /><figcaption><em>Figure P1.1 An example of a value delivery system</em></figcaption></figure><p>Put simply, a system for value delivery is part of an organization’s internal environment shaped by its policies, procedures, methods, frameworks, governance, structure, and so on.But this internal environment doesn’t stand alone. It exists within a much broader external environment, which includes things like the economy, competitors, political and legal systems, culture, and even natural conditions such as climate or geography (as shown in Figure P1.2).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*L8PMhqlzLZIc7WdXOaq-sA.png" /><figcaption><em>Figure P1.2 An example of value delivery system in internal and external environment</em></figcaption></figure><p>To work effectively, this value delivery system needs communication, information sharing, and feedback. These elements help ensure that the system runs smoothly, stays aligned with the organization’s strategy, and adapts to changes in the external environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*tQP_h4AcSmZuyjvHi5Ac8w.png" /><figcaption><em>Figure P1.3 Information model</em></figcaption></figure><p>In the figure, from left to right, the blue arrows represent information and strategic direction flowing from senior leadership. This guidance shapes Portfolios, which are then broken down into Programs and Projects. The outcomes or products from these projects are delivered to Operations for applying into practise. During operations, as products are utilized, feedback and requests for updates are generated to better align with the organization’s needs In turn, the achievements delivered by projects and programs contribute directly to the success and value of the organization’s portfolios. At the same time, operations provide ongoing information about how the organization is performing and progressing ( yellow arrows).</p><p>If we think of the <strong>system for value delivery</strong> as a machine, then the <strong>flow of information</strong> is like the energy that powers it. Without information, the value chain cannot run. Conversely, without the components of this system, even an abundance of information would be meaningless.</p><h3>3. Project management principles</h3><p>Principles of project management can also have some areas of overlap with general management principles</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*7h-vomWHTJ8PkPFE2LcfXw.png" /><figcaption><em>Figure P1.4 Overlap of Project management and General project management</em></figcaption></figure><p>“The principles of project management were identified and developed by engage a global community of project practitioners. The practitioners represent different industries, culture backgrounds, and organization in different roles and with experience in various types of projects. Multiple rounds of feedback resulted that provide guidance for effective project management”.</p><p>- Focus on value</p><p>- Be a strustworthy, respectful, and caring steward both inside and outside of the organization</p><p>- Demontrate leadership behaivior that enables high performance of any specific role in the project team</p><p>- Create a collaborative project team environment</p><p>- Effectively engage with stakeholders</p><p>- Regconize, evaluate and response to system interactions with holistic view</p><p>- Tailor based on the context</p><p>- Ensure quality management process to produce deliverables meet project objectives</p><p>- Navigate continually project complexity</p><p>- Optimize risk responses both opportunities and threats</p><p>- Embrace adaptability and resiliency</p><p>- Enable change management to achieve the envisioned future state ( different form change control management)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*hNgjN1s2xAwQbk5tV20U3A.png" /><figcaption><em>Figure P1.5 Project management principles</em></figcaption></figure><p>In conclusion, these are the fundamental concepts that every manager in general — and project managers in particular — should reflect on, understand deeply, and apply in both their mindset and their day-to-day work. At first, they may seem academic or abstract, but at the heart of management lies vision and an open mindset that allows us to adapt under any circumtances. Surely It will takes time to practice and experience to fully grasp their meaning. And in the real world, these ideas may not always be implemented perfectly, due to the inevitable influence of people, politics, organizational dynamics, or external factors. Nevertheless, these concepts remain a solid foundation that can help any project manager advance further in their professional journey.</p><p>End of Part 1.</p><p>Coming up in Part 2: Initiate the project</p><p><em>Reference sources :</em></p><p>· <em>PMBOK Guide seventh edition</em></p><p>· <em>Project Management Institute (PMI)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d824a07eda6a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Not sure what to study? Start with economics]]></title>
            <link>https://medium.com/@vothanhthuy2802/not-sure-what-to-study-start-with-economics-3195ae4c09a0?source=rss-146e8dd656fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/3195ae4c09a0</guid>
            <category><![CDATA[management-mindset]]></category>
            <category><![CDATA[economics]]></category>
            <dc:creator><![CDATA[Debra Vo]]></dc:creator>
            <pubDate>Sun, 21 Sep 2025 07:05:51 GMT</pubDate>
            <atom:updated>2025-09-21T07:05:51.918Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi there,</p><p>I’m glad you’ve clicked on my piece. If the title has drawn you in, let me clarify from the start: I have no intention of prescribing a career path or glorifying some lofty — abstract term. What follows is simply distilled from my own experiences and reflections. At its core, I just want to share these thoughts with anyone who might need them — and perhaps, in some small way, they may be of use to you.</p><h3>Why Economics?</h3><p>First, ask yourself: what truly sets people apart from one another? Whether they are students, farmers, doctors, engineers, CEOs, company chairmen — or even presidents. Or perhaps, what is the single most important factor in the growth of an individual and the prosperity of a nation? Let us pause for a moment and reflect.</p><p>Consider the <em>story of the broken window</em>.</p><p>At a bakery, a mischievous boy throws a stone and shatters a window. The crowd gathers, lamenting, “What a shame.” Yet soon the argument emerges: the baker now must pay to repair the window. That expense becomes revenue for the glazier, and income for the repairmen. With their new earnings, they spend more, which in turn becomes income for others. If the broken window were large enough, could it not spark an economic boom?</p><p>Most people accept this reasoning — at least in part. But they are not economists. A true economist would reply: If the baker had not been forced to replace the window, he could have invested that money in a new oven. That would have increased sales for the oven-maker, improved efficiency for the bakery, expanded the business, and created more jobs and income. The broken window did not generate new value; it merely diverted spending from one use to another.</p><p>People often see only what happens, rarely what would have happened had the window never been broken. Economics, at its core, trains us to PERCEIVE THAT HIDDEN LAYER — so we may improve, adapt, and create real progress.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gl_MOsbKEvQKxwA0mduB3g.png" /><figcaption><em>Generated by ChatGPT</em></figcaption></figure><p>Another example of this perspective is the decline of certain kinds of jobs.</p><p><em>Is job loss always bad news?</em></p><p>There was a time when nearly 90% of the U.S. population worked to produce food. Today, only about 3% do. Forgive me for asking, but did America grow poorer because agricultural jobs disappeared? Of course not. Those who might once have been farmers are now doctors, engineers, software developers, or university professors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qEoZhxOzh19-yGC2tH08ZQ.png" /></figure><p>That is why, instead of simply counting the number of jobs, we should ensure that all kind of work are taken into account. From an economist’s point of view, creating jobs — or desperately clinging to them — has never been a sustainable long-term goal. True progress, they understand, often comes through the destruction of old jobs. There will be moments of disruption, when supply and demand in the labor market fall out of balance. But those moments are temporary. So do not be overly pessimistic, nor impatient, nor stubbornly resistant to change.</p><p>I am certain that everyone has at least once heard of Adam Smith’s famous hypothesis: The theory of <em>Invisible Hand </em>. This is perhaps the single most important idea you will encounter when studying economics. You will come to understand how each of us, by pursuing our own interests, can end up advancing the well-being of society as a whole. You will see how seemingly fragmented activities in the marketplace are coordinated into a force that creates national prosperity. You will grasp both the wonder of markets — and the dangers when they are excessively constrained. And I wager you will learn far more than what your high school textbooks ever suggested.</p><p>As Robert D. McTeer, former President of the Federal Reserve Bank of Dallas, wrote in the Wall Street Journal (June 2003):</p><p>“Studying economics becomes increasingly valuable as you climb the career ladder. I don’t know of a better major for CEOs, members of Congress, or Presidents of the United States. Learning to THINK LOGICALLY AND SYSTEMATICALLY will be of great benefit throughout your life.”</p><p>Indeed, the perspective of economics seeps into every corner of life. It is this way of thinking that marks the difference between one person and another. To apply what you have learned — to use the principles of economics as a compass in the real world — is what makes a person resilient, confident, and capable of climbing ever higher on the ladder of career and life.</p><h3>Who Studies Economics</h3><p>As a student, you may have wondered whether studying economics will truly be useful later in life. In truth, economics may sound abstract, yet at its core it is deeply practical — and remarkably versatile across many career paths. Consider just a few names of those who once studied economics as undergraduates:</p><p>George H. W. Bush — U.S. President</p><p>Donald Trump — U.S. President</p><p>Meg Whitman — Former CEO of eBay</p><p>Elon Musk — CEO of Tesla, SpaceX</p><p>Scott Adams — Cartoonist of Dilbert</p><p>Cate Blanchett — Actress</p><p>Miuccia Prada — Fashion designer</p><p>Anthony Zinni — General (ret.), U.S. Marine Corps</p><p>Michael Kinsley — Journalist</p><p>Mick Jagger — Singer (The Rolling Stones)</p><p>Of course, attending the London School of Economics did not help Mick Jagger hit the high notes. And a degree in economics did not give Scott Adams the ability to create one of the world’s most famous comic strips. Yet what it did provide was a FRAMEWORK to manage and invest wisely the immense income he would later earn in their career.</p><p>When asked in 2005 why The Rolling Stones were still touring, economics graduate Mick Jagger answered with disarming brevity: “Supply and demand.” To which Keith Richards added, “If the demand’s there, we’ll supply.”</p><h3>Thinking Like an Economist</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*MfAjY_undKbAqb1hLaEg7A.png" /><figcaption><em>Generated by ChatGPT</em></figcaption></figure><p>Every discipline has its own language and way of thinking. Mathematicians speak of theorems, numbers, and vectors. Biologists speak of cells, reproduction, and evolution. Lawyers speak of principles, rules, and binding promises. Economists, too, have their own vocabulary — terms such as supply, demand, elasticity, comparative advantage, consumer surplus, and deadweight loss. Sometimes even familiar words are used by economists in a way that feels entirely different. At first, this language may seem distant and cryptic, but over time it reveals its value, offering fresh and practical insights into the world you live in. Naturally, it takes time to learn how to think like an economist — just as no one becomes a mathematician, a biologist, or a skilled engineer overnight.</p><p>At first glance, it may sound odd to call economics a science. After all, economists do not work in laboratories or peer through telescopes. Yet economics shares THE ESSENCE OF SCIENTIFIC METHOD: a process of observing the world and testing hypotheses about how it works. The challenge, however, is that controlled experiments in economics are often difficult — sometimes impossible. A physicist can study gravity by dropping a ball from the top of a building. An economist cannot simply alter a nation’s monetary policy to generate data. How, then, do economists learn? The answer lies in the “natural experiments” that history provides. Consider, for example, how wars in the Middle East disrupt the supply of crude oil, sending global prices soaring. Such events allow economists to study the impact of vital resources on the world economy. Through these episodes, we gain a window into the past, a means of evaluating modern theories, and a guide to more accurate predictions for the future.</p><p>Another equally important method is the use of ASSUMPTIONS. Assumptions simplify a complex reality, making it easier to understand. To study international trade, for instance, economists might assume there are only two countries and each produces only two goods. In reality, of course, there are hundreds of countries producing thousands of goods. Yet once the insights is clear in the simplified model, we can extend it to the messier real world. This habit of reasoning by abstraction is not only powerful in economics but also invaluable in approaching life’s many problems.</p><p>Do not fall into the trap of thinking that the workings of financial systems or national monetary policies have nothing to do with your life. Such a view is gravely mistaken. The company you start is part of your nation’s market, and your nation itself is woven into the system of the global economy. The links are deep and inseparable, and their effects — whether good or bad, near or far — will eventually touch you and your family.</p><p>That is why it is worth choosing and preparing for yourself a strong, reliable companion on the journey toward a meaningful career and a fulfilling life: THE MINDSET OF AN ECONOMIST.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3195ae4c09a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[To be human is to live with trade-offs]]></title>
            <link>https://medium.com/@vothanhthuy2802/to-be-human-is-to-live-with-trade-offs-0fc60f8b40a5?source=rss-146e8dd656fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/0fc60f8b40a5</guid>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[human-behavior]]></category>
            <dc:creator><![CDATA[Debra Vo]]></dc:creator>
            <pubDate>Sat, 13 Sep 2025 07:50:27 GMT</pubDate>
            <atom:updated>2025-12-03T14:46:02.690Z</atom:updated>
            <content:encoded><![CDATA[<p>Understanding the fundamental nature of society helps us make better decisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*50ptcgQTibOq7n0iJph4lg.png" /><figcaption><em>Generated by ChatGPT</em></figcaption></figure><p><strong>To begin with, the nature of resources on Earth is limited.</strong></p><p>Resources include both tangible and intangible elements: people, land, air, fuel energy, time, etc.</p><p>Every person only has 24 hours in a day. A student must choose between dedicating her time learning economics or exploring psychology or trying to balance both. If she wants to spend 01 more hour on economics, she must give up 1 hour else where. Instead of attending in the class, she could use that time to work part time job, watch TV or take a nap at home.</p><p>Parents face similar decisions. When they decide to spend 1 extra dollar on shopping for their children, they’re giving up a 01 dollar that could have been saved for the future.</p><p>Now we approach to bigger picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lXC8gKYriOhPzNAxw5hF8A.png" /><figcaption><em>Generated by ChatGPT</em></figcaption></figure><p><strong>Trade-offs become more complex when individuals come together into society.</strong></p><p>In modern life, one of important trade-offs is between environment protection and income. For example, a law released which the call for reducing pollutant emissions. This leads to business incur higher cost to comply with and as a result the higher products price, reduced profit and potentially lower wages. While this policy help preserve environment, improve the public health, they also impose economic burdens on business owners, workers and consumers.</p><p>Another example is trade-offs between Efficiency and Equity. In his book of Macroeconomic ( 6th edition) by N Gregory Mankiw, he likened Efficiency to the size of ecomomic pie and Equity to how fairly the pie is divided among people. This analogy highlights a fundamental tension: When the law makers aim to distribute the well-being more equally, through programs like health insurance, unemployment benefits which providing benefits to those in need-they often face trade-offs. Take progressive taxation as an example: individuals who earn more are required to contribute more to fund government operations. While it brings equity in society by re-distributing wealth from the rich to the poor, it can also decrease the incentives for high earners to work harder or invest more. As a result, policies designed to enhance fairness may unintentionally affect overall economic efficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cpwcnWIYS9WwhjsJDQDMrg.png" /><figcaption><em>Generated by ChatGPT</em></figcaption></figure><p><strong>Recognition of trade-offs is the first step toward making better decision.</strong></p><p>Understanding that every choice involves trade-offs doesn’t mean that you always know the right answer for what should do and what shouldn’t.</p><p>Should the student give up learning the psychology to focus entirely for economics? Should the governance sacrifice evironment protection to maintain standard of living? Or should we stop supporting the poor merely because it might distorts their work motivation?</p><p>There are no definitive answers or universal formulas. However, it’s so fundamental to aware and recognite the trade-offs because people will make better decision when they understand all current choices well.</p><p><strong>In conclusion,</strong> no matter who you’re , what you do or where you live , as long as you ‘re human being living and interacting in society, you inevitably face trade-offs in every aspect evey choice and every policy . The most significant thing is to recognise them, learn how to make decision — accept the consequences and adapt accordingly. After all, nothing is perfect.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0fc60f8b40a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>