<?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 (DirkSonguer)</title>
    <link>https://pinboard.in/u:DirkSonguer/public/</link>
    <description>recent bookmarks from DirkSonguer</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://www.joelonsoftware.com/2009/03/09/how-to-be-a-program-manager/"/>
	<rdf:li rdf:resource="http://www.bloomberg.com/news/articles/2016-10-06/a-designer-s-ghost-protocol"/>
	<rdf:li rdf:resource="https://govinsider.asia/smart-gov/why-britain-banned-mobile-apps/"/>
	<rdf:li rdf:resource="http://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp#more-7646"/>
	<rdf:li rdf:resource="http://dupress.com/articles/minimum-viable-business-model-transformation-business-trends/"/>
	<rdf:li rdf:resource="http://ronjeffries.com/articles/2015-02-20-giles/"/>
	<rdf:li rdf:resource="http://mhsutton.me/scrum-designed-misuse/"/>
	<rdf:li rdf:resource="http://www.lean-agile-scrum.ch/downloads/"/>
	<rdf:li rdf:resource="http://www.internetevolution.com/document.asp?doc_id=240386&amp;print=yes"/>
	<rdf:li rdf:resource="http://www.sdtimes.com/blog/post/2011/11/11/Agile-slaves.aspx"/>
	<rdf:li rdf:resource="http://www.startuplessonslearned.com/2011/10/case-study-nordstrom-innovation-lab.html?"/>
	<rdf:li rdf:resource="http://news.quelsolaar.com/#post88"/>
	<rdf:li rdf:resource="http://www.startuplessonslearned.com/2011/05/case-study-lean-ux-at-work.html?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+startup%2Flessons%2Flearned+%28Lessons+Learned%29"/>
	<rdf:li rdf:resource="http://www.sandywalsh.com/2011/04/iterations-and-time-boxing-are-mostly.html"/>
	<rdf:li rdf:resource="http://blog.agilegamedevelopment.com/2011/03/team-motivation.html"/>
	<rdf:li rdf:resource="http://blog.agilegamedevelopment.com/2011/01/design-as-questions-development-as.html"/>
	<rdf:li rdf:resource="http://framethink.wordpress.com/2011/01/17/how-facebook-ships-code/"/>
	<rdf:li rdf:resource="http://www.johanpaul.com/blog/2010/09/non-sterile-agile-distributed-teams/"/>
	<rdf:li rdf:resource="http://timothyfitz.wordpress.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/"/>
	<rdf:li rdf:resource="http://startuplessonslearned.blogspot.com/2009/02/continuous-deployment-and-continuous.html"/>
	<rdf:li rdf:resource="http://www.agilelogic.com/sp_resources.html"/>
	<rdf:li rdf:resource="http://www.infoq.com/news/2008/12/snake-on-the-wall"/>
	<rdf:li rdf:resource="http://www.nngroup.com/reports/agile/"/>
	<rdf:li rdf:resource="http://www.tastycupcakes.com/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://www.joelonsoftware.com/2009/03/09/how-to-be-a-program-manager/">
    <title>How to be a program manager – Joel on Software</title>
    <dc:date>2018-06-21T16:48:15+00:00</dc:date>
    <link>https://www.joelonsoftware.com/2009/03/09/how-to-be-a-program-manager/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Having a good program manager is one of the secret formulas to making really great software. And you probably don’t have one on your team, because most teams don’t.]]></description>
<dc:subject>development agile management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:13c684a03b9e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.bloomberg.com/news/articles/2016-10-06/a-designer-s-ghost-protocol">
    <title>A Designer’s Ghost Protocol - Bloomberg</title>
    <dc:date>2016-11-24T09:44:59+00:00</dc:date>
    <link>http://www.bloomberg.com/news/articles/2016-10-06/a-designer-s-ghost-protocol</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Everything about Studio D Radiodurans, which Chipchase founded in 2014, is stripped-down. It has no permanent offices and no full-time staff. Its website mentions few clients or specific services, but case studies and social media posts hint at the scope of its practice: dispatches from monthslong expeditions to places such as Somalia and Tajikistan; photographs of dirt roads and remote airstrips; references to unnamed global clients who demand “keeping relationships discreet.” If Chipchase weren’t design world royalty, the whole thing might come off like viral marketing for a Jason Bourne movie.]]></description>
