<?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"><channel><title><![CDATA[AGILE CONVERSATIONS...]]></title><description><![CDATA[TPM, agilist, Cloud product owner, process analyst, Generative AI enthusiast]]></description><link>https://blog.myprojectimpact.com</link><generator>RSS for Node</generator><lastBuildDate>Sun, 08 Nov 2026 18:11:14 GMT</lastBuildDate><atom:link href="https://blog.myprojectimpact.com/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Clearly communicate technical project updates using the Executive Charter as a dictionary]]></title><description><![CDATA[For project success, we need to deliver on leadership's vision. And since the Executive Sponsor has the final say, the Dev Team’s work needs to embrace…]]></description><link>https://blog.myprojectimpact.com/clearly-communicate-technical-project-updates-using-the-executive-charter-as-a-dictionary</link><guid isPermaLink="true">https://blog.myprojectimpact.com/clearly-communicate-technical-project-updates-using-the-executive-charter-as-a-dictionary</guid><category><![CDATA[executive charter]]></category><category><![CDATA[project management]]></category><category><![CDATA[technical communication]]></category><dc:creator><![CDATA[Neville Scheevel]]></dc:creator><pubDate>Mon, 20 Jan 2025 22:38:46 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/stock/unsplash/Kl4LNdg6on4/upload/526e0b6357904108e05760f4b900885b.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>For project success, we need to deliver on leadership's vision. And since the Executive Sponsor has the final say, the Dev Team’s work needs to embrace that vision and demonstrate regular technical progress towards it.</p>
<p>To ensure everybody is aligned, the often overlooked crucial first step is creation of an Executive Charter. Developed collaboratively by the Dev Team and stakeholders, the Executive Charter document clarifies ambiguities, defines deliverables, and establishes measurable business goals.</p>
<p>Also, the Executive Charter provides a common language for the entire project. "Technical Value" narratives can be extracted from a well-crafted Executive Charter. The Dev Team can easily remember and share these narratives when describing how their technical tasks accomplish solution objectives. Framing project updates using the business terms grounded in the Executive Charter will clearly connect the technical work being discussed to the value it delivers.</p>
<div data-node-type="callout">
<div data-node-type="callout-emoji">🆕</div>
<div data-node-type="callout-text">Project updates that matter = reporting on technical tasks rooted in Business Value</div>
</div>

<p>"Transparency" is also key to successful technical updates. Converting technical uncertainties into measurable evaluations means "no surprises." Managing project risk using lean experimentation, converts technical uncertainties into quantitative evaluations. And by sharing the results frequently in feature demonstrations, this showcases solution evolution.</p>
<p>Ultimately the goal of updates is to drive proactive conversations with stakeholder. Transparency leads to alternative solutions when needed, posing questions like: "we learned that X isn't possible, but we can achieve a similar outcome with Y. Would that be acceptable?" So impediments discovered early on can be mitigated before issues escalate.</p>
<p>A well-defined Executive Charter, coupled with simple "Technical Value" narratives and transparent risk management, provides successful technical project updates.</p>
<p>By focusing on business outcomes and linking them to the underlying technical project aspects, teams ensure everyone understands how technical decisions drive project success.</p>
]]></content:encoded></item><item><title><![CDATA[Streamline Knowledge Transfer using AI]]></title><description><![CDATA[Learn how to use Generative AI and Otter.ai to automate knowledge transfer and preserve critical expertise.]]></description><link>https://blog.myprojectimpact.com/streamline-knowledge-transfer</link><guid isPermaLink="true">https://blog.myprojectimpact.com/streamline-knowledge-transfer</guid><category><![CDATA[KT]]></category><category><![CDATA[Process Improvement]]></category><category><![CDATA[Knowledge Transfer]]></category><category><![CDATA[Offboarding]]></category><category><![CDATA[Tribal Knowledge]]></category><category><![CDATA[generative ai]]></category><category><![CDATA[Kb]]></category><category><![CDATA[KnowledgeManagement]]></category><category><![CDATA[agile]]></category><category><![CDATA[lean]]></category><category><![CDATA[TPM]]></category><category><![CDATA[use-cases]]></category><dc:creator><![CDATA[Neville Scheevel]]></dc:creator><pubDate>Tue, 08 Oct 2024 22:26:50 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1728425002926/de48388f-a3b1-4537-abed-e3c5c68d7c11.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h3 id="heading-this-is-one-of-the-best-use-cases-for-generative-ai">This is one of the best use-cases for Generative AI</h3>
<p><em>A common scenario:</em> <strong>Your IT talent lands a new job</strong>. They hand in their notice. Nobody has time to write documentation. The clock is ticking. How will you capture their tribal knowledge before they walk out the door?</p>
<p>The best way to <strong>preserve ephemeral team knowledge</strong> is with a series of <strong>Knowledge Transfer sessions</strong> (KT) so that the Subject Matter Expert can share their expertise with a group.</p>
<p>For most IT Engineers, when repetitive tasks are second nature, the steps become automatic, and the details fade into obscurity. These details may be forgotten and never communicated when a seasoned employees exits the organization.</p>
<p>By <strong>recording KT sessions on Zoom</strong>, AI can be used for real-time transcription, capturing and organizing the discussions. The value of an automated transcription is that it <strong>frees participants from taking notes</strong>, allowing them to fully engage, or ask questions, or even multitask in the background without missing crucial information.</p>
<div data-node-type="callout">
<div data-node-type="callout-emoji">♨</div>
<div data-node-type="callout-text">This is the <strong>power of Generative AI</strong>, that it can reliably produce a structured and comprehensive training guide even from disjointed discussions.</div>
</div>

