<?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 Doron Katz on Medium]]></title>
        <description><![CDATA[Stories by Doron Katz on Medium]]></description>
        <link>https://medium.com/@doronkatz?source=rss-a8104afd5a1c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UK7zuN6-IKyxE_bEnnziwg.jpeg</url>
            <title>Stories by Doron Katz on Medium</title>
            <link>https://medium.com/@doronkatz?source=rss-a8104afd5a1c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:31:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@doronkatz/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[Surviving the Recession as a Technical Program Manager]]></title>
            <link>https://doronkatz.medium.com/surviving-the-recession-as-a-technical-program-manager-2fe844bd5f41?source=rss-a8104afd5a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fe844bd5f41</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[program-manager]]></category>
            <category><![CDATA[project-manager]]></category>
            <category><![CDATA[program-management]]></category>
            <dc:creator><![CDATA[Doron Katz]]></dc:creator>
            <pubDate>Wed, 01 Nov 2023 00:27:59 GMT</pubDate>
            <atom:updated>2023-11-01T00:27:59.667Z</atom:updated>
            <content:encoded><![CDATA[<h3>3 Ways to Survive the Recession as a Technical Program Manager</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yNJLoFNnLgXgN_W3.png" /></figure><p>I’ve decided to leave my current role and embark on a personal development career break. With the economy in the midst of a recession and inverting of opportunity supply and demand, I am thinking strategic which means taking a pause from the LinkedIn job rat-race to focus on better developing myself as a Technical Program Manager.</p><p>I thought I would share with you my thought process as I embark on this exciting journey, but this article can apply to those that have also been forced to look for a new TPM role. But it doesn’t mean you have to solely focus on applying for jobs. I have come up with a list of <em>3 ways to survive the recession as a Technical Program Manager</em>:</p><h4>1. Get Certified</h4><p>I have collected a few certifications over my 20-plus career, such as <a href="https://www.scrum.org/assessments/professional-scrum-master-i-certification">PSM-I</a> and <a href="https://www.scrumalliance.org/get-certified/product-owner-track/certified-scrum-product-owner">CSPO</a>, but I have my eye on the <a href="https://www.pmi.org/certifications/project-management-pmp">Project Management Professional (PMP)</a> certification, which takes at least a month to prepare for. I can certainly also look at upgrading my other certifications, such as obtaining a <a href="https://www.6sigma.us/six-sigma-yellow-belt.php">Sigma Six Yellow belt</a> and PSM-II certification.</p><h4>2. Get Technical</h4><p>Don’t neglect the T in Technical Program Manager! Since you did your computer science degree, there have been numerous technologies that have come (and gone). I would look into some LinkedIn Learning or Udemy courses to brush up on your systems design, and various select technologies.</p><p>For me, I am looking at the emerging ChatGPT and Generative AI, various web technologies such as Kubernetes and Kafka, and Swift (my passion language). Take a look at the jobs out there on the market and use that as a guide for where you want to be.</p><p>Wouldn’t hurt to also add some code to your GitHub profile if it’s been while. The proof is in the pushing (pudding).</p><h4>3. Take a Step Back if Necessary</h4><p>In military terms, a strategic retreat allows you to gain better perspective and re-allocate focus more appropriately. In times like these, with scarce opportunities out there, it’s okay to pick up a contract job or even a less paying job. It could be an opportunity for you to learn a new tech stack, perhaps pivot from TPM to PMT (technical product manager) or something else altogether. There’s no shame in that, and you can use the time to plan for the bigger picture.</p><p>Ad a TPM, you continuously execute projects with set goals, maintain risk registers and balance tech debt. It’s high time you focus on yourself as well, and not only the job applications out there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fe844bd5f41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Habits of High-Performing Technical Program Managers]]></title>
            <link>https://medium.com/the-tpm-toolkit/5-habits-of-high-performing-technical-program-managers-fe3a998912fe?source=rss-a8104afd5a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe3a998912fe</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[technical-program-manager]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Doron Katz]]></dc:creator>
            <pubDate>Wed, 19 Jul 2023 01:22:26 GMT</pubDate>
            <atom:updated>2023-07-19T01:29:14.468Z</atom:updated>
            <content:encoded><![CDATA[<h2>5 Habits of a High-Performing Technical Program Manager</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*5_kKqYp5JqnZYHXIR8fRKw@2x.jpeg" /></figure><p>Technical program management is a critical role that demands a combination of technical expertise, leadership skills, and effective program execution. In this article, we will explore five key habits commonly observed in high-performing technical program managers. These habits contribute to their success in delivering complex projects, fostering collaboration, and achieving desired outcomes.</p><ol><li><strong>Clear Goal-Setting</strong>: High-performing technical program managers understand the importance of setting clear goals and objectives. They excel at defining measurable targets that align with organizational strategies and priorities. By establishing well-defined goals, they provide a sense of direction for their teams, ensuring everyone understands the desired outcomes and can work collectively towards achieving them. Clear goal-setting enhances focus, facilitates decision-making, and enables effective resource allocation.</li><li><strong>Effective Communication</strong>: Effective communication is a cornerstone of success for technical program managers. They possess exceptional communication skills, enabling them to articulate complex technical concepts in a clear and concise manner. They tailor their communication style to suit different audiences, whether it’s engaging with stakeholders, collaborating with engineers, or presenting to executives. Their ability to convey ideas effectively fosters understanding, alignment, and engagement among team members, stakeholders, and other relevant parties.</li><li><strong>Strong Leadership</strong>: High-performing technical program managers exhibit strong leadership qualities. They inspire and motivate their teams by setting a positive example. They create an inclusive and collaborative work environment that encourages open communication, creativity, and innovation. These leaders empower their team members by providing autonomy, recognizing achievements, and supporting professional growth. Moreover, they are adept at navigating challenges, making tough decisions when necessary, and resolving conflicts in a constructive manner.</li><li><strong>Proactive Problem-Solving</strong>: Proactive problem-solving is another habit that sets high-performing technical program managers apart. They anticipate potential issues and roadblocks by leveraging their technical expertise and experience. They take a proactive approach to identify and address challenges before they escalate, minimizing the impact on the program’s progress. These managers are skilled at devising contingency plans, conducting risk assessments, and ensuring smooth program execution. Their ability to think ahead and mitigate risks contributes to successful program outcomes.</li><li><strong>Continuous Learning</strong>: High-performing technical program managers embrace a mindset of continuous learning. They recognize the importance of staying updated with industry trends, emerging technologies, and best practices. They actively seek opportunities for professional development, attend relevant conferences and workshops, and engage in knowledge-sharing with peers. These managers value feedback and reflection, leveraging lessons learned from past experiences to improve their performance. Continuous learning enables them to adapt to evolving circumstances, enhance their technical knowledge, and refine their program management skills.</li></ol><p>High-performing technical program managers possess a distinct set of habits that contribute to their success in delivering complex projects and driving positive outcomes. Their clear goal-setting, effective communication, strong leadership, proactive problem-solving, and commitment to continuous learning enable them to excel in their roles.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe3a998912fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-tpm-toolkit/5-habits-of-high-performing-technical-program-managers-fe3a998912fe">5 Habits of High-Performing Technical Program Managers</a> was originally published in <a href="https://medium.com/the-tpm-toolkit">The TPM Toolkit</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Four situations not to use the Agile Manifesto]]></title>
            <link>https://medium.com/the-tpm-toolkit/four-situations-not-to-use-the-agile-manifesto-fd912c87bec9?source=rss-a8104afd5a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd912c87bec9</guid>
            <category><![CDATA[technical-project-manager]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-manifesto]]></category>
            <category><![CDATA[technical-program-manager]]></category>
            <dc:creator><![CDATA[Doron Katz]]></dc:creator>
            <pubDate>Tue, 18 Jul 2023 18:28:28 GMT</pubDate>
            <atom:updated>2023-07-18T18:28:28.005Z</atom:updated>
            <content:encoded><![CDATA[<p>The Agile Manifesto has revolutionized the software development industry, promoting adaptive planning, collaboration, and iterative development. Agile methodologies like Scrum and Kanban have gained immense popularity due to their ability to deliver high-quality products while accommodating changing requirements. However, despite its widespread success, there are situations where the Agile Manifesto may not be the most suitable approach. Here are four scenarios where an alternate to agile should be chosen for a project methodology:</p><ol><li><strong>Stable and Predictable Projects</strong>: Agile methodologies excel in projects with dynamic requirements, where flexibility and adaptability are crucial. However, if you are working on a project with stable and well-defined requirements, where changes are unlikely or negligible, a traditional Waterfall approach might be more appropriate. Waterfall allows for detailed planning, sequential execution, and a linear development process, making it suitable for projects where predictability and precise documentation are paramount.</li><li><strong>Large-Scale and Long-Term Projects</strong>: Agile methodologies typically emphasize small, cross-functional teams working on short iterations. While this approach promotes agility, it may not be suitable for large-scale projects with a longer duration. In such cases, a hybrid methodology like the Scaled Agile Framework (SAFe) or a more traditional project management methodology like PRINCE2 may be better suited. These methodologies provide a structured framework for managing complex projects involving multiple teams, dependencies, and organizational coordination.</li><li><strong>Highly Regulated Industries</strong>: In industries with stringent regulations and compliance requirements, such as healthcare, finance, or aerospace, the Agile Manifesto may face challenges. These industries often demand rigorous documentation, traceability, and thorough validation processes, which can be at odds with the Agile principles of minimal documentation and focus on working software. In such cases, a regulatory-compliant methodology, such as the V-Model or the Rational Unified Process (RUP), might be necessary to ensure adherence to industry standards and legal obligations.</li><li><strong>Fixed-Price Contracts</strong>: Agile methodologies are built on the foundation of flexibility and adapting to change. However, in situations where projects are governed by fixed-price contracts, it becomes challenging to accommodate evolving requirements without impacting cost and scope. Traditional contract-driven approaches, such as the Fixed-Price or Time and Materials (T&amp;M) models, provide greater certainty in terms of budget, scope, and delivery timelines. These models require thorough upfront planning and documentation, making them better suited for fixed-price contracts.</li></ol><p>The Agile Manifesto has significantly transformed the software development landscape, enabling teams to deliver value quickly and respond to changing requirements effectively. However, it is crucial to recognize that Agile is not a one-size-fits-all solution. In certain situations, such as stable projects, large-scale initiatives, regulated industries, fixed-price contracts, or inexperienced teams, alternative methodologies may prove more suitable. It is essential to assess the project’s characteristics, team capabilities, and environmental factors before deciding on the most appropriate development methodology to ensure project success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd912c87bec9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-tpm-toolkit/four-situations-not-to-use-the-agile-manifesto-fd912c87bec9">Four situations not to use the Agile Manifesto</a> was originally published in <a href="https://medium.com/the-tpm-toolkit">The TPM Toolkit</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sympathetic vs Empathetic Technical Program Managers]]></title>
            <link>https://medium.com/the-tpm-toolkit/sympathetic-vs-empathetic-technical-program-managers-b7fc4259f413?source=rss-a8104afd5a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7fc4259f413</guid>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[program-management]]></category>
            <category><![CDATA[technical-program-manager]]></category>
            <dc:creator><![CDATA[Doron Katz]]></dc:creator>
            <pubDate>Tue, 18 Jul 2023 18:18:45 GMT</pubDate>
            <atom:updated>2023-07-18T18:18:45.610Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Z0YpNKFE0X9V56uXT2F4bA@2x.jpeg" /></figure><p>As a technical program manager, possessing strong interpersonal skills is foundational, considering you manage without formal authority. Building relationships, earning trust is paramount.</p><p>Two terms that often arise in this context are “<em>sympathy</em>” and “<em>empathy</em>.” While they may appear similar, they have distinct meanings and implications. In this article, we will explore the difference between a sympathetic and an empathetic technical program manager, shedding light on their unique qualities and contributions to successful project management.</p><h4>Sympathetic Technical Program Managers</h4><p>Sympathy is the ability to understand and express feelings of compassion towards another person’s experiences, struggles, or emotions. A sympathetic technical program manager recognizes and acknowledges the challenges faced by team members or stakeholders. They exhibit a genuine concern for their well-being and are able to offer support and assistance when needed. Sympathy often manifests through acts of kindness, compassion, and listening. A sympathetic technical program manager demonstrates:</p><ol><li><strong>Supportive communication</strong>: They actively listen to team members, providing a safe space for expressing concerns, frustrations, or difficulties.</li><li><strong>Compassionate problem-solving</strong>: They prioritize addressing challenges faced by team members and seek viable solutions that alleviate their pain points.</li><li><strong>Emotional intelligence</strong>: They possess a keen awareness of their own emotions and those of others, allowing them to navigate conflicts or sensitive situations with sensitivity.</li><li><strong>Team cohesion</strong>: They foster an environment of trust and collaboration, promoting a sense of unity and camaraderie among team members.</li></ol><h4>Empathetic Technical Program Managers</h4><p>Empathy, on the other hand, goes beyond understanding and compassion. Empathy is the ability to step into someone else’s shoes and truly share their emotional experiences. An empathetic technical program manager not only acknowledges the challenges faced by team members but actively seeks to understand their perspectives, motivations, and needs. They strive to create an environment where individuals feel heard, valued, and understood. An empathetic technical program manager demonstrates:</p><ol><li><strong>Deep understanding</strong>: They make a conscious effort to comprehend the emotions, experiences, and perspectives of team members, enabling them to make informed decisions and provide appropriate support.</li><li><strong>Adaptability and flexibility</strong>: They adjust their management style to accommodate the diverse needs and working styles of team members, fostering an inclusive and collaborative work environment.</li><li><strong>Emotional support</strong>: They offer emotional support to team members during stressful periods, showing empathy and understanding when personal or professional challenges arise.</li><li><strong>Empowerment and growth</strong>: They encourage the professional development of team members by identifying their strengths, providing constructive feedback, and creating opportunities for growth.</li></ol><p>Both sympathetic and empathetic technical program managers possess valuable qualities that contribute to effective project management and team dynamics. While a sympathetic manager shows genuine concern and support, an empathetic manager takes it a step further by immersing themselves in the experiences and emotions of their team members. By leveraging their emotional intelligence, both types of managers can foster trust, collaboration, and productivity within their teams, ultimately leading to successful project outcomes.</p><p>Ultimately, the choice between being sympathetic or empathetic as a technical program manager depends on the context and the unique needs of the team members. Striking a balance between sympathy and empathy allows managers to create a supportive and understanding environment while effectively driving project success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7fc4259f413" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-tpm-toolkit/sympathetic-vs-empathetic-technical-program-managers-b7fc4259f413">Sympathetic vs Empathetic Technical Program Managers</a> was originally published in <a href="https://medium.com/the-tpm-toolkit">The TPM Toolkit</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leverage ChatGPT as a Technical Program Manager to Write Effective Status Reports]]></title>
            <link>https://medium.com/the-tpm-toolkit/leverage-chatgpt-as-a-technical-program-manager-to-write-effective-status-reports-2d7a02db8bc3?source=rss-a8104afd5a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d7a02db8bc3</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technical-program-manager]]></category>
            <category><![CDATA[chatgpt]]></category>
            <dc:creator><![CDATA[Doron Katz]]></dc:creator>
            <pubDate>Fri, 07 Jul 2023 05:18:35 GMT</pubDate>
            <atom:updated>2023-07-07T05:19:42.310Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-HoIW3N-kr7YEhP9gLJK7Q.png" /></figure><p>With the story of the year being ChatGPT, squarely focused on everyone from engineers to data scientists, writers, academics, I thought I’d write a blurb on how as a Technical Program Manager, I leverage ChatGPT in my day-to-day. I assume of course unless you have been living under a rock, you have heard of ChatGPT and probably have downloaded the app or access its online tool. If not, head over to <a href="https://chat.openai.com/">https://chat.openai.com/</a> and create an account and play around with it.</p><p>One of the primary yet mandate tasks as a TPM is writing status reports regularly. Well thankfully, your wing-person ChatGPT can help here. In fact, I even asked ChatGPT how it could help me write better status reports, asking the following:</p><blockquote>How can I use chatGPT to write a status report, as a project manager</blockquote><p>This is what it wrote back:</p><h3>Instructions</h3><ol><li>Provide an introduction: Start by providing a brief introduction about the project, including its name, purpose, and key objectives. For example: “Project XYZ aims to develop a new mobile application that enhances customer engagement and streamlines internal processes.”</li><li>Outline project milestones: Specify the major milestones or deliverables achieved during the reporting period. Include any significant accomplishments, challenges, or delays. You can ask ChatGPT for suggestions based on your project’s progress, such as: “Can you help me list the key milestones achieved during the past week?”</li><li>Report progress: Describe the overall progress made towards each milestone. Highlight the tasks completed, percentage of completion, and any outstanding work. You can ask ChatGPT for assistance in summarizing the progress, such as: “Can you help me summarize the progress made on each milestone?”</li><li>Address issues and risks: Identify any issues, challenges, or risks that have arisen during the reporting period. Explain their impact on the project and any mitigation strategies implemented or planned. Seek advice from ChatGPT on how to address these issues effectively.</li><li>Discuss resource utilization: Provide an overview of resource utilization, including the allocation of team members, budget, and any changes made to the resource plan. Mention if there were any resource constraints or if additional resources were required.</li><li>Share upcoming tasks: Outline the tasks or milestones planned for the next reporting period. Discuss their importance, dependencies, and estimated timelines. Ask ChatGPT for suggestions on prioritizing and sequencing tasks.</li><li>Communicate next steps: Describe the actions that will be taken to address the reported issues, risks, or changes. Provide a clear plan for moving forward and achieving project objectives. You can ask ChatGPT for guidance on formulating actionable next steps.</li><li>Conclude with a summary: Summarize the key points discussed in the status report. Emphasize the overall project status, milestones achieved, and upcoming priorities. Seek assistance from ChatGPT in creating a concise and impactful summary.</li></ol><h3>Fictitious Project</h3><p>Next, I take the content above and ask ChatGPT:</p><blockquote>Write a fictitious mobile app project introduction including its name, purpose, and key objectives</blockquote><p>It then generates the following:</p><h4><strong>Project Introduction</strong></h4><p>The SwiftConnect project aims to develop a cutting-edge mobile application that revolutionizes communication and connectivity for global travelers. By leveraging advanced technology and intuitive design, SwiftConnect will enhance the travel experience by providing a seamless platform for travelers to stay connected, access essential information, and connect with fellow explorers around the world.</p><h4><strong>Project Purpose</strong></h4><p>The purpose of SwiftConnect is to bridge the gap between travelers and their destinations, offering a comprehensive solution to address the challenges faced during international travel. The app will provide a centralized hub of information and services that empower users to navigate unfamiliar territories, engage with local communities, and make the most out of their travel experiences.</p><h4><strong>Project Key Objectives</strong></h4><ol><li>Seamless Connectivity: SwiftConnect aims to ensure uninterrupted connectivity for travelers by integrating with local networks, offering reliable internet access, and enabling voice and video calls across borders. The app will prioritize a seamless and hassle-free connection experience, eliminating the need for multiple SIM cards or complicated roaming processes.</li><li>Traveler Support: SwiftConnect will serve as a comprehensive travel companion, offering real-time information and assistance tailored to each user’s location and preferences. From personalized recommendations on attractions, dining, and events, to language translation and emergency support, the app will provide a range of services to help travelers navigate new environments with confidence.</li><li>Social Networking: The app will facilitate connections between like-minded travelers, enabling them to share experiences, create travel communities, and foster meaningful connections. SwiftConnect’s social networking features will encourage cultural exchange, collaboration on itineraries, and the formation of friendships that transcend borders.</li><li>Safety and Security: The safety and security of users will be a top priority for SwiftConnect. The app will provide essential safety information, such as local emergency contacts, medical facilities, and safety alerts. It will also integrate with emergency services and offer features like check-in notifications for loved ones, ensuring peace of mind during travel.</li><li>User-Friendly Interface: SwiftConnect will prioritize a user-friendly interface, ensuring a seamless and intuitive experience for travelers of all technological backgrounds. The app will be designed with simplicity and efficiency in mind, empowering users to access the app’s features effortlessly and make the most of their travel adventures.</li></ol><h4>Project Milestones</h4><p><strong>Milestone 1</strong>: App Conceptualization and Design</p><ul><li>Define app features and functionalities</li><li>Create wireframes and mockups</li><li>Finalize app design</li></ul><p><strong>Milestone 2:</strong> Development and Backend Integration</p><ul><li>Develop the front-end of the mobile app</li><li>Implement backend systems and databases</li><li>Integrate APIs for connectivity and location services</li></ul><p><strong>Milestone 3</strong>: Testing and Quality Assurance</p><ul><li>Conduct thorough testing of app functionality and performance</li><li>Identify and fix any bugs or glitches</li><li>Ensure seamless user experience across different devices and platforms</li></ul><p><strong>Milestone 4</strong>: Deployment and Launch</p><ul><li>Prepare the app for release on major app stores</li><li>Create marketing materials and promotional strategies</li><li>Launch the app to the target market</li></ul><h4><strong>Report Progress</strong></h4><p>During the reporting period, we have made significant progress in achieving the project milestones:</p><p><strong>Milestone 1</strong>: App Conceptualization and Design</p><ul><li>Completed the definition of app features and functionalities.</li><li>Finalized the wireframes and mockups.</li><li>Reviewed and approved the app design, incorporating user-friendly elements.</li></ul><p><strong>Milestone 2</strong>: Development and Backend Integration</p><ul><li>Developed the front-end of the mobile app, achieving 80% completion.</li><li>Successfully integrated backend systems and databases.</li><li>Completed the integration of essential APIs for connectivity and location services.</li></ul><h4><strong>Issues and Risks</strong></h4><p>While progressing towards our milestones, we encountered a few challenges and risks:</p><ol><li><strong>Limited Resources</strong>: The development team faced resource constraints due to unforeseen personnel changes, leading to a slight delay in development timelines. However, we have adjusted the resource allocation and hired additional developers to mitigate this issue.</li><li><strong>Connectivity Challenges</strong>: Integrating with local networks in certain regions posed technical challenges, as regulations and network infrastructure varied. We are actively collaborating with network providers and exploring alternative solutions to ensure consistent connectivity across locations.</li><li><strong>Resource Utilization</strong>: Our resource utilization during the reporting period was as follows:</li><li><strong>Team Allocation</strong>: The development team dedicated an average of 120 hours per week to the project, focusing on front-end development, backend integration, and quality assurance.</li><li><strong>Budget Allocation:</strong> 80% of the allocated budget was utilized, primarily for development costs, API integrations, and testing activities.</li></ol><h4>Share Upcoming Tasks</h4><p>For the next reporting period, we have planned the following tasks:</p><p><strong>Milestone 2:</strong> Development and Backend Integration</p><ul><li>Complete front-end development and user interface enhancements.</li><li>Conduct comprehensive testing and debugging to ensure a robust application.</li></ul><p><strong>Milestone 3</strong>: Testing and Quality Assurance</p><ul><li>Perform thorough functional testing across various devices and platforms.</li><li>Implement user feedback and fine-tune the app for optimal performance.</li></ul><p><strong>Milestone 4</strong>: Deployment and Launch</p><ul><li>Finalize marketing materials and strategies for app promotion.</li><li>Prepare for the app’s release on major app stores, including the submission process and compliance checks.</li></ul><h3>OK ChatGPT… Write my Status Report</h3><p>Alright, an impressive fictitious project. I wanted to take a specific risk sentence, and convert it into an Amazon-style status narrative:</p><blockquote>Re-write the following paragraph as a one sentence concise narrative in the format “As of 05/05/23 we are yellow on the issue but have a Path-to-Green to remedy” for the following:</blockquote><blockquote>The development team faced resource constraints on the SwiftConnection project due to unforeseen personnel changes, leading to a slight delay in development timelines. However, we have adjusted the resource allocation and hired additional developers to mitigate this issue.</blockquote><p>We get back the following:</p><blockquote>As of 05/05/23, we are yellow on the SwiftConnection due to unforeseen personnel changes, but we have a Path-to-Green by adjusting resource allocation and hiring additional developers to mitigate the slight delay in development timelines.</blockquote><p>As you can see, its quite nifty. You can use it to re-write specific sections, paragraphs and so on. In the above example I used it to re-write the status as an Amazon-style narrative. Remember, when you reply back it remembers the conversation thread and context so you don’t have to repeat yourself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d7a02db8bc3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-tpm-toolkit/leverage-chatgpt-as-a-technical-program-manager-to-write-effective-status-reports-2d7a02db8bc3">Leverage ChatGPT as a Technical Program Manager to Write Effective Status Reports</a> was originally published in <a href="https://medium.com/the-tpm-toolkit">The TPM Toolkit</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to influence resistant teams to Embrace Agile in 8 Steps]]></title>
            <link>https://doronkatz.medium.com/how-to-influence-resistant-teams-to-embrace-agile-in-8-steps-818b1a5b9e8d?source=rss-a8104afd5a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/818b1a5b9e8d</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Doron Katz]]></dc:creator>
            <pubDate>Wed, 28 Jun 2023 17:36:08 GMT</pubDate>
            <atom:updated>2023-06-28T17:36:08.331Z</atom:updated>
            <content:encoded><![CDATA[<h3>Influencing teams to Embrace Agile in 9 Steps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MiWI5furL2P2utZAFvyk6A@2x.jpeg" /></figure><p>Introducing and influencing teams to adopt agile practices can be a significant challenge. Resistance to change, fear of the unknown, and ingrained habits are common barriers. But with the right strategies and a compelling case, you can successfully influence your teams to embrace agile.</p><h4>Understand the Value of Agile:</h4><p>Before attempting to influence others, it’s crucial to thoroughly understand the value and benefits of agile methodology. Educate yourself on its principles, such as iterative development, customer collaboration, and continuous improvement. Gain a deep understanding of how agile can address common pain points, increase productivity, and deliver better results. This knowledge will form the foundation of your influence. Lead by Example:</p><p>As a leader or influencer, it’s vital to embody the principles and practices of agile in your own work. Demonstrate the positive impact of agile by applying it to your projects and showcasing the benefits. When your team sees firsthand how agile improves efficiency, increases transparency, and enhances outcomes, they’ll be more likely to embrace it themselves. Be a role model for agile practices and encourage others to observe and learn from your experiences. Communicate the Why:</p><p>To influence teams effectively, it’s crucial to articulate the “why” behind the transition to agile. Clearly communicate the rationale for adopting agile methodology, highlighting how it aligns with organizational goals and addresses pain points. Emphasize the need for flexibility, adaptability, and faster delivery in today’s dynamic business environment. Discuss the competitive advantages of agile, such as increased customer satisfaction and quicker time-to-market. By presenting a compelling case for change, you can generate enthusiasm and buy-in.</p><h4>Tailor the Approach</h4><p>Every team is unique, with its own set of challenges and dynamics. It’s essential to tailor your approach to fit the specific context and needs of each team you’re trying to influence. Understand the team’s current working methods, their strengths, and pain points. Identify how agile practices can address their specific challenges and create a more collaborative and efficient work environment. Customizing your message and approach increases the chances of successful adoption.</p><h4>Provide Training and Support</h4><p>Transitioning to agile requires a shift in mindset and acquiring new skills. Offer comprehensive training sessions and workshops to help team members understand agile principles and practices. Provide resources, such as online courses, books, and articles, to support their learning journey. Offer mentorship and coaching to guide them through the initial stages of implementation. By investing in their growth and providing the necessary support, you empower team members to embrace agile with confidence.</p><h4>Start Small and Iterate</h4><p>Introducing agile can be overwhelming for teams accustomed to traditional methodologies. Instead of a big-bang approach, start small and gradually introduce agile practices. Begin with a pilot project or a specific team within the organization. Allow the team to experience the benefits of agile firsthand and learn from their successes and challenges. Collect feedback and make iterative improvements along the way. This incremental approach helps build confidence and encourages broader adoption.</p><h4>Foster Collaboration and Ownership</h4><p>Agile thrives on collaboration, transparency, and shared ownership. Create an environment that fosters collaboration, where team members feel empowered to contribute their ideas and expertise. Encourage cross-functional communication, daily stand-ups, and regular retrospectives to promote continuous improvement. Foster a culture of accountability and trust, where team members take ownership of their work and strive for collective success.</p><h4>Celebrate Successes and Share Stories</h4><p>When teams experience positive outcomes and tangible benefits from agile, celebrate their successes. Share success stories and testimonials within the organization to create a ripple effect. Recognize and reward individuals and teams for their efforts and achievements.</p><p>By showcasing the positive impact of agile, you inspire others to follow suit. Influencing teams to embrace agile requires patience, perseverance, and effective communication. By understanding the value of agile, leading by example, customizing your approach, providing support, and fostering collaboration, you can navigate the transition successfully and unlock the power of agile within your organization.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=818b1a5b9e8d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Difference Between a Technical Program Manager, Engineering]]></title>
            <link>https://medium.com/the-tpm-toolkit/the-difference-between-a-technical-program-manager-engineering-9eb72ddd5cfa?source=rss-a8104afd5a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9eb72ddd5cfa</guid>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technical-program-manager]]></category>
            <dc:creator><![CDATA[Doron Katz]]></dc:creator>
            <pubDate>Tue, 27 Jun 2023 22:03:33 GMT</pubDate>
            <atom:updated>2023-06-27T22:03:33.876Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Difference Between a Technical Program Manager, Engineering Manager, and Product Manager</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*yledxzc6gqQ0I1n-f50H-w.png" /><figcaption>From Technical Program Manager’s Handbook by Joshua Alan Teter</figcaption></figure><p>In the tech industry, several key roles play a critical part in driving projects, managing teams, and delivering successful products. Three roles that are often discussed and sometimes misunderstood are the Technical Program Manager (TPM), Engineering Manager, and Product Manager. While these roles can overlap in certain areas, they have distinct responsibilities and focus areas. Let’s dive into the differences between these roles to gain a clearer understanding.</p><h4>Technical Program Manager (TPM):</h4><p>The role of a Technical Program Manager is primarily focused on overseeing the successful execution of complex projects. TPMs work closely with cross-functional teams, such as engineering, product management, and quality assurance, to ensure the delivery of technical initiatives. Their responsibilities typically include project planning, resource allocation, risk management, and stakeholder communication. TPMs are skilled in managing timelines, dependencies, and driving alignment among various teams. They navigate the challenges of ambiguity and work to resolve issues that arise during the project lifecycle. TPMs are responsible for ensuring projects are completed on time, within budget, and meet the defined goals and objectives.</p><p>Of course this varies from organization to organization, and by level at each organization, such as at Amazon where as a principal TPM you are expected to work cross-organization, more strategically-focused and so forth.</p><h4>Engineering Manager:</h4><p>The Engineering Manager on the other hand is responsible for leading and managing the engineering team within an organization. Their primary focus is on people management and technical leadership. Engineering Managers work closely with individual engineers, providing mentorship, coaching, and career development support. They allocate resources, manage workloads, and ensure the team has the necessary tools and processes to deliver high-quality software products. Engineering Managers also collaborate with other teams, such as product management and design, to define technical strategies and align engineering efforts with overall business objectives. They play a vital role in fostering a positive team culture, facilitating communication, and creating an environment that promotes innovation and continuous improvement.</p><h4>Product Manager:</h4><p>Product Managers are responsible for defining and driving the product strategy and roadmap. They act as the voice of the customer, deeply understanding user needs, market trends, and competitive landscapes. Product Managers work closely with cross-functional teams, including engineering, design, marketing, and sales, to define product requirements, prioritize features, and manage the product development process. They bridge the gap between business objectives, user requirements, and technical feasibility. Product Managers are skilled in market research, product planning, and product launch strategies. They are responsible for ensuring that the final product aligns with the company’s vision, meets customer needs, and achieves business goals.</p><p>While the roles of TPM, Engineering Manager, and Product Manager may have distinct responsibilities, successful collaboration among them is crucial for delivering high-quality products. They often work closely together, leveraging their unique expertise to drive successful outcomes. For example, a TPM ensures the smooth execution of technical initiatives, an Engineering Manager leads the engineering team responsible for development, and a Product Manager shapes the product vision and strategy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9eb72ddd5cfa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-tpm-toolkit/the-difference-between-a-technical-program-manager-engineering-9eb72ddd5cfa">The Difference Between a Technical Program Manager, Engineering</a> was originally published in <a href="https://medium.com/the-tpm-toolkit">The TPM Toolkit</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five Key Differences between a Project and a Program]]></title>
            <link>https://medium.com/the-tpm-toolkit/five-key-differences-between-a-project-and-a-program-6f2c9c76e681?source=rss-a8104afd5a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f2c9c76e681</guid>
            <category><![CDATA[program-management]]></category>
            <category><![CDATA[portfolio-management]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Doron Katz]]></dc:creator>
            <pubDate>Tue, 27 Jun 2023 02:18:02 GMT</pubDate>
            <atom:updated>2023-07-21T02:49:06.227Z</atom:updated>
            <content:encoded><![CDATA[<h3>3 Key Differences between a Project and a Program</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*C7qte_Hy8CGpoLMB9miSrw@2x.jpeg" /></figure><p>In the realm of project management, two fundamental terms often arise: projects and programs. While they share similarities, distinguishing between them is crucial for effective management and successful execution. This article aims to shed light on the key differences between a project and a program, enabling project managers and stakeholders to understand their unique characteristics and tailor their approaches accordingly.</p><p>A <strong>project</strong> is a temporary endeavor with a specific goal, set objectives, and defined deliverables. It is a unique undertaking that follows a distinct lifecycle, typically involving a team of individuals working collaboratively to achieve predetermined outcomes. Projects have clear start and end dates, and their success is typically measured against predetermined criteria, such as budget, timeline, and quality.</p><h4>Characteristics of a Project:</h4><ol><li><strong>Defined Scope</strong>: Projects have well-defined boundaries, objectives, and deliverables. They have a specific focus and are designed to create a unique product, service, or result.</li><li><strong>Temporary Nature</strong>: Projects have a defined duration, marked by a start and end date. Once the project objectives are met and deliverables are produced, the project is considered complete.</li><li>Singular Focus: Projects typically concentrate on achieving a specific goal or outcome. They require dedicated resources, clear roles and responsibilities, and a structured plan to ensure successful completion.</li></ol><p>A <strong>program</strong>, on the other hand, comprises a group of related projects and activities managed in a coordinated manner to achieve strategic objectives that individual projects alone cannot accomplish. Programs are larger in scale, often spanning a more extended period and involving multiple interdependent projects that contribute to an overarching goal.</p><h4>Characteristics of a Program:</h4><ol><li><strong>Strategic Alignment</strong>: Programs are aligned with the organization’s strategic objectives and are designed to address complex problems or initiatives that cannot be adequately achieved through individual projects.</li><li><strong>Multiple Projects</strong>: Programs consist of multiple interdependent projects that collectively work towards achieving a common objective. These projects are managed in a coordinated manner, with shared resources and integrated planning.</li><li><strong>Ongoing Nature</strong>: Programs are long-term and enduring, extending beyond the completion of individual projects. They focus on continuous improvement, adapting to changing circumstances, and achieving sustained benefits.</li></ol><h3>Key Differences between Projects and Programs</h3><ol><li><strong>Scope and Scale</strong>: Projects have a defined scope, while programs encompass multiple projects with broader scope and strategic significance.</li><li><strong>Timeframe</strong>: Projects are temporary, with a specific start and end date, while programs are ongoing and may extend over several years.</li><li><strong>Objectives</strong>: Projects have specific, well-defined objectives, while programs are geared towards achieving strategic goals that require the collective effort of multiple projects.</li><li><strong>Interdependences</strong>: Projects are largely standalone endeavors, while programs involve interdependencies between projects, requiring coordination and integration of efforts.</li><li><strong>Resource Allocation</strong>: Projects have dedicated resources assigned to them, whereas programs share resources across multiple projects, optimizing their utilization.</li></ol><p>Distinguishing between projects and programs is crucial for effective project management and strategic alignment. Projects are discrete endeavors with specific goals and deliverables, while programs are a collection of interdependent projects working towards a broader objective. By understanding the key differences, project managers can tailor their approaches, allocate resources effectively, and ensure successful outcomes for both individual projects and overarching programs. Clear comprehension of these distinctions enables organizations to navigate the complexities of project management and optimize their strategic initiatives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f2c9c76e681" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-tpm-toolkit/five-key-differences-between-a-project-and-a-program-6f2c9c76e681">Five Key Differences between a Project and a Program</a> was originally published in <a href="https://medium.com/the-tpm-toolkit">The TPM Toolkit</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is a Parking Lot in Scrum Speak?]]></title>
            <link>https://medium.com/the-tpm-toolkit/what-is-a-parking-lot-in-scrum-speak-6d0f43c75d65?source=rss-a8104afd5a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d0f43c75d65</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Doron Katz]]></dc:creator>
            <pubDate>Tue, 27 Jun 2023 02:07:20 GMT</pubDate>
            <atom:updated>2023-06-27T02:07:20.811Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Gz2gOJ5y48jpceyGlHEwmw@2x.jpeg" /></figure><p>In project management, a <strong>Parking Lot</strong> is a designated space, either physical or virtual, where ideas, concerns, questions, or issues that arise during project meetings or discussions are recorded. These unresolved matters are “parked” in the lot to be revisited and addressed later, preventing them from derailing the current discussion or hindering project progress. <strong>Parking Lots</strong> provide the benefits of:</p><ol><li>Maintain Focus: By parking unresolved issues, the project team can maintain focus on the immediate task at hand without getting sidetracked. This ensures that meetings and discussions stay on track and productive.</li><li>Prevents Information Loss: Important ideas or concerns that arise during discussions might be forgotten or overlooked if not immediately addressed. The Parking Lot acts as a repository for capturing and retaining these valuable inputs, preventing information loss and missed opportunities.</li><li>Encourages Collaboration: The Parking Lot fosters collaboration among project team members. It provides a platform for individuals to contribute their ideas or concerns, even if they may not be relevant to the ongoing discussion. This inclusivity promotes teamwork and ensures that everyone’s input is considered.</li><li>Enhances Decision-Making: By documenting unresolved issues, the Parking Lot enables project managers and stakeholders to make informed decisions at a later stage. It allows for careful analysis and evaluation of each item, ensuring that decisions are well-considered and based on a holistic understanding of the project.</li><li>Facilitates Issue Resolution: The Parking Lot serves as a centralized location for tracking and addressing unresolved matters. By periodically revisiting the items parked in the lot, project teams can prioritize and resolve them systematically, ensuring that critical issues are not left unattended.</li></ol><p>To effectively leverage the Parking Lot technique, consider the following best practices:</p><ol><li><strong>Clear Documentation</strong>: Ensure that all items in the Parking Lot are clearly documented, including a brief description, the person responsible, and any relevant deadlines. This promotes clarity and accountability.</li><li><strong>Regular Review</strong>: Schedule dedicated times to review the items in the Parking Lot, ideally during project meetings or milestone checkpoints. This ensures that issues do not accumulate and become overwhelming.</li><li><strong>Prioritization</strong>: Assign priorities to items in the Parking Lot based on their importance and impact on the project. This allows for efficient resource allocation and timely issue resolution.</li><li><strong>Communication and Transparency</strong>: Keep the project team informed about the status of items in the Parking Lot. Regularly update stakeholders on progress, resolutions, or decisions made regarding the unresolved matters.</li></ol><p>In project management, the Parking Lot technique plays a crucial role in maintaining focus, preventing information loss, encouraging collaboration, enhancing decision-making, and facilitating issue resolution. By providing a dedicated space for capturing and revisiting unresolved matters, the Parking Lot ensures that valuable ideas and concerns are not forgotten, ultimately contributing to the successful execution of projects. Embracing this technique can significantly enhance project outcomes and promote effective teamwork within project teams.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d0f43c75d65" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-tpm-toolkit/what-is-a-parking-lot-in-scrum-speak-6d0f43c75d65">What is a Parking Lot in Scrum Speak?</a> was originally published in <a href="https://medium.com/the-tpm-toolkit">The TPM Toolkit</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Started with Swift Package Manager (SPM)]]></title>
            <link>https://medium.com/the-tpm-toolkit/getting-started-with-swift-package-manager-spm-25196eceb77b?source=rss-a8104afd5a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/25196eceb77b</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[swift-package-manager]]></category>
            <category><![CDATA[swift-library]]></category>
            <dc:creator><![CDATA[Doron Katz]]></dc:creator>
            <pubDate>Sun, 25 Jun 2023 16:01:02 GMT</pubDate>
            <atom:updated>2023-06-25T16:01:02.807Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*CXlJTrA-diBFtwoHrzjf6A@2x.jpeg" /></figure><p>Swift Package Manager (SPM) is a powerful tool provided by Apple for managing dependencies in Swift projects. It simplifies the process of integrating third-party libraries and frameworks into your projects, ensuring a smooth development experience. Prior to SPM, I had used <a href="https://cocoapods.org/">cocoapods</a> which is still indeed an active project, but with native support either Xcode baked in, I find it a much smoother and natural experience working with SPM.</p><p>In this tutorial, you will learn how to use Swift Package Manager to add and manage dependencies in your Swift projects.</p><h3>Step 1: Creating a Swift Package</h3><ol><li>Open Terminal.</li><li>Navigate to the directory where you want to create your Swift package.</li><li>Run the following command to create a new Swift package: .</li></ol><pre>swift package init</pre><p>This command will generate the basic structure for a Swift package, including the `Sources` and `Tests` directories.</p><h3>Step 2: Adding Dependencies</h3><ol><li>Open the Package.swift file in a text editor or Xcode.</li><li>Inside the `dependencies` array, add a new item for each dependency you want to include. For example:</li></ol><pre>dependencies: [ package(<br>url: “https://github.com/Alamofire/Alamofire.git”, from: “5.4.0&quot;), ]</pre><p>This example adds the Alamofire library as a dependency to your project. Adjust the URL and version requirements based on your desired library.</p><h3>Step 3: Resolving and Fetching Dependencies</h3><ol><li>In Terminal, navigate to your project’s root directory.</li><li>Run the following command to fetch and resolve the dependencies:</li></ol><pre>swift package resolve</pre><p>SPM will analyze the package manifest and fetch the required dependencies from the specified sources.</p><p>Once the dependencies are resolved, you will find a new file named `Package.resolved` that lists the resolved versions of the dependencies.</p><h3>Step 4: Using Dependencies in Your Code</h3><ol><li>Open the Swift file where you want to use the added dependency.</li><li>2. Import the module using the `import` statement. For example, to import Alamofire:</li></ol><pre>import Alamofire</pre><p>You can now use the features and functions provided by the imported dependency in your code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25196eceb77b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-tpm-toolkit/getting-started-with-swift-package-manager-spm-25196eceb77b">Getting Started with Swift Package Manager (SPM)</a> was originally published in <a href="https://medium.com/the-tpm-toolkit">The TPM Toolkit</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>