<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (plindberg)</title>
    <link>https://pinboard.in/u:plindberg/public/</link>
    <description>recent bookmarks from plindberg</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://jchyip.medium.com/the-top-3-points-you-should-have-paid-attention-to-in-the-spotify-engineering-culture-videos-that-f936a512fb3b"/>
	<rdf:li rdf:resource="https://sprint.ly/"/>
	<rdf:li rdf:resource="http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html"/>
	<rdf:li rdf:resource="http://www.bananascrum.com/"/>
	<rdf:li rdf:resource="http://www.architecturalpractices.com/articles_xpm.html"/>
	<rdf:li rdf:resource="http://www.computerworld.com/managementtopics/management/project/story/0,10801,93641,00.html"/>
	<rdf:li rdf:resource="http://bossavit.com/thoughts/archives/000719.html"/>
	<rdf:li rdf:resource="http://www.informit.com/isapi/product_id~{3EE7D21A-C3CD-4D18-8585-6CF532664022}/content/index.asp"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://jchyip.medium.com/the-top-3-points-you-should-have-paid-attention-to-in-the-spotify-engineering-culture-videos-that-f936a512fb3b">
    <title>The top 3 points you should have paid attention to in the Spotify Engineering Culture videos that aren’t Squads, Chapters, Tribes, Guilds | by Jason Yip | Feb, 2022 | Medium</title>
    <dc:date>2022-02-07T06:44:40+00:00</dc:date>
    <link>https://jchyip.medium.com/the-top-3-points-you-should-have-paid-attention-to-in-the-spotify-engineering-culture-videos-that-f936a512fb3b</link>
    <dc:creator>plindberg</dc:creator><description><![CDATA[Most of the time when someone mentions the “Spotify Model”, they only talk about structure: Squads, Chapters, Tribes, Guilds. When it comes to product development culture, structure is the last thing…]]></description>
<dc:subject>spotify via:twitter agile</dc:subject>
<dc:identifier>https://pinboard.in/u:plindberg/b:4d609765e219/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:spotify"/>
	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:via:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:agile"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://sprint.ly/">
    <title>Make beautiful products - sprint.ly</title>
    <dc:date>2012-10-23T09:25:05+00:00</dc:date>
    <link>https://sprint.ly/</link>
    <dc:creator>plindberg</dc:creator><dc:subject>scrum agile kanban</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:plindberg/b:46a206a0bb84/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:kanban"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html">
    <title>ReinH | A Git Workflow for Agile Teams</title>
    <dc:date>2009-05-24T21:21:00+00:00</dc:date>
    <link>http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html</link>
    <dc:creator>plindberg</dc:creator><dc:subject>git workflow agile via:jonaslejon</dc:subject>
<dc:identifier>https://pinboard.in/u:plindberg/b:e2c300559fb6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:workflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:via:jonaslejon"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.bananascrum.com/">
    <title>Welcome to Banana Scrum - scrum project management tool</title>
    <dc:date>2008-11-24T10:07:51+00:00</dc:date>
    <link>http://www.bananascrum.com/</link>
    <dc:creator>plindberg</dc:creator><dc:subject>scrum xlent projectmanagement agile</dc:subject>
<dc:identifier>https://pinboard.in/u:plindberg/b:9c459dc5356c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:xlent"/>
	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:projectmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:agile"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.architecturalpractices.com/articles_xpm.html">
    <title>Architectural Practices: Extreme Project Management.</title>
    <dc:date>2004-12-16T05:33:41+00:00</dc:date>
    <link>http://www.architecturalpractices.com/articles_xpm.html</link>
    <dc:creator>plindberg</dc:creator><description><![CDATA["[Extreme Programming] practices can be readily and beneficially adapted to architecture. This paper shows how." Written by an architect/software developer. (Via Jonas Bengtsson.)]]></description>
<dc:subject>agile architecture xp</dc:subject>
<dc:identifier>https://pinboard.in/u:plindberg/b:2a67c76c04c5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:xp"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.computerworld.com/managementtopics/management/project/story/0,10801,93641,00.html">
    <title>Big IT: Doomed - Computerworld.</title>
    <dc:date>2004-06-14T12:07:07+00:00</dc:date>
    <link>http://www.computerworld.com/managementtopics/management/project/story/0,10801,93641,00.html</link>
    <dc:creator>plindberg</dc:creator><description><![CDATA["So how does this big -- and successful -- IT project prove that big IT projects are doomed? It became successful only because [they] _stopped_ running it as a big IT project."]]></description>
<dc:subject>agile</dc:subject>
<dc:identifier>https://pinboard.in/u:plindberg/b:d13f7a52a319/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:agile"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bossavit.com/thoughts/archives/000719.html">
    <title>Incipient(thoughts): Self-Organizing Teams.</title>
    <dc:date>2004-03-31T05:09:23+00:00</dc:date>
    <link>http://bossavit.com/thoughts/archives/000719.html</link>
    <dc:creator>plindberg</dc:creator><description><![CDATA["The Agile Manifesto states: 'The best architectures, requirements, and designs emerge from self-organizing teams.' Yet the topic of self-organizing teams seems to barely deserve a mention at conferences or in articles."]]></description>
<dc:subject>agile</dc:subject>
<dc:identifier>https://pinboard.in/u:plindberg/b:76fd1551d981/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:agile"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.informit.com/isapi/product_id~{3EE7D21A-C3CD-4D18-8585-6CF532664022}/content/index.asp">
    <title>Jim Highsmith: Agile Software Development: Why It's Hot!</title>
    <dc:date>2004-01-04T17:10:29+00:00</dc:date>
    <link>http://www.informit.com/isapi/product_id~{3EE7D21A-C3CD-4D18-8585-6CF532664022}/content/index.asp</link>
    <dc:creator>plindberg</dc:creator><dc:subject>agile</dc:subject>
<dc:identifier>https://pinboard.in/u:plindberg/b:86f3631ee316/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:plindberg/t:agile"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>