<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Project Management on Trayix</title><link>https://trayix.com/tag/project-management/</link><description>Recent content in Project Management on Trayix</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 10 Jun 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://trayix.com/tag/project-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Complexity is the new normal</title><link>https://trayix.com/2026/06/complexity-new-normal/</link><pubDate>Wed, 10 Jun 2026 09:00:00 +0000</pubDate><guid>https://trayix.com/2026/06/complexity-new-normal/</guid><description>&lt;p&gt;Ask a project professional whether projects feel harder than they used to, and you&amp;rsquo;ll get a knowing look. PMI&amp;rsquo;s 2026 Pulse of the Profession report puts a number on it: 81% of project professionals say projects have become more complex in recent years. We doubt many readers are surprised. The more useful question is what to do about it.&lt;/p&gt;&#10;&lt;h2 id="complexity-isnt-just-more-work"&gt;Complexity isn&amp;rsquo;t just more work&lt;/h2&gt;&#10;&lt;p&gt;More tasks is a scheduling problem. Complexity is different: many parts that affect each other in ways nobody planned. A change to one system alters a process in another department, which changes how customers behave, which changes demand on the first system. Plans built as lists of tasks handle this badly, because the trouble sits between the tasks.&lt;/p&gt;</description></item><item><title>Building business acumen in project teams</title><link>https://trayix.com/2025/11/business-acumen/</link><pubDate>Wed, 05 Nov 2025 09:00:00 +0000</pubDate><guid>https://trayix.com/2025/11/business-acumen/</guid><description>&lt;p&gt;PMI&amp;rsquo;s 2025 Pulse of the Profession report found that only 18% of project professionals demonstrate high business acumen. If that number is even roughly right for your team, it explains a lot: projects that deliver what was specified but not what was needed, and steering committees where nobody can say why one initiative outranks another.&lt;/p&gt;&#10;&lt;h2 id="what-business-acumen-means-for-a-project-professional"&gt;What business acumen means for a project professional&lt;/h2&gt;&#10;&lt;p&gt;It isn&amp;rsquo;t an MBA. It&amp;rsquo;s knowing enough about the business to make good decisions without asking permission every time. In practice, that means understanding:&lt;/p&gt;</description></item><item><title>From project management success to project success</title><link>https://trayix.com/2025/07/project-success/</link><pubDate>Wed, 09 Jul 2025 09:00:00 +0000</pubDate><guid>https://trayix.com/2025/07/project-success/</guid><description>&lt;p&gt;A project can finish on time, on budget, and on scope, and still leave the business no better off. Most of us have seen it: the launch party happens, the status turns green, and six months later nobody uses the new system. The Project Management Institute (PMI) is now saying plainly that this isn&amp;rsquo;t good enough.&lt;/p&gt;&#10;&lt;h2 id="two-kinds-of-success"&gt;Two kinds of success&lt;/h2&gt;&#10;&lt;p&gt;PMI&amp;rsquo;s 2025 Pulse of the Profession report calls for shifting focus and accountability beyond project management success to project success. The difference is simple to state. Project management success means the team delivered on time, on budget, and on scope. Project success means the intended value and outcomes were realized.&lt;/p&gt;</description></item><item><title>Tailoring the approach to each project</title><link>https://trayix.com/2022/04/tailoring-each-project/</link><pubDate>Wed, 06 Apr 2022 09:00:00 +0000</pubDate><guid>https://trayix.com/2022/04/tailoring-each-project/</guid><description>&lt;p&gt;A one-size-fits-all method has a certain appeal. Everyone learns the same templates, the same gates, the same vocabulary. The cost shows up later, when a three-week internal change carries the same paperwork as a multi-year infrastructure program. The alternative is tailoring: choosing the approach for each project based on what that project needs. It takes judgment, but you can structure it.&lt;/p&gt;&#10;&lt;h2 id="assess-the-project-first"&gt;Assess the project first&lt;/h2&gt;&#10;&lt;p&gt;Before choosing a lifecycle, understand the work. We look at six factors:&lt;/p&gt;</description></item><item><title>PMBOK 7: from processes to principles</title><link>https://trayix.com/2021/10/pmbok-7-principles/</link><pubDate>Wed, 13 Oct 2021 09:00:00 +0000</pubDate><guid>https://trayix.com/2021/10/pmbok-7-principles/</guid><description>&lt;p&gt;For years, the Project Management Body of Knowledge (PMBOK) Guide taught a generation of practitioners to think in processes: five process groups, ten knowledge areas, and the inputs, tools, and outputs that connected them. This year, the Project Management Institute (PMI) published the 7th edition of A Guide to the Project Management Body of Knowledge, and it takes a different shape. It&amp;rsquo;s built on principles and performance domains, not on processes.&lt;/p&gt;</description></item><item><title>From project manager to product manager</title><link>https://trayix.com/2019/03/project-to-product-manager/</link><pubDate>Wed, 13 Mar 2019 09:00:00 +0000</pubDate><guid>https://trayix.com/2019/03/project-to-product-manager/</guid><description>&lt;p&gt;When an organization moves from funding projects to funding persistent product teams, project managers start asking what&amp;rsquo;s next for them. It&amp;rsquo;s a fair question. If projects stop being the unit of work, what happens to the people who managed them? The answer isn&amp;rsquo;t &amp;ldquo;they disappear,&amp;rdquo; but it isn&amp;rsquo;t &amp;ldquo;nothing changes&amp;rdquo; either.&lt;/p&gt;&#10;&lt;h2 id="several-paths"&gt;Several paths&lt;/h2&gt;&#10;&lt;p&gt;Project managers have more options than they often realize.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Product manager or product owner.&lt;/strong&gt; These roles decide what the team builds and why. They own priorities and answer for results.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Delivery lead.&lt;/strong&gt; Some teams still need someone to coordinate dependencies, remove obstacles, and keep work flowing. This role resembles a Scrum Master or release manager, with a broader view.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Portfolio and PMO roles.&lt;/strong&gt; Someone still has to see across teams, manage capacity, and report on value. Project managers with a strong grasp of planning and governance fit well.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Program or change leadership.&lt;/strong&gt; Large efforts that cross several products still need coordination.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;None is a demotion. They are different jobs, and the right one depends on what you enjoy. If you like deciding what to build, look at product work. If you like making teams effective, look at delivery. If you like seeing the whole picture, look at portfolio.&lt;/p&gt;</description></item><item><title>Top 5 reasons why projects fail</title><link>https://trayix.com/2014/10/why-projects-fail/</link><pubDate>Fri, 03 Oct 2014 22:09:44 +0000</pubDate><guid>https://trayix.com/2014/10/why-projects-fail/</guid><description>&lt;p&gt;Many project management office (PMO) consultants, program managers, and project managers will tell you, &amp;ldquo;Yes, many projects and programs have unrealistic and inflexible deadlines.&amp;rdquo; Many of them have been assigned to so many projects at once that, without time management, efficiency has become a thing of the past. Managing multiple projects, competing priorities, and tight deadlines is everyday work for many corporate employees. Have you ever had a chance to step back, think, and find a way to be proactive? Guess what? This isn&amp;rsquo;t going to change anytime soon. So we shouldn&amp;rsquo;t overlook the reasons why some projects fail. In this article, we&amp;rsquo;ll help you identify the causes and suggest solutions for your next project.&lt;/p&gt;</description></item><item><title>Waterfall isn't the enemy</title><link>https://trayix.com/2013/06/waterfall-isnt-the-enemy/</link><pubDate>Wed, 12 Jun 2013 09:00:00 +0000</pubDate><guid>https://trayix.com/2013/06/waterfall-isnt-the-enemy/</guid><description>&lt;p&gt;Every few weeks, someone in a steering meeting declares that waterfall is dead and agile is the answer. Then someone else asks how agile will work for the data center migration. Both people have a point, and neither has the whole picture. The useful question isn&amp;rsquo;t which approach wins. It&amp;rsquo;s which approach fits the work in front of you.&lt;/p&gt;&#10;&lt;h2 id="what-waterfall-does-well"&gt;What waterfall does well&lt;/h2&gt;&#10;&lt;p&gt;Waterfall (and its cousin, the stage-gate process) assumes you can know most of what you need up front, then build it in order. When that assumption holds, the approach works well. Consider a regional bank that must meet a regulatory change by a fixed date, with the requirements spelled out in the regulation itself. Little is uncertain about what to build. The risk is in coordination, documentation, and proof that you followed the rules. A plan with clear phases and sign-offs serves that work.&lt;/p&gt;</description></item></channel></rss>