<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Silicon Valley Project Management</title>
	<atom:link href="https://svprojectmanagement.com/feed" rel="self" type="application/rss+xml" />
	<link>https://svprojectmanagement.com</link>
	<description>Project management wisdom from practitioners and the UCSC Extension in Silicon Valley</description>
	<lastBuildDate>Thu, 10 Sep 2026 17:57:02 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>

<image>
	<url>https://svprojectmanagement.com/wp-content/uploads/2019/04/SVlogo.png</url>
	<title>Silicon Valley Project Management</title>
	<link>https://svprojectmanagement.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>The Thermo Fisher Agile Hardware Case Study 12/14: Why Sprint Planning Is Different in Hardware Development</title>
		<link>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-12-14-why-sprint-planning-is-different-in-hardware-development</link>
					<comments>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-12-14-why-sprint-planning-is-different-in-hardware-development#respond</comments>
		
		<dc:creator><![CDATA[Kevin Thompson]]></dc:creator>
		<pubDate>Thu, 10 Sep 2026 17:57:01 +0000</pubDate>
				<category><![CDATA[Miscellaneous]]></category>
		<guid isPermaLink="false">https://svprojectmanagement.com/?p=32452</guid>

					<description><![CDATA[<p>One of the predictions from my Agile Hardware research was that Sprint Planning would need to account for the specialized [&#8230;]</p>
<p>The post <a href="https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-12-14-why-sprint-planning-is-different-in-hardware-development">The Thermo Fisher Agile Hardware Case Study 12/14: Why Sprint Planning Is Different in Hardware Development</a> first appeared on <a href="https://svprojectmanagement.com">Silicon Valley Project Management</a>.</p>]]></description>
		
					<wfw:commentRss>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-12-14-why-sprint-planning-is-different-in-hardware-development/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">32452</post-id>	</item>
		<item>
		<title>Value over Velocity: What AI is teaching Agile teams about priorities</title>
		<link>https://svprojectmanagement.com/value-over-velocity-what-ai-is-teaching-agile-teams-about-priorities</link>
					<comments>https://svprojectmanagement.com/value-over-velocity-what-ai-is-teaching-agile-teams-about-priorities#comments</comments>
		
		<dc:creator><![CDATA[Shruti Reddy Alikepalli]]></dc:creator>
		<pubDate>Fri, 04 Sep 2026 21:15:32 +0000</pubDate>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Goals]]></category>
		<category><![CDATA[Priorities]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[Executing]]></category>
		<category><![CDATA[Team Leadership]]></category>
		<category><![CDATA[AI]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Scrum]]></category>
		<category><![CDATA[Values]]></category>
		<category><![CDATA[#AI]]></category>
		<category><![CDATA[#ASVPM]]></category>
		<category><![CDATA[#ScaledValuePM]]></category>
		<category><![CDATA[#agile #scrum #projectmanagement #SVPM]]></category>
		<guid isPermaLink="false">https://svprojectmanagement.com/?p=32397</guid>

					<description><![CDATA[<p>Picture this: It&#8217;s a random Tuesday, and a stakeholder drops a familiar message in Slack: &#8220;Can we add a bulk [&#8230;]</p>
<p>The post <a href="https://svprojectmanagement.com/value-over-velocity-what-ai-is-teaching-agile-teams-about-priorities">Value over Velocity: What AI is teaching Agile teams about priorities</a> first appeared on <a href="https://svprojectmanagement.com">Silicon Valley Project Management</a>.</p>]]></description>
		
					<wfw:commentRss>https://svprojectmanagement.com/value-over-velocity-what-ai-is-teaching-agile-teams-about-priorities/feed</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">32397</post-id>	</item>
		<item>
		<title>The Thermo Fisher Agile Hardware Case Study 11/14: Why Velocity Is Different in Hardware Development</title>
		<link>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-11-14-why-velocity-is-different-in-hardware-development</link>
					<comments>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-11-14-why-velocity-is-different-in-hardware-development#respond</comments>
		
		<dc:creator><![CDATA[Kevin Thompson]]></dc:creator>
		<pubDate>Fri, 28 Aug 2026 16:29:54 +0000</pubDate>
				<category><![CDATA[Miscellaneous]]></category>
		<guid isPermaLink="false">https://svprojectmanagement.com/?p=32369</guid>

					<description><![CDATA[<p>One of the predictions from my Agile Hardware research was that Velocity would behave differently when teams estimated work in [&#8230;]</p>
<p>The post <a href="https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-11-14-why-velocity-is-different-in-hardware-development">The Thermo Fisher Agile Hardware Case Study 11/14: Why Velocity Is Different in Hardware Development</a> first appeared on <a href="https://svprojectmanagement.com">Silicon Valley Project Management</a>.</p>]]></description>
		
					<wfw:commentRss>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-11-14-why-velocity-is-different-in-hardware-development/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">32369</post-id>	</item>
		<item>
		<title>The Thermo Fisher Agile Hardware Case Study 10/14: Story Points Do Not Work Well for Hardware Teams Every Scrum team</title>
		<link>https://svprojectmanagement.com/32288-2</link>
					<comments>https://svprojectmanagement.com/32288-2#respond</comments>
		
		<dc:creator><![CDATA[Kevin Thompson]]></dc:creator>
		<pubDate>Thu, 20 Aug 2026 17:16:25 +0000</pubDate>
				<category><![CDATA[Miscellaneous]]></category>
		<guid isPermaLink="false">https://svprojectmanagement.com/?p=32288</guid>

					<description><![CDATA[<p>Every Scrum team must estimate work in order to plan Releases and Sprints. At Thermo Fisher Scientific, we used the [&#8230;]</p>
<p>The post <a href="https://svprojectmanagement.com/32288-2">The Thermo Fisher Agile Hardware Case Study 10/14: Story Points Do Not Work Well for Hardware Teams Every Scrum team</a> first appeared on <a href="https://svprojectmanagement.com">Silicon Valley Project Management</a>.</p>]]></description>
		
					<wfw:commentRss>https://svprojectmanagement.com/32288-2/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">32288</post-id>	</item>
		<item>
		<title>The Thermo Fisher Agile Hardware Case Study 9/14: Quality Assurance Specialists Do Not Test Most Story Deliverables</title>
		<link>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-9-14-quality-assurance-specialists-do-not-test-most-story-deliverables</link>
					<comments>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-9-14-quality-assurance-specialists-do-not-test-most-story-deliverables#respond</comments>
		
		<dc:creator><![CDATA[Kevin Thompson]]></dc:creator>
		<pubDate>Thu, 13 Aug 2026 16:24:01 +0000</pubDate>
				<category><![CDATA[Miscellaneous]]></category>
		<guid isPermaLink="false">https://svprojectmanagement.com/?p=32269</guid>

					<description><![CDATA[<p>One of the predictions from my Agile Hardware research was that the traditional software Quality Assurance model would not transfer [&#8230;]</p>
<p>The post <a href="https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-9-14-quality-assurance-specialists-do-not-test-most-story-deliverables">The Thermo Fisher Agile Hardware Case Study 9/14: Quality Assurance Specialists Do Not Test Most Story Deliverables</a> first appeared on <a href="https://svprojectmanagement.com">Silicon Valley Project Management</a>.</p>]]></description>
		
					<wfw:commentRss>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-9-14-quality-assurance-specialists-do-not-test-most-story-deliverables/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">32269</post-id>	</item>
		<item>
		<title>The Thermo Fisher Agile Hardware Case Study 8/14: Product Owners Don&#8217;t Write Most Stories</title>
		<link>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-8-14-product-owners-dont-write-most-stories</link>
					<comments>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-8-14-product-owners-dont-write-most-stories#respond</comments>
		
		<dc:creator><![CDATA[Kevin Thompson]]></dc:creator>
		<pubDate>Thu, 06 Aug 2026 16:37:12 +0000</pubDate>
				<category><![CDATA[Miscellaneous]]></category>
		<guid isPermaLink="false">https://svprojectmanagement.com/?p=32258</guid>

					<description><![CDATA[<p>One of the predictions from my earlier research into Agile hardware development was that Product Owners would write a much [&#8230;]</p>
<p>The post <a href="https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-8-14-product-owners-dont-write-most-stories">The Thermo Fisher Agile Hardware Case Study 8/14: Product Owners Don’t Write Most Stories</a> first appeared on <a href="https://svprojectmanagement.com">Silicon Valley Project Management</a>.</p>]]></description>
		
					<wfw:commentRss>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-8-14-product-owners-dont-write-most-stories/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">32258</post-id>	</item>
		<item>
		<title>The Thermo Fisher Agile Hardware Case Study 7/14: Story Writing Proves Difficult</title>
		<link>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-7-14-story-writing-proves-difficult</link>
					<comments>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-7-14-story-writing-proves-difficult#respond</comments>
		
		<dc:creator><![CDATA[Kevin Thompson]]></dc:creator>
		<pubDate>Wed, 29 Jul 2026 19:48:22 +0000</pubDate>
				<category><![CDATA[Miscellaneous]]></category>
		<guid isPermaLink="false">https://svprojectmanagement.com/?p=32203</guid>

					<description><![CDATA[<p>One of the surprises during the Thermo Fisher Scientific engagement was that the team initially struggled with writing Epics and [&#8230;]</p>
<p>The post <a href="https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-7-14-story-writing-proves-difficult">The Thermo Fisher Agile Hardware Case Study 7/14: Story Writing Proves Difficult</a> first appeared on <a href="https://svprojectmanagement.com">Silicon Valley Project Management</a>.</p>]]></description>
		
					<wfw:commentRss>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-7-14-story-writing-proves-difficult/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">32203</post-id>	</item>
		<item>
		<title>The Thermo Fisher Agile Hardware Case Study 6/14: Say Good-Bye to User Stories?</title>
		<link>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-6-14-say-good-bye-to-user-stories</link>
					<comments>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-6-14-say-good-bye-to-user-stories#respond</comments>
		
		<dc:creator><![CDATA[Kevin Thompson]]></dc:creator>
		<pubDate>Thu, 23 Jul 2026 17:27:20 +0000</pubDate>
				<category><![CDATA[Miscellaneous]]></category>
		<guid isPermaLink="false">https://svprojectmanagement.com/?p=32191</guid>

					<description><![CDATA[<p>One of the more surprising discoveries during the Thermo Fisher Scientific engagement involved the role of User Stories. In software [&#8230;]</p>
<p>The post <a href="https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-6-14-say-good-bye-to-user-stories">The Thermo Fisher Agile Hardware Case Study 6/14: Say Good-Bye to User Stories?</a> first appeared on <a href="https://svprojectmanagement.com">Silicon Valley Project Management</a>.</p>]]></description>
		
					<wfw:commentRss>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-6-14-say-good-bye-to-user-stories/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">32191</post-id>	</item>
		<item>
		<title>The Thermo Fisher Agile Hardware Case Study 5/14: Hardware Products Accrete Components, Not Functionality</title>
		<link>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-5-14-hardware-products-accrete-components-not-functionality</link>
					<comments>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-5-14-hardware-products-accrete-components-not-functionality#respond</comments>
		
		<dc:creator><![CDATA[Kevin Thompson]]></dc:creator>
		<pubDate>Thu, 16 Jul 2026 21:46:57 +0000</pubDate>
				<category><![CDATA[Miscellaneous]]></category>
		<guid isPermaLink="false">https://svprojectmanagement.com/?p=32186</guid>

					<description><![CDATA[<p>As the Thermo Fisher Scientific project progressed, I began to notice another fundamental difference between hardware and software development. Even [&#8230;]</p>
<p>The post <a href="https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-5-14-hardware-products-accrete-components-not-functionality">The Thermo Fisher Agile Hardware Case Study 5/14: Hardware Products Accrete Components, Not Functionality</a> first appeared on <a href="https://svprojectmanagement.com">Silicon Valley Project Management</a>.</p>]]></description>
		
					<wfw:commentRss>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-5-14-hardware-products-accrete-components-not-functionality/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">32186</post-id>	</item>
		<item>
		<title>For flow &#038; adaptiveness in software development, time-box the work – not batches such as Sprints</title>
		<link>https://svprojectmanagement.com/for-flow-adaptiveness-in-software-development-time-box-the-work-not-batches-such-as-sprints</link>
					<comments>https://svprojectmanagement.com/for-flow-adaptiveness-in-software-development-time-box-the-work-not-batches-such-as-sprints#respond</comments>
		
		<dc:creator><![CDATA[Niels Pflaeging]]></dc:creator>
		<pubDate>Thu, 09 Jul 2026 18:16:55 +0000</pubDate>
				<category><![CDATA[Time]]></category>
		<category><![CDATA[Cost]]></category>
		<category><![CDATA[Quality]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[TOSD]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[project-management]]></category>
		<guid isPermaLink="false">https://svprojectmanagement.com/?p=32076</guid>

					<description><![CDATA[<p>In software development, adopting Sprints, cadences and &#8220;iterations&#8221; was never a path to agility and flow: It was yet another [&#8230;]</p>
<p>The post <a href="https://svprojectmanagement.com/for-flow-adaptiveness-in-software-development-time-box-the-work-not-batches-such-as-sprints">For flow & adaptiveness in software development, time-box the work – not batches such as Sprints</a> first appeared on <a href="https://svprojectmanagement.com">Silicon Valley Project Management</a>.</p>]]></description>
		
					<wfw:commentRss>https://svprojectmanagement.com/for-flow-adaptiveness-in-software-development-time-box-the-work-not-batches-such-as-sprints/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">32076</post-id>	</item>
		<item>
		<title>The Thermo Fisher Agile Hardware Case Study 4/14: Scope Decomposition Is Not Driven by User Experience</title>
		<link>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-4-14-scope-decomposition-is-not-driven-by-user-experience</link>
					<comments>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-4-14-scope-decomposition-is-not-driven-by-user-experience#respond</comments>
		
		<dc:creator><![CDATA[Kevin Thompson]]></dc:creator>
		<pubDate>Thu, 09 Jul 2026 16:21:41 +0000</pubDate>
				<category><![CDATA[Miscellaneous]]></category>
		<guid isPermaLink="false">https://svprojectmanagement.com/?p=32165</guid>

					<description><![CDATA[<p>One of the first challenges facing the Thermo Fisher Scientific team was defining the scope of the product in a [&#8230;]</p>
<p>The post <a href="https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-4-14-scope-decomposition-is-not-driven-by-user-experience">The Thermo Fisher Agile Hardware Case Study 4/14: Scope Decomposition Is Not Driven by User Experience</a> first appeared on <a href="https://svprojectmanagement.com">Silicon Valley Project Management</a>.</p>]]></description>
		
					<wfw:commentRss>https://svprojectmanagement.com/the-thermo-fisher-agile-hardware-case-study-4-14-scope-decomposition-is-not-driven-by-user-experience/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">32165</post-id>	</item>
	</channel>
</rss>