<dc:subject>design future agency process popup agile</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:725e948e8903/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:future"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:process"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:popup"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://govinsider.asia/smart-gov/why-britain-banned-mobile-apps/">
    <title>Why Britain banned mobile apps | GovInsider</title>
    <dc:date>2016-06-05T09:53:56+00:00</dc:date>
    <link>https://govinsider.asia/smart-gov/why-britain-banned-mobile-apps/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[So why did the GDS ban apps? It wasn’t because they weren’t technically savvy enough to build them.

Cost, he says. Apps are “very expensive to produce, and they’re very very expensive to maintain because you have to keep updating them when there are software changes,” Terrett says. “I would say if you times that by 300, you’re suddenly talking about a huge team people and a ton of money to maintain that ecosystem”.]]></description>
<dc:subject>agile business design mobile usability apps gds</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:5fc817e7d70d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:apps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:gds"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp#more-7646">
    <title>Crisp's Blog » Making sense of MVP (Minimum Viable Product) – and why I prefer Earliest Testable/Usable/Lovable</title>
    <dc:date>2016-03-07T16:21:33+00:00</dc:date>
    <link>http://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp#more-7646</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Since then the drawing has gone viral! Shows up all over the place, in articles and presentations, even in a book (Jeff Patton’s “User Story Mapping”  – an excellent read by the way). Many tell me the drawing really captures the essence of iterative & incremental development, lean startup, MVP (minimum viable product), and what not. However, some misinterpret it, which is quite natural when you take a picture out of it’s original context. Some criticize it for oversimplifying things, which is true. The picture is a metaphor. It is not about actual car development, it is about product development in general, using a car as a metaphor.]]></description>
<dc:subject>agile article diagrams spotify</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:6530337483cd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:article"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:diagrams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:spotify"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dupress.com/articles/minimum-viable-business-model-transformation-business-trends/">
    <title>Minimum viable transformation | Deloitte University Press | Business Trends</title>
    <dc:date>2015-06-05T09:09:21+00:00</dc:date>
    <link>http://dupress.com/articles/minimum-viable-business-model-transformation-business-trends/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Minimal viable products, he makes clear, are like prototypes except that they are not simply passed around and tinkered with internally. They are immediately thrown at the market and subjected to trial by fire. ]]></description>
<dc:subject>business agile strategy prototypes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:5a9406462c46/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:strategy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:prototypes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ronjeffries.com/articles/2015-02-20-giles/">
    <title>Should Scrum die in a fire?</title>
    <dc:date>2015-03-25T13:30:17+00:00</dc:date>
    <link>http://ronjeffries.com/articles/2015-02-20-giles/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[My first reaction was not the best. I should have compassionately embraced Giles’s pain. The things that he describes in those articles are bad things, and they should not happen. I am not able to stop them, because they are in the past and I can’t sit down with him and those teams anyway. I do have some advice that might be useful to him, or to anyone having similar experiences. Listening better would have been a good start. But hey, I’m a computer programmer, not a shrink.]]></description>
<dc:subject>agile projectmanagement scrum</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:89d68773bafe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:projectmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:scrum"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mhsutton.me/scrum-designed-misuse/">
    <title>Why Scrum is designed for misuse. - @mhsutton</title>
    <dc:date>2015-02-24T14:55:04+00:00</dc:date>
    <link>http://mhsutton.me/scrum-designed-misuse/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[The fundamental reason why Scrum – as it currently exists – is broken is that it is a set of instructions, roles, rituals and artifacts that purports to *not* be a recipe. But almost every one takes it as a recipe and they follow it. But there is not enough there to be a an all encompassing recipe – there can never be.

The trouble is that, as a product , Scrum needs these illusions of completeness in order that it is taken seriously . By and large this has worked. In a world that is seeking silver bullets, Scrum has succeeded beyond it’s practicality commands. It is by far the leading agile process framework in use today. It is in this illusion of completeness that lies the myriad of problems.]]></description>
<dc:subject>agile scrum projectmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:97ec5d576aa0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:projectmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.lean-agile-scrum.ch/downloads/">
    <title>Downloads | Lean Agile Scrum Conference 2012</title>
    <dc:date>2012-09-17T12:09:09+00:00</dc:date>
    <link>http://www.lean-agile-scrum.ch/downloads/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Software Produkte entwickeln statt Projekte abzuwickeln bedeutet, den vollen Produktlebenszyklus im Fokus zu haben. Projekte werden zum Meilenstein abgeschlossen. Produkte und Dienstleistungen dagegen begeistern mit dem lauffähigen Resultat. Time to Market; High Quality; Meet the Business Plan. Themen die auf der CxO Agenda stehen. Kunden begeistern mit einem konstanten Fluss und lauffähigen Deliverables. Ob XP, Agile, Scrum, Kanban oder Lean Management: Das Produkt steht im Mittelpunkt.

