<?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 Alan Zucker on Medium]]></title>
        <description><![CDATA[Stories by Alan Zucker on Medium]]></description>
        <link>https://medium.com/@alan-pmessentials?source=rss-aa503288162e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*htR9maukCAb-YdmaeiucxQ.png</url>
            <title>Stories by Alan Zucker on Medium</title>
            <link>https://medium.com/@alan-pmessentials?source=rss-aa503288162e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:00:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alan-pmessentials/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[Back-to-Basics: Agile]]></title>
            <link>https://alan-pmessentials.medium.com/back-to-basics-agile-d88c926b9968?source=rss-aa503288162e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d88c926b9968</guid>
            <category><![CDATA[agile-project-management]]></category>
            <category><![CDATA[agile-product-managment]]></category>
            <dc:creator><![CDATA[Alan Zucker]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 03:39:55 GMT</pubDate>
            <atom:updated>2026-11-09T03:39:55.075Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-tGrL4ePmyn2kgeVAJpN-w.png" /></figure><p>Agile killed agility.</p><p>Like the owner in the fable of the goose that laid the golden eggs, the Agile industry went too far with a good idea. Agile lost its roots through its commercialization, the proliferation of certifications, and the influx of consultants.</p><p>Surveys have <a href="https://www.pmi.org/blog/project-management-embraces-the-fit-for-purpose-approach">shown a decline in Agile</a> over the past several years. <a href="https://www.linkedin.com/pulse/agile-community-shat-bed-scott-ambler-1npwc/">Leading agilists</a> declared its death. Others are trying to <a href="https://agilealliance.org/reimagining-agility/">reimagine</a> and reinvigorate it. I think we should simply return to its foundational roots.</p><p>In this article, I reflect on my nearly 40 years of experience “being agile” and explain what matters. It’s not the frameworks, practices, or tools — it’s the mindset and ways of working. This article is a companion to my 9-part series on Project Management Back to Basics, where I outline the essential components of project success.</p><h3>Agile is a Mindset</h3><p>As Agile rose in popularity, 2-day certification courses became the rage. Scrum Alliance alone reports over <a href="https://www.streetinsider.com/Globe+Newswire/Global+Scrum+Alliance+Community+Surpasses+2+Million+Credentials+Earned/26684433.html">2 million certificate holders</a>. These courses teach the tools but do not impart wisdom. The <a href="https://scrumguides.org/docs/scrumguide/v1/Scrum-Guide-US.pdf">2013 version of the Scrum Guide</a> noted that it was “simple to understand but difficult to master.”</p><p>Adopting Scrum terminology became a poor substitute for agility. Simply overlaying practices without changing culture does not help and often makes things worse. Hour-long daily stand-ups, translating requirements into user stories just to meet the “right” format, or adopting Jira are just a few examples.</p><p>The agile mindset is naturally occurring. Watch children at play without parental supervision. They self-organize. They seek feedback and iterate. These natural tendencies are unlearned through education and the acculturation process in most enterprises. However, it does not have to be that way.</p><p>I lacked formal training when I started managing projects. My education was in Economics, not in engineering or software. My first exposure was building financial models in Lotus 1–2–3 (the now-defunct precursor to Excel). I was applying concepts to a new industry using a new tool and learning through experience. I would review my work (very) often with my boss and adjust what I was doing. It made sense; only later did I learn this was the iterative process.</p><p>My first big project was automating a mission-critical application for the U.S. Treasury Department and Federal Reserve. The lead developer suggested using screen prototyping (wireframes) to document the requirements. The application was essentially built in 6 months. It would have taken at least that long to document the requirements.</p><h3>It’s About the People</h3><p>The Agile Manifesto’s first value statement is “Individuals and interactions over processes and tools.” The 5th and 11th Agile Principles describe building teams around motivated individuals and recognizing that they will develop the best solutions. Jim Collins, in “<a href="https://www.amazon.com/s?k=good+to+great+book+by+jim+collins">Good to Great</a>,” said that great leaders get the right people on the bus and put them in the right seats.</p><p>I have worked with great teams that operate with minimal process and with mediocre teams that rely on prescriptive processes. I prefer the former. It’s the people who solve problems and create innovative solutions. I remember a meeting where we faced a complex technical challenge. We brainstormed, argued, and drew pictures on a whiteboard. We found a solution quickly and remarked that it was easier than expected.</p><p>The challenge and the magic lie in creating a collaborative environment. Colocation and face-to-face interactions can create the right environment. Proximity and workspace design help. The <a href="https://en.wikipedia.org/wiki/Allen_curve">Allen Curve</a>shows that communication declines with greater distance. Technology can bridge the gap for remote, virtual, and hybrid teams, but there is more.</p><p>One of my offices seemed optimized for collaboration. The building was relatively narrow. Managers worked in offices with smoked-glass walls and no doors. Cubicles were low and had glass walls. It was easy to “visit with” and work as a team. Somehow, the quality and depth of collaboration extended to those in other cities, a phenomenon I am still pondering.</p><h3>Create the Culture</h3><p>Culture is paramount. You can have great, smart people. You can talk about an agile mindset. But if you have not created the culture, you will fail.</p><p>The secret to building and leading high-performing teams can be distilled into three simple rules:</p><ul><li>Create psychological safety;</li><li>Empower the team; and</li><li>Organize for simplicity.</li></ul><p>According to <a href="https://rework.withgoogle.com/intl/en/guides/understand-team-effectiveness">Google</a>, psychological safety is the single most important factor in creating high-performing teams. Its presence fosters innovation, creativity, and the passionate pursuit of excellence. Its absence creates a climate of fear and unproductive competition. Tim Clark defined <a href="https://www.linkedin.com/posts/timothyrclark_psychologicalsafety-the4stages-culturechange-share-7284618477984718848-iGll/">four stages of psychological safety</a>:</p><ul><li><strong>Inclusion safety</strong>. You are part of the group.</li><li><strong>Learner safety.</strong> You are comfortable asking questions.</li><li><strong>Contributor safety.</strong> Your opinion matters.</li><li><strong>Challenger safety. </strong>You can question your peers and superiors.</li></ul><p>Creating <a href="https://pmessentials.us/empowering-your-teams/">empowerment</a> is simple. Let people make decisions. However, managers often struggle to let go. It’s scary. I am the boss; shouldn’t I have the answers? What if something goes wrong?</p><p>Relinquishing this control has a profound impact. Team members make good decisions — often better than the boss — and own the outcomes. If it was a bad choice, they are motivated to fix it. And the manager is freed from feeling they need to know and be involved in everything.</p><p>The 10th Agile Principle states that simplicity is the art of maximizing the amount of work not done. If we want teams to be innovative and creative, we need an environment (system) that fosters — rather than stifles — change.</p><p>I worked for companies that were opposites: a move-fast-and-break-things telecommunications provider and a risk-averse financial services company. The first was entrepreneurial (“Agile” had not been coined yet) and a fun, great place to work. The second tried to be agile but was constrained by its command-and-control culture, achieving only limited success.</p><h3>Software (and Solutions) Evolve</h3><p>A satellite needs to be perfect before it is launched. Software — and many other solutions — need only be good enough. Good enough is not bad. It means that sufficient functionality and quality expectations have been met to deliver value.</p><p>Projects often fall prey to the tyranny of the perfect over the good. I had users insist that a non-critical feature be available at launch. After delaying implementation to accommodate that request, they realized it was not what they wanted and asked for it to be removed.</p><p>All projects can benefit from rigorous prioritization and rationalization of features. Clearly define the minimum required features for each release, recognizing that the product will evolve. In the average software product, <a href="https://www.pendo.io/resources/the-2019-feature-adoption-report/">80% of features are rarely or never used</a>.</p><p>What does this mean? Perhaps Agile is not really dead. Agile is an idea, and ideas do not die. Instead, maybe we have reached the limits of exporting Agile practices, much as <a href="https://www.thisamericanlife.org/561/nummi-2015">GM struggled</a> to adopt the lessons learned from its joint venture with Toyota across other facilities. Transferring practices without the culture does not work.</p><p>I believe that we should return to the basics. Focus on mindset, people, culture, and evolving the solution, as they are the preconditions for being agile. The frameworks were meant to serve as guides for those already on the path.</p><p>© 2026, Alan Zucker; Project Management Essentials, LLC</p><p>See related articles:</p><ul><li><a href="https://pmessentials.us/back-to-basics-part-1-state-of-the-union/">Back to Basics, Part 1: State of the Union</a></li><li><a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">Back to Basics, Part 3: The Approach</a></li><li><a href="https://pmessentials.us/back-to-basics-part-4-project-phases/">Back to Basics, Part 4: Project Phases</a></li><li><a href="https://pmessentials.us/back-to-basics-part-5-way-of-working/">Back to Basics, Part 5: Way of Working</a></li><li><a href="https://pmessentials.us/empowering-your-teams/">Empowering Your Teams</a></li><li><a href="https://pmessentials.us/simple-rules-for-high-performing-agile-teams/">Simple Rules for High-Performing Agile Teams</a></li><li><a href="https://pmessentials.us/simple-rules-make-it-easy/">Simple Rules: Make it Easy</a></li><li><a href="https://pmessentials.us/simple-rules-psychological-safety/">Simple Rules: Psychological Safety</a></li></ul><p>To learn more about our training and consulting services or subscribe to our newsletter, visit our website: <a href="http://www.pmessentials.us/">http://www.pmessentials.us/</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d88c926b9968" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Back to Basics, Part 9: Close]]></title>
            <link>https://alan-pmessentials.medium.com/back-to-basics-part-9-close-6c65d8e3b49e?source=rss-aa503288162e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c65d8e3b49e</guid>
            <category><![CDATA[agile-project-management]]></category>
            <category><![CDATA[project-closure]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Alan Zucker]]></dc:creator>
            <pubDate>Tue, 06 Oct 2026 23:17:26 GMT</pubDate>
            <atom:updated>2026-10-06T23:17:26.791Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xVKKRvrNVFuc6YQo03ecCg.png" /></figure><p>The project’s Closing Phase should be a time for celebration. We did it. We delivered value to our stakeholders within a reasonable timeframe and cost. Congratulations!</p><p>Often, Closing feels more like the end of a marathon. You are exhausted, and your body aches. You performed worse than you planned, and you question why you entered this race in the first place.</p><p>A luxury apartment building was built in Washington, DC, offering commanding views of the city. Hosting a Presidential Inauguration event was planned to anchor its grand opening ceremonies. Delays in final permitting foiled those plans and dashed what would have been an amazing celebration of the project.</p><p>The key to a successful Close is planning. Much of the groundwork occurs during the Planning and Execution phases. Proactively managing product quality and stakeholder engagement is critical. The Closing Phase includes three primary components: final review and acceptance, transition or deployment, and the administrative close. Then there is the optional, but recommended, step of recognition.</p><p>Active preparation for the Close should begin toward the end of execution. Build the detailed timeline and checklists. Monitor the process to confirm quality. Re-engage key stakeholders and review the transition plans.</p><p>This is the last article in the “Back to Basics” series, highlighting the project management practices that lead to better, more reliable outcomes. Prior articles described the <a href="https://pmessentials.us/back-to-basics-part-4-project-phases/">operating framework</a>, the processes for <a href="https://pmessentials.us/back-to-basics-part-6-initiation/">initiating</a>, <a href="https://pmessentials.us/back-to-basics-part-7-planning/">planning</a>, and <a href="https://pmessentials.us/back-to-basics-part-8-execution/">executing</a> a project, as well as the <a href="https://pmessentials.us/back-to-basics-part-5-way-of-working/">ongoing work</a> we do throughout our projects.</p><h3>Final Review and Acceptance</h3><p>Projects are expected to create value, delivered through products, services, and results. Products are tangible outputs with (ideally) clear specifications and acceptance criteria. Services, such as consulting, are often measured by the completion of well-defined deliverables or outcomes.</p><p>The Charter, which comes from the Initiation phase, defines the project’s “what,” “why,” and acceptance/exit criteria. The “what” outlines the delivery outcomes. The “why” defines the value proposition. The charter also identifies “who” will approve the final delivery.</p><p>In the Planning stage, expectations are crystallized. Predictive projects define requirements up front. Agile establishes high-level expectations at the beginning and defines detailed expectations for each iteration. Hybrid projects must also establish expectations; however, they may adopt more Predictive or Agile practices.</p><p>Quality planning is also an important component, and Predictive and Agile approaches handle it differently. A best practice is to build quality into every step. As Deming said, “You cannot inspect quality into a product.”</p><p>The Project Management Plan specifies who approves final project delivery and how approvals are obtained. Approvals may be obtained via an automated system, email, or a formal meeting. As part of Closing, any known gaps, issues, or unmet requirements should be documented and communicated.</p><h4>Predictive Projects</h4><p>Predictive projects that deliver tangible outcomes have a well-defined set of requirements and technical specifications. Successful service deliveries clearly outline expectations, outcomes, and artifacts. Establishing these expectations reduces the likelihood of misunderstandings and disappointments.</p><p>A traceability matrix is often used to track requirements through design, build, test, and acceptance. Although cumbersome to build and maintain, the matrix ensures a comprehensive accounting of deliverables. Walkthroughs and checklists are other options for reviewing deliverables and ensuring the work is complete and acceptable.</p><p>Incremental municipal code inspections are required for construction projects. The rule of thumb is that before it’s covered, it’s inspected. The final certificate of occupancy confirms that all quality checks have been met. Then there is an owner walkthrough with a final “punch list” to ensure it meets their expectations.</p><h4>Agile Projects</h4><p>Agile projects do not establish detailed requirements and scope upfront. High-level objectives and expectations are set at the start of the project. A charter or similar document should be created for Agile projects to outline the objectives and acceptance criteria.</p><p>On Scrum projects, needs and expectations are progressively refined through the product backlog, which contains a prioritized list of features and user stories. As features and stories move up the backlog, they should have clear, testable acceptance criteria. The Product Owner works closely with the Team to review completed stories and features, confirming that they meet the intended need and acceptance criteria. Stakeholder feedback is gathered during the Sprint Review.</p><p>The Team and Product Owner collaborate to define the Definition of Done, which serves as the quality checklist for each completed user story. This may include requirements for system, integration, security, and regression testing, etc. DevOps toolchains can automate many of these steps, streamlining the effort to build, test, and deploy high-quality code.</p><p>Kanban teams build quality into the workflow by defining ready (entrance) and done (exit) criteria for each step. While Kanban teams are not required to have a Product Owner, they should define who provides approval and when approval is required.</p><h3>Deployment/Transition</h3><p>While deploying or transitioning the project’s deliverables is a major milestone, it is not the end of the project. Implementing a new software system or turning over the new building marks the end of construction. However, the adoption of the new technology or the use of the new structure can be equally critical.</p><p>Large software projects and organizational change initiatives often fail to adequately plan for what happens next. Transition planning is often underappreciated yet is a critical component of project success. Planning for organizational change can improve adoption. Reorganizations, improvement initiatives, and the implementation of new enterprise software systems need to account for how people respond. Operational documentation, training, and proactive communications can help avoid potential issues.</p><h3>Administrative Close</h3><p>During the Administrative Close, logistics are finalized. Contracts are closed, invoices are paid, project finances are settled, and equipment is returned. The project team is disbanded.</p><p>Project managers and sponsors should plan for this phase. Ensure sufficient time and support to complete all required work. The project does not end with turnover or deployment. Some items may take several weeks or longer to complete. Financials may take a month or two to process before they are finalized in the accounting systems.</p><p>Continuous improvement practices — such as the Agile retrospective — help teams incrementally identify and implement changes throughout the project. Depending on the project and organization, a formal lessons-learned process may also be used to benefit future efforts. A less formal final reflection may help the team achieve closure.</p><h3>Recognition</h3><p>While not required, recognizing the team’s contribution can conclude the effort on a positive note and leave fond memories. People may have spent long hours and prioritized the project over other things. A kind word or small token of appreciation goes a long way. My home office is adorned with mementos from past projects.</p><p>Recognition can take many forms: Formal or informal gatherings. Personal thank you notes. Paper plate awards. For teams creating buildings or other structures, a private tour will allow them to share their pride with friends and family.</p><p>We want to avoid this <a href="https://barrypopik.com/blog/six_phases_of_a_project_enthusiasm_disillusionment_panic">satirical view</a> of the project lifecycle from the 1970s. The last three phases of a project are: the search for the guilty, the punishment of the innocent, and the praise of the non-participants.</p><p>Closing brings both the project and this Back-to-Basics series to an end. Successful project management does not require unnecessarily complex processes, tools, and methodologies. It requires consistently applying fundamental practices, intentionally adapting them to the project’s context, and remaining focused on delivering value.</p><p>© 2026, Alan Zucker; Project Management Essentials, LLC</p><p>See related articles:</p><ul><li><a href="https://pmessentials.us/closing-a-project-ask-the-right-questions/">Closing a Project: Ask the Right Questions</a></li><li><a href="https://pmessentials.us/back-to-basics-part-1-state-of-the-union/">Back to Basics, Part 1: State of the Union</a></li><li><a href="https://pmessentials.us/back-to-basics-part-2-principles/">Back to Basics, Part 2: Principles</a></li><li><a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">Back to Basics, Part 3: The Approach</a></li><li><a href="https://pmessentials.us/back-to-basics-part-4-project-phases/">Back to Basics, Part 4: Project Phases</a></li><li><a href="https://pmessentials.us/back-to-basics-part-5-way-of-working/">Back to Basics, Part 5: Way of Working</a></li><li><a href="https://pmessentials.us/back-to-basics-part-6-initiation/">Back to Basics, Part 6: Initiation</a></li><li><a href="https://pmessentials.us/back-to-basics-part-7-planning/">Back to Basics, Part 7: Planning</a></li><li><a href="https://pmessentials.us/back-to-basics-part-8-execution/">Back to Basics, Part 8: Execution</a></li><li><a href="https://pmessentials.us/project-success-implementation-and-adoption/">Project Success: Implementation AND Adoption</a></li></ul><p>To learn more about our training and consulting services or subscribe to our newsletter, visit our website: <a href="http://www.pmessentials.us/">http://www.pmessentials.us/</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c65d8e3b49e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Back to Basics, Part 8: Execution]]></title>
            <link>https://alan-pmessentials.medium.com/back-to-basics-part-8-execution-b83cdaf709d4?source=rss-aa503288162e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b83cdaf709d4</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[hybrid-project-management]]></category>
            <dc:creator><![CDATA[Alan Zucker]]></dc:creator>
            <pubDate>Mon, 07 Sep 2026 19:13:51 GMT</pubDate>
            <atom:updated>2026-09-07T19:13:51.344Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h_0a3O6Q7yomSEWQ7XcBPw.png" /></figure><p>Execution is the heart of successful project management.</p><p>Execution is where we build and deliver products and services, creating value for our stakeholders. We spend 60% to 80% of our time and budget on this phase.</p><p>During the Planning Phase, we set expectations — how the project will be managed, the expected scope, schedule, and cost, as well as the desired level of quality and risk. In execution, we manage these expectations. In standard terms, we monitor and control the project.</p><p>Execution is where things can go terribly wrong. The project had a compelling business case. The scope, schedule, and cost were clearly defined. The requirements and design were approved. Everything was great until development started. Design changes were accepted without review. Resources were hired without regard to the staffing plan or budget. The only surprise was nobody realized the project was “off the rails.”</p><p>Project managers are accountable for the outcomes, but generally not responsible for doing the work. Their role is to oversee the process and ensure everything stays on track. However, it often feels like trying to teach your child to drive. You want to grab the steering wheel or press the brake. But you cannot reach.</p><p>“Back to Basics” is a series of articles that highlights the project management practices that lead to better, more reliable outcomes. Prior articles covered the <a href="https://pmessentials.us/back-to-basics-part-1-state-of-the-union/">state of the industry</a>, the importance of establishing <a href="https://pmessentials.us/back-to-basics-part-2-principles/">guiding principles</a>, and advice for choosing an <a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">approach</a>. The series then described an <a href="https://pmessentials.us/back-to-basics-part-4-project-phases/">operating framework</a>, the processes for <a href="https://pmessentials.us/back-to-basics-part-6-initiation/">initiating</a> and <a href="https://pmessentials.us/back-to-basics-part-7-planning/">planning</a> a project.</p><h3>Manage the System</h3><p>Project managers play a critical role in shaping the processes, systems, and environment of how work is performed. Deming believed that the system determines 94% of performance.</p><p>Systems thinking recognizes that a project is a complex ecosystem with unpredictable actions and interactions. What may initially seem insignificant can have a profound impact.</p><p>Consider status reporting. It is often said, what gets measured gets done. What we choose to measure. How we measure it. When we measure it. All these decisions impact project operations, team morale, stakeholder expectations, and many other system components.</p><p>There is an intentional overlap between the <a href="https://pmessentials.us/back-to-basics-part-5-way-of-working/">Way of Working</a> domain and the Execution Phase. Managing stakeholders, risks, actions, issues, change, and quality is necessary throughout the project, with particular focus during execution.</p><h3>Manage Execution</h3><p>The unique nature of each project becomes clear during execution. Planning methods follow similar patterns. For example, iteration planning is industry agnostic, and the same principles apply to creating a good Gantt chart for both construction and software projects. However, remodeling a house is not the same as constructing a bridge, and basic scientific research is different than bringing that product to market.</p><p>While the project’s content may differ, the project manager’s role during execution largely remains the same. They must track progress, communicate status, manage change, ensure quality, and engage stakeholders. The specific practices will vary, but the core role remains consistent. A construction project manager “walks” the site to confirm completion, while a technology project manager also needs to check progress but walks fewer steps.</p><h3>Monitor Performance</h3><p>Project performance extends beyond just scope, schedule, and cost. It also encompasses the softer, less measurable, but equally important areas, such as executive support, stakeholder engagement, communication effectiveness, team performance, vendor reliability, quality, and risk — to name a few. Gaps between expectations and reality are early warning signs and predictors of trouble.</p><p>Performance expectations are defined during the Planning Phase. More traditionally managed projects will formally define a baseline scope, schedule, and cost. Other performance measures may also be identified. The metric, the method for measuring it, acceptable variances, etc., should be documented in the project management plan or a similar document.</p><p>Scope, schedule, cost, and quality are primary performance domains of every project. However, the tools and practices for managing performance will vary. Predictive projects use Gantt charts, critical path analysis, and (sometimes) earned value to track the schedule. Excel is the default for integrating budget, forecast, and actual data into a consumable analysis.</p><p>Agile teams focus on the product backlog to manage value delivery and use burn-up/burn-down and velocity charts to track team performance. Agile prefers visual management tools. As Jeff Sutherland said, Scrum is meant to be self-reporting.</p><p>The importance of managing scope, schedule, cost, quality, and risk varies by project. When I managed software projects, the typical priority order was schedule, cost, scope, and then quality. External factors often set deadlines. Cost and scope needed to be reasonably close, and quality just had to be “good enough to ship” — we could fix minor bugs later. When we renovated our home, quality was the primary focus. Scope and cost were secondary, and schedule was the least important. We wanted it done right.</p><h3>Communicate Status</h3><p>Clearly articulating status is critical to maintain stakeholder support and engagement. Many project managers have a detailed understanding of progress, issues, and risks, but struggle to communicate effectively. They get lost in the minutiae, and what should be a 5-sentence highlight becomes a 10-minute discourse.</p><p>Communicating status is an art that takes time and practice to perfect. It starts with understanding the stakeholders’ primary concerns. Organizational leaders and customers’ primary concern: “Is the project OK?” Or, do they need to worry? Finance people focus on the money; they want to know whether you are going to be over budget.</p><p>A straightforward template for communicating status is:</p><p>1. At a high level, is the project on or off track? If your organization uses RAG (red, amber, green) indicators, use them.</p><p>2. What are the critical issues? And what steps are being taken to address them?</p><p>3. What are the primary risks? And what are the planned response strategies?</p><p>4. Is the project expected to be completed within budget?</p><p>5. What “asks” do you have for leadership? What help do you need?</p><h3>Manage Quality</h3><p>Quality includes both “product” and process. What we deliver and how we produce it matter. In the Planning Phase, we should determine how to manage the process and control output quality. In execution, we execute these plans, measure the outcomes, and adjust as needed.</p><p>Product quality ensures that outputs meet technical specifications and customer needs. History is replete with popular products that did not meet safety or regulatory standards. Technically beautiful products that fail to be adopted often do not address a customer need — for example, the Segway Scooter.</p><p>When creating physical products, process quality generally refers to adherence to safety and regulatory requirements. For services, it may refer to adherence to standards and process guidelines. Regardless of the project type, continuous improvement and refinement are strongly encouraged.</p><h3>Manage Change</h3><p>All projects are subject to change. The objective of change management is to ensure an orderly process for identifying, assessing, deciding, approving, communicating, and confirming changes. Creating an orderly, well-understood, and generally agreed-upon process is the key to successful change management. This includes changes to the process and the product or service being delivered.</p><p>Predictive and Agile projects manage change very differently. Predictive projects scrutinize change requests to avoid adverse impacts to schedule or cost, and to ensure the desired change adds value. Agile embraces change. Changing priorities are managed through the product backlog. Changes in the current iteration are discouraged, but accommodating them in upcoming iterations is encouraged.</p><p>© 2025, Alan Zucker; Project Management Essentials, LLC</p><p>See related articles:</p><ul><li><a href="https://pmessentials.us/the-5-point-project-status-6-tips-for-effective-status-reporting/">5-Point Project Status + 6 Tips for Effective Status Reporting</a></li><li><a href="https://pmessentials.us/back-to-basics-part-1-state-of-the-union/">Back to Basics, Part 1: State of the Union</a></li><li><a href="https://pmessentials.us/back-to-basics-part-2-principles/">Back to Basics, Part 2: Principles</a></li><li><a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">Back to Basics, Part 3: The Approach</a></li><li><a href="https://pmessentials.us/back-to-basics-part-4-project-phases/">Back to Basics, Part 4: Project Phases</a></li><li><a href="https://pmessentials.us/back-to-basics-part-5-way-of-working/">Back to Basics, Part 5: Way of Working</a></li><li><a href="https://pmessentials.us/back-to-basics-part-6-initiation/">Back to Basics, Part 6: Initiation</a></li><li><a href="https://pmessentials.us/project-data-visualization/">Project Data Visualization</a></li><li><a href="https://pmessentials.us/project-status-is-subjective-status-metrics/">Project Status is Subjective: Status Metrics</a></li></ul><p>To learn more about our training and consulting services or subscribe to our newsletter, visit our website: <a href="http://www.pmessentials.us/">http://www.pmessentials.us/</a>.</p><p>Watch the trailer: <a href="https://youtu.be/ZuSIYu9U6YA">https://youtu.be/ZuSIYu9U6YA</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b83cdaf709d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Modern Project Management: Proven Hybrid Practices]]></title>
            <link>https://alan-pmessentials.medium.com/modern-project-management-proven-hybrid-practices-233087cd5fba?source=rss-aa503288162e------2</link>
            <guid isPermaLink="false">https://medium.com/p/233087cd5fba</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[hybrid-project-management]]></category>
            <dc:creator><![CDATA[Alan Zucker]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 21:17:40 GMT</pubDate>
            <atom:updated>2026-07-31T21:17:40.285Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8BYEQbHeKy5xugNhVVJCSg.png" /></figure><p>Project management is rapidly evolving. Our modern world is marked by uncertainty, ambiguity, and complexity. To succeed, project managers must anchor on basic principles and adopt proven methods from various approaches, frameworks, and strategies.</p><p><a href="https://quoteinvestigator.com/2021/03/03/not-change/">Jeff Bezos</a> said in 2012 that he could not predict what the world would look like in ten years. His strategy was to build a business based on things that wouldn’t change. Consumers want low prices, fast delivery, and a large selection of items. Instead of worrying about the unknowns, Amazon focused on the pillars of certainty.</p><p>The <a href="https://hbr.org/2021/11/the-project-economy-has-arrived">project economy</a> describes how organizations increasingly depend on projects to generate value beyond their usual operations. However, achieving success remains difficult. <a href="https://www.mckinsey.com/business-functions/mckinsey-digital/our-insights/delivering-large-scale-it-projects-on-time-on-budget-and-on-value">McKinsey</a> estimates that large IT projects go over budget by 45%, miss their deadlines by 7%, and provide 56% less value than expected. <a href="https://pmessentials.us/successful-projects-really-know/">Standish Group surveys</a> found that, on average, only about a third of projects meet the triple constraints. PMI’s newly introduced <a href="https://www.pmi.org/-/media/pmi/documents/public/pdf/learning/thought-leadership/project_success_report_2024.pdf">Net Project Success Score</a>indicates the industry average is an unimpressive 36 out of 100.</p><p>Organizations are shifting from Predictive and Agile to Hybrid approaches, according to <a href="https://www.pmi.org/learning/thought-leadership/future-of-project-work">PMI</a>.</p><p><a href="https://www.capterra.com/resources/2025-pm-software-trends/">Capterra’s latest global survey</a> finds hybrid adoption at 41 percent, nearly double the 2021 figure. AI will further disrupt how projects are estimated. <a href="https://www.gartner.com/en/newsroom/press-releases/2019-03-20-gartner-says-80-percent-of-today-s-project-management">Gartner predicted</a> that 80 percent of today’s project management tasks could be automated by 2030.</p><p>What should project managers do? Follow Amazon’s lead. Concentrate on what we know is important and will not change.</p><p>We know what stakeholders want. They seek value from their investment. They prioritize predictability — knowing how much and when. They also desire flexibility — recognizing that priorities and needs will change, and the project must adapt accordingly.</p><p>We should prioritize proven, well-known practices that lead to project success rather than rigidly adhering to a specific approach, framework, or methodology. Be intentional. Make decisions based on the context. Focus <a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">on the basics</a> and execute flawlessly.</p><h3>Building Hybrid Fluency</h3><p>Project approaches are often viewed as a spectrum, with Predictive and Agile at the extremes and Hybrid in the middle. A broader view shows a <a href="https://pmessentials.us/hybrid-project-management-part-1-what-is-hybrid/">triangular palette of project management styles</a>, with Lean and Kanban serving as the third legs. The interior area reflects the many available options.</p><p>Most project managers are proficient with Predictive practices. Building hybrid fluency means adding Lean, Agile, and Kanban to their foundational knowledge base.</p><p>Alistair Cockburn and <a href="https://martinfowler.com/bliki/ShuHaRi.html">Martin Fowler</a> — two of the Agile Manifesto signatories — describe using the ancient Japanese <em>Shu-Ha-Ri</em> model to illustrate how expertise develops. In the <em>Shu</em> stage, you follow the mechanics of frameworks and practices. Once you become proficient, you start adjusting practices during the <em>Ha</em> stage. At the <em>Ri</em> stage, you go beyond individual frameworks and practices.</p><p>Hybrid fluency is about understanding and appreciating the rich tools and practices at our disposal. It is defining options and seeing opportunities to deliver projects more effectively.</p><p>The following principles, practices, and frameworks are the building blocks of hybrid fluency:</p><p><strong>Lean</strong> evolved from manufacturing and outlines a set of principles for organizing work. The focus is on delivering value and minimizing waste. Lean emphasizes the importance of leadership, empowerment, continuous improvement, and flow in reaching these objectives.</p><p>Adopting a Lean mindset allows project managers to look beyond just delivering a solution and to understand the entire process. It fundamentally transforms how we lead and manage, encouraging us to unlock the full potential of our teams.</p><p><strong>Value streams</strong> trace a customer’s journey. The journey begins with a customer’s need and ends with it being fulfilled. The customers may be external or internal. Adopting a customer-centric view and mapping their experience allows us to identify opportunities to reduce waste and improve value delivery.</p><p><strong>Kanban</strong> is a set of principles that focus on creating flow. Kanban can help individuals and teams be more effective by emphasizing delivering value rather than just staying busy. Any project team can benefit from Kanban and visual project management practices.</p><p><strong>Scrum</strong> is the most common Agile framework and defines a set of practices and roles that enable agility. Scrum teams deliver value in short increments (sprints) that are generally 2-weeks long. They receive feedback from their stakeholders and customers that informs future development.</p><p>Scrum practices improve project success. The team is empowered and actively engaged in delivering the solution. Short development cycles foster a sense of urgency. The inspect-and-adapt loop ensures alignment with stakeholder expectations.</p><p>The <strong>Scaled Agile Framework (SAFe)</strong> is designed to support program- and enterprise-level initiatives. It uses cadence (coordinated 2-week delivery cycles) and synchronization (quarterly big-room planning) to manage the efforts of multiple Agile teams. As a comprehensive framework that incorporates multiple principles and practices, it is increasingly adopted by large corporations and government agencies.</p><p><strong>Disciplined Agile</strong> is an approach-agnostic toolkit — a curated repository of project management practices. Instead of being haphazard, project managers and teams can use this toolkit to be deliberate in improving their ways of working.</p><p>The <strong>Agile Value Management Office (VMO) </strong>applies Lean/Agile principles and practices to portfolio management and enterprise value delivery. It centers on four key themes:</p><ul><li><strong>Value acceleration.</strong> Delivering measurable business value while enabling organizational agility,</li><li><strong>Lean portfolio management.</strong> Efficiently allocating resources and reducing waste through value streams,</li><li><strong>Adaptive governance and risk management.</strong> Enabling dynamic decision-making while actively mitigating risk, and</li><li><strong>Strategic alignment and execution</strong>. Supporting organizational goals and improving execution.</li></ul><p>Amazon built its strategy on the constants. Project management can do the same. New tools, methodologies, and frameworks will be created. Best practices will keep evolving. Instead of chasing trends, successful project managers build their work on proven hybrid practices and principles.</p><p>The <em>Modern Project Management: Proven Hybrid Practices</em> <a href="https://lithespeed.com/modern-project-manager/">course</a> was designed to help project managers develop fluency in Lean, Agile, and Kanban practices. You cannot become an expert in a day, but you can learn where to look and what to do. Understanding the options, seeing proven tools in practice, and recognizing the possibilities will drive better outcomes.</p><p>© 2026, Alan Zucker; Project Management Essentials, LLC</p><p><strong>See related articles:</strong></p><ul><li><a href="https://pmessentials.us/back-to-basics-part-2-principles/">Back to Basics, Part 2: Principles</a></li><li><a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">Back to Basics, Part 3: The Approach</a></li><li><a href="https://pmessentials.us/disciplined-agile-safe/">Disciplined Agile &amp; SAFe</a></li><li><a href="https://pmessentials.us/hybrid-project-management-part-1-what-is-hybrid/">Hybrid Project Management: Part 1, What is Hybrid?</a></li><li><a href="https://pmessentials.us/hybrid-project-management-part-3-picking-the-practices/">Hybrid Project Management: Part 4, Picking the Practices</a></li><li><a href="https://pmessentials.us/project-frameworks-understand-the-choices/">Project Frameworks: Understand the Choices</a></li><li><a href="https://pmessentials.us/scrum-vs-kanban-choose/">Scrum vs. Kanban: What to Choose?</a></li></ul><p>To learn more about our training and consulting services or subscribe to our newsletter, visit our website: <a href="http://www.pmessentials.us/">http://www.pmessentials.us/</a>.</p><p>Watch the trailer: <a href="https://youtu.be/CNs70w5gOZo">https://youtu.be/CNs70w5gOZo</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=233087cd5fba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Back to Basics, Part 7: Planning]]></title>
            <link>https://alan-pmessentials.medium.com/back-to-basics-part-7-planning-377a4caf38c1?source=rss-aa503288162e------2</link>
            <guid isPermaLink="false">https://medium.com/p/377a4caf38c1</guid>
            <category><![CDATA[hybrid-project-management]]></category>
            <category><![CDATA[project-plan]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Alan Zucker]]></dc:creator>
            <pubDate>Sat, 13 Jun 2026 18:40:15 GMT</pubDate>
            <atom:updated>2026-06-13T18:40:15.828Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I1f-U6uHxh2IEpGIJ9u8ZA.png" /></figure><p>Planning is a crucial and highly visible function of project management. The tangible results involve defining the scope, schedule, and cost. But more importantly, planning sets expectations.</p><p>The initiation stage lays the foundation for the project. The charter acts as an operating agreement among the stakeholders. However, as the old saying goes, “the devil is in the details.” Planning is where the rubber meets the road.</p><p>Unfortunately, I have seen too many projects where planning was neglected or rushed. The consequences were predictable. People were very busy, but their efforts did not support a clear outcome. Stakeholders were furious — the projects experienced changes, delays, and cost overruns.</p><p>“Back to Basics” is a series of articles that highlights the project management practices that lead to better, more reliable outcomes. Prior articles covered the <a href="https://pmessentials.us/back-to-basics-part-1-state-of-the-union/">state of the industry</a>, the importance of establishing <a href="https://pmessentials.us/back-to-basics-part-2-principles/">guiding principles</a>, and advice for choosing an <a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">approach</a>. The series then described an <a href="https://pmessentials.us/back-to-basics-part-4-project-phases/">operating framework</a>, the <a href="https://pmessentials.us/back-to-basics-part-5-way-of-working/">ways of working</a>, and the <a href="https://pmessentials.us/back-to-basics-part-6-initiation/">initiation phase</a>.</p><h3>Planning</h3><p>The planning process and its artifacts flow from the <a href="https://pmessentials.us/project-frameworks-understand-the-choices/">project approach</a>. The approach is grounded in understanding the context, goals, needs, technical complexity, change costs, and team capabilities. Though Predictive, Agile, and Hybrid projects appear very different, their foundations are the same.</p><p>The primary outputs of planning are the project management plan and the project plan, which are often conflated. The project management plan outlines <strong>how</strong> the project will be executed. The project plan describes <strong>what, when, </strong>and<strong> how much. </strong>The value of these artifacts lies in the understanding and expectations they represent — not in the documents themselves.</p><h3>The Project Management Plan</h3><p>The <a href="https://pmessentials.us/unlock-the-power-of-the-project-management-plan/">project management plan</a> outlines how the project will be managed and executed. It sets expectations for both the team and external stakeholders regarding the processes, tools, and methods to be used. It defines the cadence, type, and methods for all stakeholder engagement, from status reporting to risk reviews.</p><p>The project management plan serves as the authoritative source for understanding how the project will operate. It integrates the processes, reviews, governance, performance measures, and baselines needed to guide execution. It also includes the baseline scope, schedule, cost, and other performance measures.</p><h3>The Project Plan</h3><p>Regardless of the project or approach, a key initial step is establishing scope, schedule, and cost expectations. The tools and documents used to do this will differ. However, not setting these expectations with sponsors and other important stakeholders is an early sign of potential problems.</p><h3>Predictive Planning</h3><p>Predictive project planning involves defining and breaking down the scope, creating the schedule, and estimating the budget. Although the process seems linear, it is iterative. Define and decompose the scope, develop the schedule, identify the necessary resources, and estimate the budget. The team and stakeholders negotiate what can reasonably and feasibly be achieved given the constraints.</p><p>A primary output of planning is the baseline scope, schedule, and cost. The baselines are agreed-upon metrics used to monitor and control the project’s performance. Any changes to the baseline are approved through the change process outlined in the project management plan.</p><p>A key assumption of predictive planning is that requirements and scope are clear and well-defined. The predictive approach works best for projects with high change costs, like road or bridge construction — once you start pouring concrete, you don’t want to change the plans.</p><p>Common planning process outputs for a predictive project include:</p><p>· <strong>Scope Statement</strong>. Unambiguously describes the project scope (deliverables), inclusions, and exclusions. The project requirements are an input to the scope statement. The scope statement, in turn, is a primary input to the creation of the work breakdown structure and scope baseline.</p><ul><li><strong>Work Breakdown Structure (WBS)</strong>. The WBS is a hierarchical decomposition of the project’s scope. Work packages represent the lowest level of detail.</li><li><strong>Scope Baseline.</strong> The agreed-upon project scope.</li><li><strong>Schedule Baseline.</strong> The agreed-upon project schedule.</li><li><strong>Cost Baseline.</strong> The agreed-upon project cost.</li></ul><h3>Agile Scrum Planning</h3><p>Agile is optimized for projects where change costs are low, and the specific requirements and scope are unclear. Teams regularly deliver small increments of work, typically every two weeks, to iteratively refine the solutions. Stakeholders provide feedback that guides future planning for iterations.</p><p>Agile inverts the triple-constraint. It prefers long-standing, stable teams, making it easier to estimate costs, which are simply the team’s monthly run rate. Since the scope is emergent, the project duration and cost can be set externally by senior leadership — how much should be invested? Therefore, the scope can be adjusted to fit within the time and cost constraints.</p><p>Agile planning happens at multiple levels and time horizons. The product vision and product roadmap outline the strategic direction. The roadmap provides a time-phased view of the expected functionality or features and is typically reviewed with stakeholders quarterly.</p><p>The product backlog connects strategy to tactical execution. The product backlog is a prioritized list of planned deliverables and may be reviewed monthly. Items can be added, dropped, and reprioritized.</p><p>Iteration planning transforms the product backlog into the iteration backlog. The iteration backlog specifies what the team will deliver over the next two weeks. During the iteration planning meeting, the team estimates its capacity — how much work they believe they can complete. Then, items are moved from the product backlog to the iteration backlog until the capacity is filled.</p><p>Most Scrum teams use story points to estimate the size of work items. Story points are a composite measure of size, complexity, uncertainty, and other factors. The average number of story points the team completes per iteration serves as the basis for estimating their capacity.</p><h3>Agile Kanban Planning</h3><p>Kanban projects share many planning attributes with Scrum — stable, longstanding teams make cost estimating straightforward. Kanban teams have greater flexibility to prioritize and pivot than Scrum teams because they are not constrained by the 2-week cycle, allowing backlog priorities to be adjusted sooner and releasing working software when ready.</p><p>Kanban teams focus on optimizing flow. The goal is to deliver work consistently and predictably while improving efficiency and effectiveness. Reducing bottlenecks and eliminating waste are core principles. Instead of using story points like Scrum, they measure throughput and use statistical models to estimate how quickly work can move through the system.</p><p>Planning scope and time become flexible. One Agile concept is “bringing work to the team.” In other words, a high-performing team can support multiple applications by managing new features, improvements, maintenance, and support requests. The order of work in the backlog becomes the primary factor determining what gets delivered and when.</p><h3>Hybrid Planning</h3><p>Planning a hybrid project is complicated because there is no agreed-upon set of practices or artifacts. The underlying approach(es) will determine how planning is carried out. The methods, artifacts, and expectations should be documented in the project management plan. Successful hybrid planning requires greater intentionality because there are fewer established patterns and no universally accepted set of practices.</p><p>Planning establishes the expectations that guide the rest of the project. The specific artifacts and practices will vary, but the objective remains the same: create alignment around what will be delivered, how it will be delivered, and how success will be measured. In the next article, I will explore the execution phase, where plans are translated into results.</p><p>© 2026, Alan Zucker; Project Management Essentials, LLC</p><p>See related articles:</p><ul><li><a href="https://pmessentials.us/back-to-basics-part-1-state-of-the-union/">Back to Basics, Part 1: State of the Union</a></li><li><a href="https://pmessentials.us/back-to-basics-part-2-principles/">Back to Basics, Part 2: Principles</a></li><li><a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">Back to Basics, Part 3: The Approach</a></li><li><a href="https://pmessentials.us/back-to-basics-part-4-project-phases/">Back to Basics, Part 4: Project Phases</a></li><li><a href="https://pmessentials.us/back-to-basics-part-5-way-of-working/">Back to Basics, Part 5: Way of Working</a></li><li><a href="https://pmessentials.us/back-to-basics-part-6-initiation/">Back to Basics, Part 6: Initiation</a></li><li><a href="https://pmessentials.us/gantt-101-building-a-better-project-schedule/">Gantt 101: Building a Better Project Schedule</a></li><li><a href="https://pmessentials.us/project-frameworks-understand-the-choices/">Project Frameworks: Understand the Choices</a></li><li><a href="https://pmessentials.us/unlock-the-power-of-the-project-management-plan/">Unlock the Power of the Project Management Plan</a></li></ul><p>To learn more about our training and consulting services or subscribe to our newsletter, visit our website: <a href="http://www.pmessentials.us/">http://www.pmessentials.us/</a></p><p><a href="https://youtu.be/VFKLYPUWxjY">https://youtu.be/VFKLYPUWxjY</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=377a4caf38c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Back to Basics, Part 6: Initiation]]></title>
            <link>https://alan-pmessentials.medium.com/back-to-basics-part-6-initiation-33b2d2f1d745?source=rss-aa503288162e------2</link>
            <guid isPermaLink="false">https://medium.com/p/33b2d2f1d745</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[hybrid-project-management]]></category>
            <dc:creator><![CDATA[Alan Zucker]]></dc:creator>
            <pubDate>Mon, 04 May 2026 19:39:21 GMT</pubDate>
            <atom:updated>2026-05-04T19:39:21.728Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vGokoefxDYcxj2ZUD57law.png" /></figure><p>We need to do better. Our current project management practices do not predictably deliver value.</p><p>Better project results come from consistently and reliably applying fundamental practices. “Back to Basics” highlights the core principles of simplicity, intentionality, and practicality. Clear, value-driven guidelines and practices enable project teams to make pragmatic, deliberate decisions rather than blindly following rigid standards.</p><p>“Back to Basics” is a series of articles that highlights the project management practices that lead to better, more reliable outcomes. The first six articles covered the <a href="https://pmessentials.us/back-to-basics-part-1-state-of-the-union/">state of the industry</a>, the importance of establishing <a href="https://pmessentials.us/back-to-basics-part-2-principles/">guiding principles</a>, advice for choosing an <a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">approach</a>, a <a href="https://pmessentials.us/back-to-basics-part-4-project-phases/">framework</a>, and the <a href="https://pmessentials.us/back-to-basics-part-5-way-of-working/">way of working</a>.</p><p>This article explains the initiation phase, which establishes the project’s foundation. The outcome is a clear set of commitments and understandings. Without this alignment, stakeholders’ expectations will not be met.</p><p>The CIO mused that a new application might fill an unmet need. A development manager saw this as an urgent request and tasked the team with building it. They proceeded without sponsorship, approval, or a formal charter. After completing the development, the manager reported the achievement to the CIO, hoping for praise. However, he was met with a bewildered and annoyed boss. This was not an official request; the CIO was just musing aloud.</p><h3>Initiation Phase</h3><p>The initiation phase lays the project’s foundation. Before initiation, projects undergo a selection and funding process. Inputs such as the business case, benefits management, and realization plans inform this decision.</p><p>The project charter is the phase’s main artifact. It outlines the project’s context, goals, and opportunities and threats. Ensuring stakeholder alignment on the “what” and “why” is essential to the project’s overall success.</p><p>The project sponsor plays a dual and vital role during the initiation phase. They are accountable to the organization for delivering the benefits defined in the business case. They are also responsible for ensuring the project has the resources and support to succeed.</p><p>The sponsor, along with other organizational leaders, approves the charter. This affirmation can be leveraged by the project manager.</p><h3>Understanding the Context</h3><p>Every project is unique and operates within its own context, and has its own <a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">environmental factors</a>, including:</p><ul><li>The organization’s culture, which encompasses risk tolerance, decision-making practices, and structure;</li><li>The team’s maturity level, skills, trust, and cohesion, and whether co-located or virtual;</li><li>Regulatory, contract constraints, and operating procedures; and</li><li>Stakeholders’ expectations, degree of alignment, and level of engagement.</li></ul><p>Honoring the context is critical to planning and structuring the project. For example, teams in highly structured, risk-averse environments will likely fail if they are required to “be Agile” without sufficient preparation.</p><p>Elements of the context can shift as the project progresses. This can be driven by changes in the operating environment, market conditions, or key stakeholders and their expectations.</p><h3>The Project Charter</h3><p>The project charter, or a similar document, is a critical output of the initiation phase and represents an agreement between the requesting and delivering organizations. It also designates and authorizes the project manager, defining their formal role and decision-making authority. As questions and conflicts emerge, the charter can serve as a resource to “re-ground” stakeholders in the original intent.</p><p>The following are the primary components of the charter:</p><h4>Stakeholder Register and List</h4><p>During the initiation stage, the stakeholder register is created. The register is a detailed, working document used to capture information about stakeholders and analyze their needs. It often includes assessments of stakeholder power, influence, interest, impact, and current versus desired engagement levels. The list is a summary included in the charter.</p><h4>Objectives, High-Level Requirements, and Scope</h4><p>The charter builds on the business case and provides a more refined, elaborated view of the objectives, high-level requirements, and scope. As more stakeholders are engaged as the project moves into the initiation stage, the objectives may shift, and a clearer view of the scope and more detailed requirements will emerge. Project boundaries — what will not be done — may also be documented.</p><p>The charter should clearly define the project’s “what” and “why.” The “what” describes the project’s outputs. The “why” establishes the objective or desired outcome. Incorporated in the “why” is an understanding of the problem to be solved. A robust alternatives analysis should be conducted to ensure the “what” is the most effective way of delivering the “why.”</p><h4>Initial Schedule, Cost, and Performance Measures</h4><p>The detailed project scope, schedule, and cost will be developed during the planning phase. At this point, the goal is to establish consensus on roughly what the project will deliver, how long it will take, and how much it will cost. These are still order-of-magnitude estimates that represent a range of outcomes. Other key performance measures may also be established; common examples include quality and product performance standards.</p><p>Refining the project performance goals is an iterative process as trade-offs are considered and decisions are made. Creating stakeholder alignment will be critical to the project’s ultimate success. Disagreement at this stage will be a strong predictor of future challenges. However, agreement will not guarantee success. Influencing, coalition-building, and decision-making skills will be valuable for creating and maintaining consensus and support.</p><h4>Success Criteria</h4><p>Defining the success or exit criteria at the beginning of the project motivates stakeholders to clarify their expectations and provides the project team with a clear view of success. This can be a valuable forcing function and resolves the “I will know it when I see it” conundrum. Well-established exit criteria may be required to enter the planning phase.</p><h4>Initial Risks, Assumptions, and Constraints</h4><p>Risks are opportunities and threats. At this stage, the focus should be on strategic items that could have a significant impact on the project and may inform requirements, scope, and project approach. Optimism often prevails at this phase; consequently, the risk log should be robust and avoid bias.</p><p>Assumptions are the things we know we don’t know. They can relate to the development and operational environments, and are used to develop initial plans, estimates, and designs. Without assumptions, it is often impossible to proceed. They should be documented and validated as soon as feasible.</p><p>Constraints limit the project and include contracts, operating agreements, regulations, internal procedures, and laws of nature. They represent project boundaries. Documenting the relevant constraints at the appropriate level of detail helps keep the project out of trouble.</p><p>Assumptions and constraints are also project risks and should be cross-populated in the risk log.</p><p>Initiation creates the project’s foundation. In the next article, I will discuss the planning phase, where the expectations are clarified and established.</p><p>© 2026, Alan Zucker; Project Management Essentials, LLC</p><p>See related articles:</p><ul><li><a href="https://pmessentials.us/are-we-aligned/">Are We Aligned?</a></li><li><a href="https://pmessentials.us/back-to-basics-part-1-state-of-the-union/">Back to Basics, Part 1: State of the Union</a></li><li><a href="https://pmessentials.us/back-to-basics-part-2-principles/">Back to Basics, Part 2: Principles</a></li><li><a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">Back to Basics, Part 3: The Approach</a></li><li><a href="https://pmessentials.us/back-to-basics-part-4-project-phases/">Back to Basics, Part 4: Project Phases</a></li><li><a href="https://pmessentials.us/back-to-basics-part-5-way-of-working/">Back to Basics, Part 5: Way of Working</a></li><li><a href="https://pmessentials.us/the-project-charter-lays-the-foundation/">The Project Charter Lays the Foundation</a></li><li><a href="https://pmessentials.us/engage-your-stakeholders/">Engage Your Stakeholders</a></li><li><a href="https://pmessentials.us/managing-project-assumptions-risks/">Managing Project Assumptions &amp; Risks</a></li><li><a href="https://pmessentials.us/assumptions-risks/">Project Assumptions &amp; Risks</a></li><li><a href="https://pmessentials.us/projectsstart-with-what-why/">Projects…Start with What &amp; Why</a></li></ul><p>To learn more about our training and consulting services or subscribe to our newsletter, visit our website: <a href="http://www.pmessentials.us/">http://www.pmessentials.us/</a>.</p><p>Watch the trailer: <a href="https://youtu.be/F7lEi2gg1cA">https://youtu.be/F7lEi2gg1cA</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33b2d2f1d745" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Back to Basics, Part 5: Way of Working]]></title>
            <link>https://alan-pmessentials.medium.com/back-to-basics-part-5-way-of-working-97c5fe07b794?source=rss-aa503288162e------2</link>
            <guid isPermaLink="false">https://medium.com/p/97c5fe07b794</guid>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Alan Zucker]]></dc:creator>
            <pubDate>Thu, 09 Apr 2026 12:28:19 GMT</pubDate>
            <atom:updated>2026-04-09T12:28:19.883Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9IxtJD1g-xBA8bLYRvQaGg.png" /></figure><p>“We know what to do, we just need to do it!”</p><p>I believe that experienced project managers understand the core practices that lead to project success. The existing methodologies, frameworks, and tools are intended to lead to consistent outcomes. However, projects continue to be delivered late, over-budget, and lacking the desired functionality. Failure is rarely a surprise. We could have or should have seen it coming, but we didn’t.</p><p>“Back to Basics” is a series of articles that outlines foundational project management practices that lead to better, more consistent outcomes. My goal is elegant simplicity — reducing complexity and enabling autonomic responses. The first four articles discussed the <a href="https://pmessentials.us/back-to-basics-part-1-state-of-the-union/">state of the industry</a>, the importance of establishing <a href="https://pmessentials.us/back-to-basics-part-2-principles/">guiding principles</a>, advice for selecting the <a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">approach</a>, and a <a href="https://pmessentials.us/back-to-basics-part-4-project-phases/">framework</a> for organizing project work.</p><p>This article outlines the essential way of working and ongoing activities. These activities are the fabric that builds the team’s capabilities, engages the stakeholders, manages the details, and ensures improvement.</p><h3>Lead the Team</h3><p>A project manager’s primary responsibility is to lead the team and foster a culture that maximizes performance. Peter Drucker famously said that “culture eats strategy for breakfast.” In <a href="https://www.jimcollins.com/article_topics/articles/good-to-great.htm">Good to Great</a>, Jim Collins argues that getting the right people on the bus and putting them in the right seats is management’s most important role.</p><p>I identify psychological safety, empowerment, and simplicity as the requirements for creating <a href="https://pmessentials.us/simple-rules-make-it-easy/">high-performing teams.</a> Pushing decision-making to the lowest responsible level enables empowerment. Reducing complexity and eliminating unproductive rules and processes allows teams to thrive.</p><p><a href="https://pmessentials.us/simple-rules-psychological-safety/">Psychological safety</a> is the foundation for creating high-performing teams. <a href="https://www.linkedin.com/posts/timothyrclark_psychologicalsafety-the4stages-culturechange-activity-7284618478961991681-0RIA/">Tim Clarke</a> outlined a four-level model — inclusion, learner, contributor, and challenger safety. His work aligns with Maslow’s <a href="https://en.wikipedia.org/wiki/Maslow%27s_hierarchy_of_needs">Hierarchy of Needs</a> and Patrick Lencioni’s <a href="https://www.tablegroup.com/topics-and-resources/teamwork-5-dysfunctions/">Five Dysfunctions of a Team</a>. The presence of psychological safety fosters trust, engagement, innovation, and creativity. Its absence leads to negative work environments, poor results, and, in extreme cases, tragic disasters.</p><p>Foundational steps to building an empowered and trusting team environment can be achieved by:</p><ul><li>Setting clear objectives and trusting the team to find the best solution,</li><li>Assuming “best intentions” and treating mistakes as learning opportunities,</li><li>Encouraging and valuing diverse perspectives, and</li><li>Shielding the team from external distractions.</li></ul><h3>Engage and Communicate with Stakeholders</h3><p>Engaging and communicating with project stakeholders is critical. User involvement and executive support are the two leading indicators of <a href="https://www.researchgate.net/publication/263849222_The_Chaos_Report">project success</a>. Too often, actively managing these relationships is an early casualty of project <em>busyness</em>. The team prioritizes tactical execution issues over strategic engagement — the project may be on the right track, but the stakeholders are not on board with the direction.</p><p>Stakeholder and communications management should be an ongoing daily, weekly, and monthly set of activities that incorporates the following:</p><p><strong>Stakeholder identification and analysis</strong>. The project manager should actively maintain and update the stakeholder register. New stakeholders will be identified, existing ones may be retired, and their desired involvement may shift.</p><p><strong>Stakeholder engagement, communications, and monitoring. </strong>Stakeholders are engaged through communications. The communications management plan is developed to identify the most effective way to inform and involve stakeholders. These communications can include formal and informal, written communications, and meetings. The project manager should periodically confirm that engagement and alignment are as planned. If not, then adjust.</p><p>Regular communication prevents missteps that can cause failure. Agile incorporates a regular cadence — backlog reviews and iteration demos. Predictive and Hybrid communication plans should also include similar feedback loops.</p><h3>Manage Risks, Actions, and Issues</h3><p>Proactively managing risks, actions, and issues prevents projects from being derailed by unexpected events and ensures that items don’t slip through the cracks. Discipline is the watchword. Small actions can make a big difference. Establish a process and a schedule. Assign ownership and follow-up to maintain accountability.</p><p>Risks are future events that have a likelihood of occurrence and potential impact. Risk events must be clearly articulated, documented in a risk register, assessed, and response strategies developed. Using <em>IF/THEN</em> statements to describe the risk focuses on the outcome, which simplifies identifying specific triggers and responses.</p><p>Issues and action items are items that need to be addressed. Issues are concerns raised by stakeholders. Action items are steps needed to address concerns.</p><p>There is a hierarchy or concentric circle of concern and influence, spanning from project teams to sponsors and executive stakeholders. Risks, actions, and issues are organized for visibility and potential response at each level. Operational and project-level items can remain with the team. Items needing executive action or having strategic impact must be escalated. How items are expressed and communicated should be customized for the target audience.</p><h3>Transfer Knowledge</h3><p>Knowledge transfer leads to consistent execution and serves as a lever for future team growth and maturity. There are two types of knowledge: explicit and tacit.</p><p>Explicit knowledge is straightforward to document and share, such as practice guides, templates, and FAQs that define standard operating procedures. Tacit knowledge consists of experience and wisdom. Project teams require mechanisms to manage both types.</p><p>Explicit knowledge acts as the lubricant that keeps operations running smoothly — people understand what to do, how to do it, and when to do it. Large organizations typically have enterprise project management tools, onboarding processes, and guidance for project lifecycle management. Project-specific procedures and practices should be documented in the project management plan.</p><p>Tacit knowledge is best communicated orally. Creating an environment where wisdom and experience are shared requires proactive management. The design of the working environment, proximity to colleagues, technologies, and formal and informal interactions all play a role.</p><h3>Improve Continuously</h3><p>Kaizen is a foundational Lean principle and promotes making regular, small incremental process changes and improvements. Traditional project lessons learned are conducted at the end of the project and are rarely reviewed and applied to future efforts. Agile introduced post-iteration retrospectives to quickly identify and address issues.</p><p>After each iteration, Agile teams assess their performance. They review people, processes, technologies, and relationships. Then, they propose and implement solutions to the most pressing problem(s) in the next iteration.</p><p>Retrospectives empower teams to address their problems. It shifts ownership from management to the team. This increases buy-in and the likelihood that the solution is viable and effective. It also shortens the time from “pain to gain.”</p><p>Enabling a continuous improvement culture requires effort. Teams may need training in process improvement, facilitation, and problem resolution skills. Our experiences inform and bias our approach. Exposure to “better practices” through tools such as the <a href="https://www.pmi.org/disciplined-agile/da-browser">Disciplined Agile Browser</a> can help teams think outside the box.</p><p>© 2025, Alan Zucker; Project Management Essentials, LLC</p><p>See related articles:</p><ul><li><a href="https://pmessentials.us/are-we-aligned/">Are We Aligned?</a></li><li><a href="https://pmessentials.us/back-to-basics-part-1-state-of-the-union/">Back to Basics, Part 1: State of the Union</a></li><li><a href="https://pmessentials.us/back-to-basics-part-2-principles/">Back to Basics, Part 2: Principles</a></li><li><a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">Back to Basics, Part 3: The Approach</a></li><li><a href="https://pmessentials.us/back-to-basics-part-4-project-phases/">Back to Basics, Part 4: Project Phases</a></li><li><a href="https://pmessentials.us/empowering-your-teams/">Empowering Your Teams</a></li><li><a href="https://pmessentials.us/engage-your-stakeholders/">Engage Your Stakeholders</a></li><li><a href="https://pmessentials.us/knowledge-management-share-the-wisdom/">Knowledge Management: Share the Wisdom</a></li><li><a href="https://pmessentials.us/managing-project-assumptions-risks/">Managing Project Assumptions &amp; Risks</a></li><li><a href="https://pmessentials.us/simple-rules-for-high-performing-agile-teams/">Simple Rules for High-Performing Agile Teams</a></li><li><a href="https://pmessentials.us/simple-rules-psychological-safety/">Simple Rules: Psychological Safety</a></li></ul><p>To learn more about our training and consulting services or subscribe to our newsletter, visit our website: <a href="http://www.pmessentials.us/">http://www.pmessentials.us/</a>.</p><p>Image generated by ChatGPT</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FT0WBmu2_P5w%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DT0WBmu2_P5w&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FT0WBmu2_P5w%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8dd1cc60855de55b1cbce4c2b8dc6523/href">https://medium.com/media/8dd1cc60855de55b1cbce4c2b8dc6523/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97c5fe07b794" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Back to Basics, Part 4: Project Phases]]></title>
            <link>https://alan-pmessentials.medium.com/back-to-basics-part-4-project-phases-a06f7d1e7af1?source=rss-aa503288162e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a06f7d1e7af1</guid>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Alan Zucker]]></dc:creator>
            <pubDate>Mon, 09 Mar 2026 00:04:04 GMT</pubDate>
            <atom:updated>2026-03-09T00:04:04.225Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ykQmxsQYYUIqIN6bz5ZMTg.png" /></figure><p>Project success remains elusive despite the array of methodologies, frameworks, practices, and tools available. Better outcomes will come from mastering and consistently executing foundational practices. Data from <a href="https://www.pmi.org/-/media/pmi/documents/public/pdf/learning/thought-leadership/pulse/pulse-of-the-profession-2018.pdf">PMI</a>, <a href="https://wellingtone.com/state-of-project-management-research">Wellingtone</a>, <a href="https://cmmiinstitute.com/news/press-releases/october-2017/cmmi%C2%AE-institute-reports-fifth-consecutive-year-of">CMMI,</a> and other sources demonstrate that we fail to do the basics.</p><p>“Back to Basics” is a series describing industry-agnostic, context-sensitive project management best practices. The first three articles discussed the <a href="https://pmessentials.us/back-to-basics-part-1-state-of-the-union/">state of the industry</a>, the importance of establishing <a href="https://pmessentials.us/back-to-basics-part-2-principles/">guiding principles</a>, and advice for selecting the <a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">approach</a>.</p><p>This article establishes a framework for organizing project work, primary outcomes, and activities. Defining the lifecycle phases creates a shared vocabulary and taxonomy, which is vital for building a common understanding and expectations.</p><p>The Tower of Babel Effect plagued a Fortune 100 company’s financial restatement. New employees and consulting firms were hired to rebuild its financial reporting infrastructure and establish compliant accounting practices. The lack of a common project framework and language created confusion, misunderstandings, and conflicts.</p><h3>Project Phases or Stages</h3><p>A common taxonomy and shared vocabulary challenge all project types. Project phases or stages are the primary framework for understanding how the project should operate. It sets expectations for the sequencing of activities, outcomes, and artifacts.</p><p>This taxonomy is inspired by the PMBOK® Guide’s focus areas and the Disciplined Agile process goal categories. To be inclusive, synonymous phase titles are included. A project can be described as going through the phases or stages of:</p><p>· <strong>Way-of-Working (Ongoing).</strong> These activities are core disciplines that span the life of the project.</p><p>· <strong>Initiate (Start-Up, or Concept).</strong> The activities undertaken to establish the project’s foundational elements.</p><ul><li><strong>Plan.</strong> The activities that establish expectations for scope, schedule, and cost, as well as define how the project will be managed.</li><li><strong>Execute (Build, Construct, or Create).</strong> The activities to deliver value or create the product, service, or result.</li><li><strong>Close (Transition or Implement).</strong> The activities related to the final acceptance of the project’s outcomes and its administrative closure.</li></ul><p>Every project is unique, and context matters. Consequently, how practices are carried out and the formality of the artifacts will vary based on multiple factors. The project type, regulatory or contractual constraints, and organizational culture and expectations are some primary drivers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mCZh2BFaT0UpCnf7Lt9CmA.png" /></figure><h3>Way-of-Working</h3><p>Way-of-working is not a phase; it is the work performed throughout the project. The intensity and importance of these activities will vary throughout the lifecycle. Primary activities and artifacts are listed below, but this list is not exhaustive.</p><h4>Stakeholder Engagement and Communications</h4><p>Effective stakeholder management is a key to project success. Project managers begin working with stakeholders on the first day and continue until the project is finished. The processes are identifying, assessing, engaging, and monitoring stakeholder engagement. The stakeholder register is the primary artifact.</p><p>Stakeholders are engaged through communications. The management plan outlines the types, frequencies, and key messages to be communicated to stakeholders and other constituencies.</p><h4>Risk</h4><p>Risks are future events that present opportunities or threats. If they are not actively managed, it is less likely that the opportunities will be realized and that the threats will be avoided or mitigated. The primary processes are to identify, assess, plan responses, implement responses, and monitor. The risk register is the primary artifact.</p><h4>Issues and Actions</h4><p>Issues and actions are identified items that need to be addressed. Managing these items is an essential “housekeeping” task. Issues represent concerns, while actions are tasks that must be completed. Both should be tracked in a register and actively overseen. The issues and action item log is the primary artifact.</p><h3>Initiate Phase</h3><p>The objective of the initiate phase is to clearly define the project goals and outcomes. The project sponsor, owner, senior management, and governance organizations should play significant roles to ensure the project aligns with the organization’s strategy and needs. Engaging the project manager early is preferred but not required.</p><p>The starting point for the initiate phase is an approved business case or similar funding approval document. For large infrastructure projects, this phase may take years. For small projects, it may be days or weeks.</p><p>The primary output of the initiate stage is the project charter or a similar document. The charter serves as a critical foundational document that establishes a shared understanding between the requesting and delivering parties. It elaborates on and refines the objectives, defines success or acceptance criteria, and sets initial scope, schedule, and cost parameters.</p><h3>Plan</h3><p>The goal of the planning phase is to create artifacts that guide the rest of the project. Planning is more than just creating documents; it sets expectations. As Eisenhower said, “Plans are useless, but planning is indispensable.” The process of evaluating what needs to be done, how to do it, exploring options, identifying risks, and recognizing interdependencies is crucial. However, we must also recognize that even the best plans often change due to real-world factors.</p><p>The project type, approach, and multiple other factors will influence the preferred planning process, artifacts, and deliverables. At a minimum, the project’s scope, schedule, cost/budget, and project management plan should be documented.</p><p>The project management plan, or a similar document, is the opportunity to describe how the project will be executed and managed. The project approach, guidelines, management reviews, stakeholder and communication management, and performance reporting are among the critical components.</p><h4>Planning Predictive Projects</h4><p>Predictive methodologies generally have established processes for defining scope, schedule, and cost baselines, which then act as key performance indicators. These measures set initial expectations for the team and stakeholders. To maintain ongoing alignment, any changes to the baseline must follow the approved change management process.</p><p>The scope baseline includes the scope statement and work breakdown structure (WBS). The scope statement clearly defines what will be delivered. The WBS decomposes the scope into smaller work packages that are small enough to estimate and assign.</p><p>The schedule is derived from the WBS and typically displayed as a Gantt chart, highlighting the critical path. The budget accounts for contingency reserves (known risks) and management reserves (unknown risks).</p><h4>Planning Agile Projects</h4><p>Agile projects are planned differently from predictive ones. Agile favors ongoing, iterative planning rather than defining everything upfront. Initially, a product vision along with time and cost expectations must be established. The product vision sets the long-term goals. Since Agile scope is emergent, the investment decision (time and cost) can be set as external constraints.</p><p>The product roadmap and backlog are key artifacts for defining the product and scheduling functionality delivery. The product owner should regularly review and update these with stakeholders to ensure ongoing alignment.</p><p>The project team plans its upcoming work at the beginning of each iteration. During the planning meeting, they decide what can be completed. The team also reviews and refines product backlog items to ensure they are understood, well-defined, and ready to work on when they enter the iteration.</p><h4>Planning Hybrid Projects</h4><p>Hybrid projects lack a standard approach because practices can combine both predictive and agile methods. Therefore, it is necessary to define the practices and understand the project scope, schedule, and cost. The project management plan must also outline how planning will be carried out.</p><h3>Execution Phase</h3><p>The execution phase is when the team delivers the product, service, or result that creates value. Every project will have its unique practices, processes, and artifacts. In addition to the ongoing activities, the primary activities for the execution phase include:</p><h4>Performance Measurement and Status Reporting</h4><p>PMI <a href="https://www.pmi.org/-/media/pmi/documents/public/pdf/about/purpose/pmi-more-2025.pdf?rev=39376cfad0e847c9b004067b52fa0115">research</a> found that establishing and tracking performance measures improves the chances of project success. Performance management is broadly defined as comparing planned versus actual performance and taking appropriate actions. Monitoring scope, schedule, and cost are the standard metrics, but others may be equally important.</p><p>Status reporting involves regularly updating stakeholders about project performance. The format, frequency, method, and details can vary depending on the approach. Agile projects prioritize transparency and use “information radiators” to show progress. Predictive projects follow specific, established formats and metrics.</p><h4>Change Management</h4><p>Change management is a broadly defined process. The typical steps include identifying, logging, assessing, making decisions, communicating, and verifying. The specific practices, processes, and artifacts will vary.</p><h3>Close Phase</h3><p>The primary activities of the closing phase are delivering or transitioning the project outcomes to the customer and completing administrative steps to close the project. This may include a formal review and acceptance of the outcomes, transitioning to operations, returning equipment, releasing the team, closing contracts, and finalizing project financials.</p><p>© 2025, Alan Zucker; Project Management Essentials, LLC</p><p>See related articles:</p><ul><li><a href="https://pmessentials.us/back-to-basics-part-1-state-of-the-union/">Back to Basics, Part 1: State of the Union</a></li><li><a href="https://pmessentials.us/back-to-basics-part-2-principles/">Back to Basics, Part 2: Principles</a></li><li><a href="https://pmessentials.us/back-to-basics-part-3-the-approach/">Back to Basics, Part 3: The Approach</a></li><li><a href="https://pmessentials.us/gantt-101-building-a-better-project-schedule/">Gantt 101: Building a Better Project Schedule</a></li><li><a href="https://pmessentials.us/planning-is-a-process-not-an-outcome/">Planning is a Process, Not an Outcome</a></li><li><a href="https://pmessentials.us/project-frameworks-understand-the-choices/">Project Frameworks: Understand the Choices</a></li><li><a href="https://pmessentials.us/the-project-charter-lays-the-foundation/">The Project Charter Lays the Foundation</a></li><li><a href="https://pmessentials.us/unlock-the-power-of-the-project-management-plan/">Unlock the Power of the Project Management Plan</a></li></ul><p>To learn more about our training and consulting services or subscribe to our newsletter, visit our website: <a href="http://www.pmessentials.us/">http://www.pmessentials.us/</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a06f7d1e7af1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No Zombie Project Management]]></title>
            <link>https://alan-pmessentials.medium.com/no-zombie-project-management-54c8a027e12d?source=rss-aa503288162e------2</link>
            <guid isPermaLink="false">https://medium.com/p/54c8a027e12d</guid>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[zombies]]></category>
            <dc:creator><![CDATA[Alan Zucker]]></dc:creator>
            <pubDate>Mon, 09 Feb 2026 14:53:20 GMT</pubDate>
            <atom:updated>2026-02-09T14:53:20.074Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EHFoqHgvVEhTHgZbYbIhGw.png" /></figure><p>Zombies are the walking dead. They are unresponsive, lifeless, and apathetic. Zombie project managers simply go through the motions. They follow the rules and practices but are otherwise unengaged.</p><p>Zombie project management infects all project types. No one is immune — project managers, scrum masters, and development leads — can all become Zombies. We lead our projects without understanding “why” we are doing something or questioning if it is effective.</p><p>This article describes the symptoms of Zombie project management and offers the antidote to the problem. Project management must move from ritualized compliance to thoughtful, intentional practices.</p><h3>Finding the Zombies</h3><p>Finding the Zombies is easy. Examine yourself, your colleagues, and your organization. Do you suffer from any of the following symptoms?</p><p>· The organization treats standards as check-the-box activities rather than as opportunities for thoughtful review and meaningful discussion.</p><p>· Teams follow prescribed methodologies without tailoring them and then mindlessly executing, thus failing to achieve the intended value.</p><p>· Continuing to execute processes that are ineffective without questioning.</p><p>Zombies infected traditional projects after they fell victim to the misconception that adherence to a process guaranteed success. This stems from the belief that projects can be managed like a factory. The rise of Computer-Assisted Software Engineering (CASE) tools in the 1990s marked the peak of this movement. Unfortunately, projects are unique and depend on people, neither of which promotes predictability and stability.</p><p>Agile was infected when teams ignored the first value statement, “Individuals and interactions over processes and tools.” Implementing Agile practices without changing the way of working is the path to failure. Sprints that look like mini-falls, hour-long daily stand-ups, command-and-control management practices, or non-dedicated teams are common Agile anti-patterns.</p><p>It will only be a matter of time before Hybrid is infected as well. Teams will fail to establish sufficient structure and practices, and their work will be executed aimlessly. Succeeding in the middle ground between Predictive and Agile requires intentional planning. The processes and practices must be clearly defined; otherwise, chaos will ensue.</p><p>AI is already being overrun by Zombies. “AI workslop” describes low-quality AI-generated content. Examples include emails that do not make sense, charts with incorrect or fictitious data, or completely absurd ideas. The time savings from using AI are <a href="https://www.axios.com/2026/01/14/ai-jobs-productivity-workslop">offset by the rework required</a>. While AI can automate many tasks, there are many things it <a href="https://www.washingtonpost.com/technology/interactive/2026/ai-jobs-automation/">cannot</a> do — such as dealing with people.</p><h3>Killing the Zombies</h3><p>Stopping the Zombies will be difficult. It will require overcoming inertia and breaking ingrained habits. Methodologies and frameworks were designed to establish standard practices that make projects less chaotic and more predictable — a laudable goal. The unintended consequence is passivity. Instead of actively engaging, we became captive to the process.</p><p>To break the pattern, intentionality must be incorporated as a core skill and routine. The PMBOK® 8th Edition includes the principle of “Adopting a holistic approach,” which requires proactive engagement throughout the entire project lifecycle. Systems thinking and critical analysis should be constant companions. Recognizing even unseen dependencies and relationships helps us “look around corners.” Understanding the “why” behind the project and our practices enables us to grasp the intent and remain focused on the “right” things.</p><h3>Engaging the Thinking Brain</h3><p>Zombies infected a large federal contractor. Project managers complained about the prescribed standards, stage-gate, and periodic performance reviews. Teams spent countless hours creating slide decks and preparing. However, the meetings were formulaic, with predictable dialogue and outcomes. Little value or insight was gained.</p><p>Interviews with the organization’s leaders revealed a different story. Materials in the slide deck were recommended but not required. Project and program managers should feel empowered to challenge reviewers to provide meaningful insight and recommendations.</p><p>Complacency Zombies infected the teams and the reviewers. Disengagement was the problem, not the processes or standards. It was easier to go through the motions rather than dig deep and ask the difficult questions. The cure was simple. Less material but more actionable information. Shifting the conversation from what went wrong to what could be done better.</p><p>Engaging the thinking brain requires effort. It requires asking tough, open-ended, and probing questions, scrutinizing assumptions, and probing for cognitive biases. Expect this to be uncomfortable.</p><h3>Establishing the Approach</h3><p>Many projects are doomed before they even begin. The approach and lifecycle choices are often made mindlessly — default options that ignore the project’s specific needs. This can set the project on the wrong trajectory and lead to practices that are incongruent with the operating environment.</p><p>The CIO of a large financial services company declared that 75% of projects will be agile by the end of the year, which may have been a great aspirational goal, but was a Zombie management decision. To comply, rational managers became Zombies and implemented so-called agile practices across all projects. The result was disastrous. Many of the older applications were behemoths that were physically unable to move quickly.</p><p>Disciplined Agile embraces the values of context counts, choice is good, and pragmatism. Every organization, project team, and project is unique. Project managers face numerous decisions about how to lead, manage, and execute the project. These decisions should be informed by the context, project needs, and the available options.</p><p>Avoid falling into Maslow’s Hammer cognitive bias: “If the only tool you have is a hammer, it is tempting to treat everything as if it were a nail.” Make informed decisions. Tailor the project management plan and required development guidelines. Push back, avoid the path of least resistance.</p><h3>Managing the Project</h3><p>During the long project execution phase, the immune system is suppressed, making it vulnerable to infection. Even the best-run projects have problems and must deviate from the initial plan. There are delays, unforeseeable events, conflicts, and, of course, more work than expected. Risks, issues, and action items start falling through the cracks. Slipping into Zombie-autopilot mode is a natural response.</p><p>Resisting the Zombie instinct is essential. Fight back. Stay engaged. Engage the thinking brain. Adopt and adapt. Avoid knee-jerk solutions.</p><p>The construction of an office building was several months behind schedule. During a site visit, an executive declared the solution was to expedite the delivery of building materials. The project manager knew better but had no choice but comply. Fast-tracking deliveries overwhelmed the loading zone, delaying more critical shipments. Some of the pre-positioned materials were damaged due to insufficient storage space.</p><p>When the going gets tough, it’s time to pause, think, and be deliberate. Uncover the root cause(s) of the problems. Engage in critical thinking. Interrogate beliefs and assumptions. Make thoughtful adjustments. Then, review the changes to ensure they had the desired effect.</p><p>“Insanity is doing the same thing over and over again and expecting different results.”</p><p>While this phrase is often attributed to Einstein, it is not. Check your facts. Do not be a Zombie.</p><p>© 2026, Alan Zucker; Project Management Essentials, LLC</p><p>See related articles:</p><ul><li><a href="https://pmessentials.us/create-a-learning-environment-profit-from-your-mistakes/">Create a Learning Environment: Profit from Your Mistakes</a></li><li><a href="https://pmessentials.us/dont-blame-agile-for-bad-agile/">Don’t Blame Agile for Bad Agile</a></li><li><a href="https://pmessentials.us/intentional-project-management/">Intentional Project Management</a></li><li><a href="https://pmessentials.us/project-frameworks-understand-the-choices/">Project Frameworks: Understand the Choices</a></li><li><a href="https://pmessentials.us/reports-of-agiles-death-are-exaggerated/">Reports of Agile’s Death are Exaggerated</a></li></ul><p>To learn more about our training and consulting services or subscribe to our newsletter, visit our website: <a href="http://www.pmessentials.us/">http://www.pmessentials.us/</a>.</p><p>Image courtesy of: DustandCurruption.com</p><p>Watch the trailer: <a href="https://youtu.be/9hZ4mqzQR0A">https://youtu.be/9hZ4mqzQR0A</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54c8a027e12d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Back to Basics, Part 3: The Approach]]></title>
            <link>https://alan-pmessentials.medium.com/back-to-basics-part-3-the-approach-df112e655cb9?source=rss-aa503288162e------2</link>
            <guid isPermaLink="false">https://medium.com/p/df112e655cb9</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[hybrid-project-management]]></category>
            <dc:creator><![CDATA[Alan Zucker]]></dc:creator>
            <pubDate>Sun, 04 Jan 2026 21:15:05 GMT</pubDate>
            <atom:updated>2026-01-04T21:15:05.765Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ykQmxsQYYUIqIN6bz5ZMTg.png" /></figure><p>The project management profession is at a new crossroads. As reported by <a href="https://www.pmi.org/learning/thought-leadership/future-of-project-work">PMI</a>, both the use of Agile and Waterfall approaches are in decline. Hybrid is on the rise. But it lacks clear usage patterns. AI will support but not supplant project activities.</p><p>Rather than pinning hopes on the next big thing or a new silver-bullet solution, project managers should return to the basics — proven foundational practices. This requires thoughtful, intentional decisions and disciplined follow-through.</p><p>The first article in this series discussed the <a href="https://pmessentials.us/back-to-basics-part-1-state-of-the-union/">state of the industry</a>. The second recommended is to develop <a href="https://pmessentials.us/back-to-basics-part-2-principles/">guiding principles</a> to set the context and provide intent. This article describes how to select a project approach. Future articles will outline an execution framework and foundational practices.</p><p>Selecting the approach is a critical decision that is often unexamined. Teams frequently default to “what we always do,” the enterprise’s preferred or mandated option, or bow to the pressure of the loudest person in the room. The approach decision should be made carefully based on an assessment of the project’s context and specific needs.</p><h3>Approach Options</h3><p>There is an overwhelming variety of project management approaches available. By one count, there are at least 50 options. The choices are often summarized as a <a href="https://www.pmi.org/disciplined-agile/serial/hybridlifecycles">continuum</a> with Predictive and Agile as endpoints and Hybrid options in the middle.</p><p>Predictive is often loosely defined as the “waterfall” or sequential approach. One phase follows another. At a high level, that is true. But dig a little deeper. There are competing international standards, and most large enterprises have developed proprietary processes and practices.</p><p>Scrum is often used synonymously with Agile. But it is not. And that creates problems. Scrum is the most popular framework that describes a set of roles, artifacts, and ceremonies (meetings) that enable the Agile Manifesto Values and Principles. However, Scrum is not always the “best” agile approach.</p><p>Kanban is valuable, difficult to categorize, and can improve various delivery methods. It is a set of principles and practices that encourage flow and can be used in projects and operations. Sadly, it is often overlooked as a standalone approach. For example, agile teams working on a systems migration project do not need to be limited by a fixed sprint length because they are not releasing functionality every two weeks.</p><p>“All projects are hybrid,” claims Jesse Fewell, Global Chair of PMBOK 8th Edition. In my series on <a href="https://pmessentials.us/hybrid-project-management-part-1-what-is-hybrid/">hybrid project management</a>, I described a palette of approaches, with Waterfall, Agile, and Lean/Kanban forming the endpoints of a triangle, and the interior space representing a blend of practices (Hybrid). Within the palette, patterns emerge. Hybrid-predictive projects emphasize predictive elements, while hybrid-agile projects emphasize adaptive aspects. Lean and Kanban components can be integrated into any project type.</p><p>Like artists mixing colors to create beautiful paintings, project managers should combine practices to achieve greater success. Successful hybrid projects require intentional design; they will not occur by accident.</p><h3>Picking an Approach Pattern</h3><p>The approach decision sets the trajectory and embeds key assumptions about how the project will be managed and executed, including governance, delivery cadence, team and stakeholder engagement, and more. These decisions may be inconsistent with the project’s needs or constraints, setting up internal conflicts. Examples abound. There are fixed-scope “agile” projects and Scrum projects that do not deliver functionality until the end.</p><p>There is no single agreed-upon method for choosing the approach. <a href="https://pmessentials.us/hybrid-project-management-part-3-picking-the-approach/">Models, decision trees, and rubrics</a> are available. Deterministic tools can inform decisions and guide the process, but they can also be misleading and lead to poor choices. Tools are helpful, but do not replace sound judgment. Assessing the cost of change, understanding the clarity of the problem and solution space, and considering environmental factors provides a context-sensitive outcome.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/867/1*B0x2tcW_dTsq4IlRNGv1lg.png" /></figure><h3>Cost of Change</h3><p>Understanding the cost of change can help determine the best overall approach for the project and for each phase. The cost of change measures how easy it is to modify or change a project deliverable. This is influenced by physical constraints as well as timing.</p><p>The Predictive approach supports projects with high change costs. Construction projects provide a ready example. The design and specifications are finalized and approved before construction begins. Once the concrete is poured, moving a pipe or conduit is costly.</p><p>Knowledge work projects often favor an adaptive (Agile) approach. Quickly developing solution increments, getting feedback, and adjusting is cost-effective. Agile software projects are successful due to short development cycles and regular customer feedback. High school teachers review term paper drafts for similar reasons. It is easier to test, fix, and adjust 10 lines of code than 1,000 lines of code.</p><p>Timing is also an important factor. Blending approaches (Hybrid) based on project type and phase is a common practice. For some types of projects, the cost of change may initially be low, but at a certain point, it becomes prohibitive.</p><p>During the design phase of a construction project, the cost of change is low. Architects meet regularly with stakeholders to review and adjust design ideas. Making changes to blueprints is easy and cheap. Changes during construction are expensive.</p><h3>Problem and Solution Space</h3><p>When starting a project, gaining an orientation of the landscape can be invaluable. The Cynefin and Stacey Models can provide guidance into the problem and solution space by framing the environment. They provide insight without prescribing decisions.</p><p>The Cynefin Model is a sense-making framework for the problem space where situations can be simple, complicated, complex, or chaotic. The Stacey Model builds on this orientation, adds the solution space, and recommends a development approach:</p><ul><li>Simple problems have well-understood requirements and solutions. A Predictive or Kanban approach is recommended for these projects. We know what to do, just do it.</li><li>Complicated problems often have fewer clear requirements and solutions. A Predictive approach, where significant effort is invested in developing the solution, is commonly used for these types of projects. A Hybrid approach that employs iterative design and incremental delivery can also be effective.</li><li>Complex problems have unclear requirements and solutions that require Agile’s iterative and incremental approach.</li></ul><h3>Environmental Factors</h3><p>Environmental factors affect the project and are outside the team’s control. Examples include industry, regulatory environment, corporate culture, team experience, and risk appetite. Fully considering these environmental factors is essential for determining the approach.</p><p>Industries producing physical products, such as construction and defense, where the cost of change is high, tend to favor a more predictive approach. Software, finance, and other industries where the cost of change is lower can adopt agile practices.</p><p>Highly regulated industries, government work, and risk-averse cultures have constraints that require more structure, documentation, reviews, and approvals. Predictive approaches more natively support these needs, though hybrid-agile approaches can also be tailored to accommodate them.</p><p>An organization’s and a team’s preferences and experience can influence these decisions. Explicit policies and standards may specify the use of a particular approach. Team experience, or the lack thereof, can also favor one approach over another. Rigidity may persist even when a single approach or set of practices better fits a project’s needs.</p><p>© 2025, Alan Zucker; Project Management Essentials, LLC</p><p>See related articles:</p><ul><li><a href="https://pmessentials.us/back-to-basics-part-1-state-of-the-union/">Back to Basics, Part 1: State of the Union</a></li><li><a href="https://pmessentials.us/back-to-basics-part-2-principles/">Back to Basics, Part 2: Principles</a></li><li><a href="https://pmessentials.us/hybrid-project-management-part-3-picking-the-approach/">Hybrid Project Management: Part 3, Picking the Approach</a></li><li><a href="https://pmessentials.us/project-frameworks-understand-the-choices/">Project Frameworks: Understand the Choices</a></li></ul><p>To learn more about our training and consulting services or subscribe to our newsletter, visit our website: <a href="http://www.pmessentials.us/">http://www.pmessentials.us/</a>.</p><p>Image generated by ChatGPT</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df112e655cb9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>