<p>But the real game-changer is using Otter AI as the transcriber. Recently I uncovered Otter's ability to <strong>add screen-grabs from Zoom presentations</strong>, so as presenters visit new screens, Otter AI can automatically capture screenshots and sync them to the discussion.</p>
<hr />
<h3 id="heading-here-is-a-recipe-for-scaling-your-kt-sessions-with-ai">Here is a recipe for scaling your KT sessions with AI:</h3>
<ol>
<li><p><strong>Review</strong> task history: Jira | ServiceNow | GitHub (PR's) ... wherever the team is tracking their work.</p>
</li>
<li><p>Identify the Subject Matter Expert's <strong>top 10 critical</strong> or frequent tasks, that only they handle.</p>
</li>
<li><p><strong>Block out one hour daily</strong> on the calendar for a team Zoom meeting.</p>
</li>
<li><p><strong>Invite Otter AI</strong> as a meeting participant on the Calendar invites.</p>
<p> (Otter AI will capture and transcribe each meeting in real-time)</p>
</li>
<li><p>Have a Project Manager or Analyst <strong>mediate the sessions</strong>, while the SME performs the demonstrations.</p>
</li>
<li><p>Make sure a couple team members attend to <strong>add context and questions</strong>.</p>
</li>
<li><p>For <strong>each process in review</strong>, have the SME begin with a general overview and then delve into specifics as participants raise questions.</p>
</li>
<li><p>The information doesn't need to be presented in precise order. The <strong>AI will organize</strong> and structure the content later, even when there are gaps or twists in the discussion.</p>
</li>
<li><p>Paste any links for <strong>supplemental info</strong> in the Zoom chat.</p>
</li>
<li><p>Define internal jargon as it arises. <strong>Focus on clarity</strong> so anyone can make sense of the material.</p>
</li>
<li><p>The AI output will be a comprehensive <strong>Standard Operating Procedure</strong>, outlined-formatted-illustrated.</p>
</li>
<li><p><strong>Publish it</strong> to your Knowledge Base and it's ready for your next new-hire replacement.</p>
</li>
</ol>
<p>Afterwards, you can have someone new to the procedure <strong>follow it step-by-step</strong>, to ensure the AI-generated guide is truly comprehensive. Follow up on anything that's missing or unclear <strong>before the Subject Matter Expert vanishes</strong>.</p>
<p>With a tight economy right now, most companies are looking to <strong>reduce headcount and find offshore</strong> <strong>options</strong>, and we need effective ways to capture and scale Knowledge Transfer. As a TPM, my role is to streamline project execution, and even though discussing staff departures can be uncomfortable, <strong>this is a critical process-improvement</strong> for the benefit of any technology enterprise.</p>
<p><em>What has been your experience automating knowledge capture?</em></p>
<p><em>Have you tried similar methods?</em></p>
]]></content:encoded></item><item><title><![CDATA[Liar-liar Gantt chart on fire]]></title><description><![CDATA[Why Capacity Heat Maps beat Gantt charts]]></description><link>https://blog.myprojectimpact.com/liar-liar-gantt-chart-on-fire</link><guid isPermaLink="true">https://blog.myprojectimpact.com/liar-liar-gantt-chart-on-fire</guid><category><![CDATA[agile]]></category><category><![CDATA[Productivity]]></category><category><![CDATA[project management]]></category><dc:creator><![CDATA[Neville Scheevel]]></dc:creator><pubDate>Tue, 04 Jun 2024 22:04:35 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1717459384801/78f46953-cc35-4d85-9016-6322cd987f9d.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Most project managers struggle with accurately estimating timelines for new teams with new types of projects.</p>
<p>The challenge with estimating anything new is its unfamiliarity. With no established benchmarks or historical metrics to rely on it is difficult to estimate the required effort. Additionally, projects that venture into uncharted territory make it difficult to anticipate the what challenges will be encountered along the way.</p>
<p>Gantt charts are a great tool for visualizing project timelines, but on unpredictable projects, where estimates are based on wishful thinking and guesswork, Gantt charts are misleading. And then when stakeholders misinterpret a fictional Gantt chart as a promise, getting them to agree on a change of scope may become impossible.</p>
<div data-node-type="callout">
<div data-node-type="callout-emoji">📉</div>
<div data-node-type="callout-text">Those once-vibrant swim-lane colors, now mocking your every project prediction.</div>
</div>