Am 12. September 2012 fand die Lean Agile Scrum (LAS) Konferenz bereits zum vierten Mal in Zürich statt. Sie bat den jeweils knapp 190 Praktikern „und solchen die es werden wollen“ aus dem Umfeld von Scrum, Lean, Kanban & Agile Development ein Forum zum Lernen und zum Austausch von Erfahrungen.]]></description>
<dc:subject>agile scrum talks projectmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:e56472f5e70e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:talks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:projectmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.internetevolution.com/document.asp?doc_id=240386&amp;print=yes">
    <title>Internet Evolution - The Big Report - Google's Mounting Trash Pile</title>
    <dc:date>2012-03-14T13:22:31+00:00</dc:date>
    <link>http://www.internetevolution.com/document.asp?doc_id=240386&amp;print=yes</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[In 2011, Google spent $5.2 billion on research, up 37 percent over 2010’s rate.

On what, you ask?

Robots. Elevators to outer space. A nationwide fiberoptic network. Energy created from hog waste...

Google’s vast array of engineering projects includes the sublime, the ridiculous, and just occasionally, the ingenious.

Is it all worth it?]]></description>
<dc:subject>google research fail agile</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:73301d5114e7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:fail"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.sdtimes.com/blog/post/2011/11/11/Agile-slaves.aspx">
    <title>Agile slaves</title>
    <dc:date>2012-01-23T07:34:51+00:00</dc:date>
    <link>http://www.sdtimes.com/blog/post/2011/11/11/Agile-slaves.aspx</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Last summer, I had the good fortune to visit a “very advanced” Agile shop. These folks really did embrace agile methods with a discipline, completeness, and a zealous fervor that would be hard to match. In many ways, they could have been a poster child for Agile methods...But these weren’t productive developers freed from mindless process dogma. They were Agile slaves. The dogma they followed was ours, and they followed it well. And as with many organizations in a similar position, they saw some promising results. Continuous integration, refactoring, unit tests, pair programming—all these techniques yielded some benefit. But they weren’t thinking, they weren’t reacting, they weren’t being agile. When problems came up, they addressed them with all the grace and elegance of a deer caught in the terrifying blaze of alien headlights. They knew how to do Agile; they didn’t know how to be agile.]]></description>
<dc:subject>agile development programming software projectmanagement management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:8bda04580044/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:projectmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.startuplessonslearned.com/2011/10/case-study-nordstrom-innovation-lab.html?">
    <title>Lessons Learned: Case Study: The Nordstrom Innovation Lab</title>
    <dc:date>2011-10-30T14:21:27+00:00</dc:date>
    <link>http://www.startuplessonslearned.com/2011/10/case-study-nordstrom-innovation-lab.html?</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Below, you'll find two videos: one about the lab, and one containing a case study of the team at work. Watch them both. If you have questions, JB has generously agreed to make himself available to answer them in a future post. Just leave your question as a comment to this post. If there's sufficient interest, we'll expand this MVP.]]></description>
<dc:subject>nordstrom development scrum agile prototyping</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:66f5ea31fbba/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:nordstrom"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:prototyping"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://news.quelsolaar.com/#post88">
    <title>News</title>
    <dc:date>2011-10-17T10:57:38+00:00</dc:date>
    <link>http://news.quelsolaar.com/#post88</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[The story most of you are talking about is story telling being told in text, cut scenes, voiceover, and machinima. None of that is a game, its other media squeezed in between what is a game. Games have emergent stories, or what I prefer to call drama. That's the thing that happens when you are the last counter terrorist trying to defuse the bomb in counterstrike. Quake, and Doom had drama, modern AAA games have Story telling.]]></description>
<dc:subject>gamedesign story agile iterations rage z3</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:81cd8553ff49/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:gamedesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:story"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:iterations"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:rage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:z3"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.startuplessonslearned.com/2011/05/case-study-lean-ux-at-work.html?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+startup%2Flessons%2Flearned+%28Lessons+Learned%29">
    <title>Lessons Learned: Case Study: Lean UX at work</title>
    <dc:date>2011-05-22T16:31:04+00:00</dc:date>
    <link>http://www.startuplessonslearned.com/2011/05/case-study-lean-ux-at-work.html?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+startup%2Flessons%2Flearned+%28Lessons+Learned%29</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Originally a waterfall shop, we transitioned to Agile development about two years ago. We entered the process largely blind and have had to feel our way in the dark until we found processes that worked for each team (you can read more about our transition here). Now entering our third year with Agile we’re continually trying to improve the efficiency, productivity and velocity of the various teams. Levels of Agile adoption span the full spectrum across our 6 Scrum teams. Some teams are still working to get beyond the gated approach of various phases and approval cycles while other teams are beginning to break down the silos of roles and focus on team-wide problem solving and velocity.]]></description>
<dc:subject>agile innovation startup ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:0b014d51ac02/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:innovation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:startup"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.sandywalsh.com/2011/04/iterations-and-time-boxing-are-mostly.html">
    <title>SandyWalsh.com: Iterations and Time-boxing are (Mostly) Useless</title>
    <dc:date>2011-05-04T13:32:55+00:00</dc:date>
    <link>http://www.sandywalsh.com/2011/04/iterations-and-time-boxing-are-mostly.html</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[If you know me, you know I'm not a big fan of Scrum. I don't like the hand-waving concept of Velocity and I don't like the fact that it places a priority on process over code. XP, I feel, is a much more important for software development. Agile (aka customer responsiveness) can be achieved without the dogma. But that's not the point of this post. In this post I want to question the value of timeboxing and the benefits that modern revision control systems grant developers. So, stick with it, I spend some time setting it up before getting into the meat of the post.]]></description>
<dc:subject>agile scrum projectmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:1fc7c33ddb77/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:projectmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.agilegamedevelopment.com/2011/03/team-motivation.html">
    <title>Agile Game Development: Team motivation and the role of the ScrumMaster</title>
    <dc:date>2011-03-09T10:26:38+00:00</dc:date>
    <link>http://blog.agilegamedevelopment.com/2011/03/team-motivation.html</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[The daily stand-up is a window into the motivation level of the team.  Stand-ups with motivated teams are noisy, complex, often chaotic, and information rich.   They often seem like football huddles when the score is tied and there are no timeouts left in the final two minutes of the game.  There is humor, intensity and a sense of "being in it together".

The stand-up meeting for an unmotivated team is different.  It's common to sense the boredom or an impatience for it to end.  It often feels like a group of individuals reporting to the ScrumMaster, who is writing everything down, or even worse, with everyone sitting at a conference table looking at a projection of a spreadsheet on a wall and only paying attention when it's their turn to report.

A tedious daily stand-up meeting is a symptom that the team lacks one or more of the factors of intrinsic motivation.  It's often easiest to examine the team's autonomy and the practices of the ScrumMaster, whose role is to foster and grow autonomy.]]></description>
<dc:subject>scrum agile projectmanagement management teams</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:c3097bb17660/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:projectmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:teams"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.agilegamedevelopment.com/2011/01/design-as-questions-development-as.html">
    <title>Agile Game Development: Design as questions, development as answers</title>
    <dc:date>2011-01-28T15:50:50+00:00</dc:date>
    <link>http://blog.agilegamedevelopment.com/2011/01/design-as-questions-development-as.html</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[In Scrum workshops, I often ask developers if they have ever compared the game that they last shipped against the original design document.  The usual answer is that, except for the title, much of the design changed during development.]]></description>
<dc:subject>scrum development management processes agile planning change</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:9a670c03b336/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:processes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:change"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://framethink.wordpress.com/2011/01/17/how-facebook-ships-code/">
    <title>How Facebook Ships Code « FrameThink – Frameworks for Thinking People</title>
    <dc:date>2011-01-25T11:47:30+00:00</dc:date>
    <link>http://framethink.wordpress.com/2011/01/17/how-facebook-ships-code/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[I’m fascinated by the way Facebook operates.  It’s a very unique environment, not easily replicated (nor would their system work for all companies, even if they tried).  These are notes gathered from talking with many friends at Facebook about how the company develops and releases software.]]></description>
<dc:subject>agile code development facebook software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:3e3e59532d71/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.johanpaul.com/blog/2010/09/non-sterile-agile-distributed-teams/">
    <title>Non-sterile Agile: Distributed teams | Comments, Code and Qt.</title>
    <dc:date>2011-01-14T21:59:46+00:00</dc:date>
    <link>http://www.johanpaul.com/blog/2010/09/non-sterile-agile-distributed-teams/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[I call this post non-sterile agile because I feel that once agile principles are let loose into the corporate world agile development changes its nature and face. In this (and hopefully upcoming posts) I will try to go through some of the ideas and experiences I have about agile development in the corporate world.]]></description>