<p>When stakeholders view a Gantt chart as a rigid plan, the project manager loses the flexibility to adapt. When discrepancies between the charted timeline and reality become evident, stakeholders may question the project's management, causing an erosion in trust and creating unnecessary tension.</p>
<p>To overcome these perils I use "Capacity Heat Maps" to manage expectations. It's the effective way for project managers to visually communicate the reality of project timelines, when dealing with the unpredictable nature and unforeseen constraints of a unique project.</p>
<p>Capacity Heat Maps are more effective because they address the problem of inaccurate estimates by continuously recalculating capacity as the project progresses. This allows for dynamic adjustments to expectations, clearly indicating capacity dedicated to high-priority work streams along with reduced expectations for lower-priority ones when bandwidth is limited.</p>
<div data-node-type="callout">
<div data-node-type="callout-emoji">💡</div>
<div data-node-type="callout-text">Capacity Heat Maps provide a real-time picture of project risk and execution.</div>
</div>

<p>Beyond addressing inaccurate estimates, Capacity Heat Mapping maintains the visual clarity of a Gantt chart, making it easy for stakeholders to understand. By displaying capacity estimates as activity swim-lanes, it clearly shows which activities have allocated capacity and which activities will receive less effort due to constraints.</p>
<p>This allows you to present stakeholders with a real-time picture of project risk and execution, avoiding the trap of committing to an unrealistic timeline based on faulty estimates. Maintaining this credibility with stakeholders is crucial for project success.</p>
]]></content:encoded></item><item><title><![CDATA[Know more, do less]]></title><description><![CDATA[incrementalism]]></description><link>https://blog.myprojectimpact.com/know-more-do-less</link><guid isPermaLink="true">https://blog.myprojectimpact.com/know-more-do-less</guid><category><![CDATA[Productivity]]></category><category><![CDATA[lean]]></category><category><![CDATA[agile]]></category><dc:creator><![CDATA[Neville Scheevel]]></dc:creator><pubDate>Thu, 06 Jul 2023 11:47:20 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1688643420497/087ddbc8-df5b-428b-9c5f-42d0744375d4.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Project approvals &amp; business decisions rely on three basic questions:</p>
<ul>
<li><p>When will it be done?</p>
</li>
<li><p>How much will it cost?</p>
</li>
<li><p>Is it worth doing?</p>
</li>
</ul>
<p>When a project is unlike anything the team has done before, early estimates become overly optimistic. And, if a timeline is built on dependencies, we end up too far behind to make mid-course corrections.</p>
<div>
<div>📈</div>
<div>After all, adding people or resources to an already late project only makes it later.</div>
</div>