<dc:subject>agile scrum projectmanagement projects</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:7abc7c1d187a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:projectmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:projects"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://timothyfitz.wordpress.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/">
    <title>Continuous Deployment at IMVU: Doing the impossible fifty times a day ...</title>
    <dc:date>2009-02-11T08:36:34+00:00</dc:date>
    <link>http://timothyfitz.wordpress.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Continuous Deployment isn’t just an abstract theory. At IMVU it’s a core part of our culture to ship. It’s also not a new technique here, we’ve been practicing continuous deployment for years; far longer than I’ve been a member of this startup.
]]></description>
<dc:subject>blog programming development article agile testing deployment english</dc:subject>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:ce8ea1e06f64/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:blog"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:article"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:english"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://startuplessonslearned.blogspot.com/2009/02/continuous-deployment-and-continuous.html">
    <title>Continuous deployment and continuous learning</title>
    <dc:date>2009-02-11T08:35:29+00:00</dc:date>
    <link>http://startuplessonslearned.blogspot.com/2009/02/continuous-deployment-and-continuous.html</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. I find these on-the-ground descriptions of the system and how they work so much more credible than just theory-type posts that I am excited to share them with you. I can personally attest that these guys know what they are talking about; I saw them do it first-hand. I will always be full of awe and gratitude for what they accomplished.
]]></description>
<dc:subject>agile deployment development blog article english</dc:subject>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:2bae4234d700/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:blog"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:article"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:english"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.agilelogic.com/sp_resources.html">
    <title>Agile Logic | Training, Workshops, Coaching, Assessment - Lean and ...</title>
    <dc:date>2009-01-28T13:44:41+00:00</dc:date>
    <link>http://www.agilelogic.com/sp_resources.html</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Agile Logic helps companies deliver better software faster. Our unique Absolute Agile approach blends the best lean and agile methods to reduce risk, maximize benefits and ensure continuous improvement.
]]></description>
<dc:subject>agile scrum templates resources articles english management</dc:subject>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:db566c8476eb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:templates"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:resources"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:articles"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:english"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.infoq.com/news/2008/12/snake-on-the-wall">
    <title>InfoQ: Using a &quot;Snake On The Wall&quot; To Quantify Impediments</title>
    <dc:date>2008-12-23T14:33:54+00:00</dc:date>
    <link>http://www.infoq.com/news/2008/12/snake-on-the-wall</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Kevin Schlabach posted recently on his Agile Commentary blog about using a "Snake On The Wall", a lightweight approach he's used to help his team get a handle on the things that are slowing their development process.
]]></description>
<dc:subject>english management article agile scrum</dc:subject>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:e7497cd2ed2b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:english"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:article"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:scrum"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nngroup.com/reports/agile/">
    <title>Agile Usability: Report on Best Practices for User Experience on Agile ...</title>
    <dc:date>2008-11-19T16:25:38+00:00</dc:date>
    <link>http://www.nngroup.com/reports/agile/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[Rapid Application Development (RAD) processes such as Agile, Scrum, and the like, simultaneously pose an opportunity and a threat to achieving a quality user experience. It all depends on how it's handled. The standard methodologies as described in books don't work in practice, if you care about the usability of your products. But small modifications work wonders, as we found when studying how Agile works on real projects.
]]></description>
<dc:subject>usability agile english papers lectures studies</dc:subject>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:ef69ff86c3f1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:english"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:papers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:lectures"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:studies"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.tastycupcakes.com/">
    <title>Tasty Cupcakes - Tasty Cupcakes</title>
    <dc:date>2008-11-14T08:41:56+00:00</dc:date>
    <link>http://www.tastycupcakes.com/</link>
    <dc:creator>DirkSonguer</dc:creator><description><![CDATA[By 'Tasty Cupcakes', we of course mean experiential learning games that accelerate the adoption and understanding of Agile principles in a fun and interactive way.
Below are games (in the form of recipe cards) that we have found useful in learning settings.
]]></description>
<dc:subject>development games agile projectmanagement english wiki</dc:subject>
<dc:identifier>https://pinboard.in/u:DirkSonguer/b:e53fca2f0aa5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:games"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:projectmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:english"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DirkSonguer/t:wiki"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>