<p>The remedy is to measure the "risk" upfront through lean experimentation (and by "risk," I mean the unknowns that defy accurate estimation).</p>
<p>Identify those unknowns, slice them into thin experiments, dedicate resources, time-box the effort, and run them just long enough to make the work "knowable." Then we can scale estimates accordingly.</p>
]]></content:encoded></item><item><title><![CDATA[When facing the complexities of a project how do you go about making sense of it?]]></title><description><![CDATA[Compressing complexity into something manageable]]></description><link>https://blog.myprojectimpact.com/when-facing-the-complexities-of-a-project-how-do-you-go-about-making-sense-of-it</link><guid isPermaLink="true">https://blog.myprojectimpact.com/when-facing-the-complexities-of-a-project-how-do-you-go-about-making-sense-of-it</guid><category><![CDATA[agile]]></category><category><![CDATA[Productivity]]></category><category><![CDATA[project management]]></category><dc:creator><![CDATA[Neville Scheevel]]></dc:creator><pubDate>Fri, 24 Mar 2023 12:14:10 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1679609890526/fe4aea6c-716c-4223-92a4-da233a2f8eeb.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>My method is to start by zooming out and taking a low-resolution mental-snapshot, altering the resolution at which I'm perceiving the matter.</p>
<p>It's like squinting (so to speak) it blurs the resolution, so instead of dealing with overwhelming individual complexities, regions of complexity coalesce into a handful of bundles. And although blurry, the picture is simplified and becomes more mentally manageable.</p>
<p>Then with each over-simplified bundle of complexity, we can start to unpack and re-evaluate individually, becoming more granular, correcting biases and adopting a nuanced understanding of the underlying complexities.</p>
<p>Working in iterative cycles of; drilling into each bundle and zooming back out is like slicing through a cake, we get a view of all the layers and gain a deeper insight.</p>
<p>Along the way, reoccurring patterns emerge and when durable enough they can speed up our analysis of the remainder of the complexities. These emerging patterns appear ... classifications, metaphors, relationships, analogies or anecdotal examples ... and aid in succinctly communicating the gist of complexities to others and ourselves.</p>
<p>In the end, this technique culminates in a comfortable understanding of the complex whole. At least only the comprehension we need to define the goals of our project and propose the next logical steps forward.</p>
]]></content:encoded></item><item><title><![CDATA[Managing Unplanned Work For Teams]]></title><description><![CDATA[At the start of each development iteration, a lucky few are designated as the other-interesting-work squad. These guys are in reserve to work on…]]></description><link>https://blog.myprojectimpact.com/managing-unplanned-work-for-teams</link><guid isPermaLink="true">https://blog.myprojectimpact.com/managing-unplanned-work-for-teams</guid><category><![CDATA[agile]]></category><category><![CDATA[agile development]]></category><category><![CDATA[Productivity]]></category><category><![CDATA[project management]]></category><dc:creator><![CDATA[Neville Scheevel]]></dc:creator><pubDate>Wed, 10 Feb 2021 18:25:12 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1612984108895/oaZbeYU0n.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h3 id="heading-welcome-to-the-other-interesting-work-squad">Welcome to the "other interesting work" squad.</h3>
<p>At the start of each development iteration, a lucky few are designated as the other-interesting-work squad. These guys are in reserve to work on "unplanned" items that will enter the work-stream but while there's nothing unplanned to work on, they get to do all the fun stuff, like</p>
<ul>
<li><p>new platforms or frameworks the team has been wanting to investigate</p>
</li>
<li><p>competitive coding and proof-of-concept cage-matches</p>
</li>
<li><p>katas, continuing education or certification prep</p>
</li>
<li><p>codebase care-and-feeding, implementing that shiny new CI pipeline feature</p>
</li>
</ul>
<p>The OIW-squad trades out these tasks for unplanned work as new items enter the iteration. The unplanned intake can be the priority, but why not have a little fun along the way 😉</p>
]]></content:encoded></item></channel></rss>