<?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 (jm)</title>
    <link>https://pinboard.in/u:jm/public/</link>
    <description>recent bookmarks from jm</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://medium.com/@dekaah/22-axioms-of-the-extreme-go-horse-methodology-xgh-9fa739ab55b4"/>
	<rdf:li rdf:resource="https://cutle.fish/blog/12-signs-youre-working-in-a-feature-factory"/>
	<rdf:li rdf:resource="https://apenwarr.ca/log/20171213"/>
	<rdf:li rdf:resource="https://www.quora.com/Why-do-some-developers-at-strong-companies-like-Google-consider-Agile-development-to-be-nonsense/answer/David-Jeske?share=1"/>
	<rdf:li rdf:resource="http://rc3.org/2013/03/03/dont-get-stuck/"/>
	<rdf:li rdf:resource="https://blog.mozilla.org/webdev/2013/04/22/kanban-for-mdn-development/"/>
	<rdf:li rdf:resource="http://www.quora.com/Engineering-Management/Why-are-software-development-task-estimations-regularly-off-by-a-factor-of-2-3"/>
	<rdf:li rdf:resource="http://blog.tridgell.net/?p=111"/>
	<rdf:li rdf:resource="http://www.pivotaltracker.com/learnmore"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://medium.com/@dekaah/22-axioms-of-the-extreme-go-horse-methodology-xgh-9fa739ab55b4">
    <title>eXtreme Go Horse Methodology (XGH)</title>
    <dc:date>2022-06-23T09:34:15+00:00</dc:date>
    <link>https://medium.com/@dekaah/22-axioms-of-the-extreme-go-horse-methodology-xgh-9fa739ab55b4</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>
By talking about Agile Marketing, and Agile in general, with a foreign friend, I figured out that people outside Brazil are not familiar with the eXtreme Go Horse Methodology. Even though we’ve seen it applied to many companies (like Tesla), apparently this widely used global methodology was only formally detailed by Brazilian Devs.
</blockquote>

Example XGH methodology: "In XGH you don’t think, you do the first thing that comes to your mind. There’s not a second option as the first one is faster."]]></description>
<dc:subject>satire agile programming coding xgh tesla methodologies process</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:b6926d104c92/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:satire"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:xgh"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tesla"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:methodologies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:process"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cutle.fish/blog/12-signs-youre-working-in-a-feature-factory">
    <title>12 Signs You’re Working in a Feature Factory</title>
    <dc:date>2020-02-17T13:00:29+00:00</dc:date>
    <link>https://cutle.fish/blog/12-signs-youre-working-in-a-feature-factory</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>I’ve used the term *Feature Factory *at a couple conference talks over the past two years. I started using the term when a software developer friend complained that he was “just sitting in the factory, cranking out features, and sending them down the line.”</blockquote>

heh, this rings a bell....]]></description>
<dc:subject>features product-management agile teams work management product companies prioritization planning</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:c4f2ce936374/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:features"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:product-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:product"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:companies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:prioritization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:planning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://apenwarr.ca/log/20171213">
    <title>An epic treatise on scheduling, bug tracking, and triage</title>
    <dc:date>2019-10-25T11:41:00+00:00</dc:date>
    <link>https://apenwarr.ca/log/20171213</link>
    <dc:creator>jm</dc:creator><description><![CDATA[by apenwarr.  Excellent stuff -- most of what we do in Swrve for scheduling is included here]]></description>
<dc:subject>agile management software programming scheduling triage bugs backlogs jira</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:24ba57f7dcef/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scheduling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:triage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bugs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:backlogs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:jira"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.quora.com/Why-do-some-developers-at-strong-companies-like-Google-consider-Agile-development-to-be-nonsense/answer/David-Jeske?share=1">
    <title>David Jeske's answer to Why do some developers at strong companies like Google consider Agile development to be nonsense? - Quora</title>
    <dc:date>2019-08-06T11:57:13+00:00</dc:date>
    <link>https://www.quora.com/Why-do-some-developers-at-strong-companies-like-Google-consider-Agile-development-to-be-nonsense/answer/David-Jeske?share=1</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Wow, this is a great answer.  As he notes, the Scrum-style process is flawed for big backend projects:

"This style of short-term planning, direct customer contact, and continuous iteration is well suited to software with a simple core and lots of customer visible features that are incrementally useful. It is not so well suited to software which has a very simple interface and tons of hidden internal complexity, software which isn’t useful until it’s fairly complete, or leapfrog solutions the customer can’t imagine."

And he goes on to come up with something which works better for Google-style projects:

<blockquote>
Our highest priority is to increase customer (and programmer) productivity and access to information. Work on the biggest, most frequently used problems you can find, and create the largest net impact. Don’t give the customer what they ask for; understand them, and revolutionize their world.

Developers should create a Google Design Document (a fairly minimal, but structured design doc), explaining the project, what goals it hopes to achieve, and explains why it can’t be done in other ways. This document should be circulated with stakeholders, to get early feedback before the project gets underway. The written record is essential, as it assures there is a clear and agreed understanding of when the project is a success and how it aims to get there.
At all phases of the project, critical design elements for larger components should be concisely explained and captured in a design document.

Innovate in leapfrogs. It’s more important to finish and deploy a leapfrog than to attempt perfection. There is no perfection. Instead be flexible, and plan to constantly reinvent at every level of the stack.

Deliver working software as soon as is reasonably possible, and no sooner. “Dogfood” projects internally before they are shipped externally. Make sure products meet high quality standards before shipping. The quality of the product is more important than the time it takes to achieve it.</blockquote>

]]></description>
<dc:subject>agile architecture google scrum development coding projects project-management design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:a6046dfadf0d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:projects"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://rc3.org/2013/03/03/dont-get-stuck/">
    <title>Don’t get stuck</title>
    <dc:date>2014-01-04T21:30:16+00:00</dc:date>
    <link>http://rc3.org/2013/03/03/dont-get-stuck/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Good description of Etsy's take on continuous deployment, committing directly to trunk, hidden with feature-flags, from Rafe Colburn]]></description>
<dc:subject>continuous-deployment coding agile deployment devops etsy rafe-colburn</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:d8dec5f4bf39/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:continuous-deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:devops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:etsy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rafe-colburn"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.mozilla.org/webdev/2013/04/22/kanban-for-mdn-development/">
    <title>Kanban for MDN development</title>
    <dc:date>2013-05-01T11:07:22+00:00</dc:date>
    <link>https://blog.mozilla.org/webdev/2013/04/22/kanban-for-mdn-development/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Mozilla's experience with Kanban.  We've had good results in Amazon, too.  good intro links in this post -- might start talking about it in Swrve...]]></description>
<dc:subject>kanban scheduling team agile mozilla</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:5dc3f963dfa9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:kanban"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scheduling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:team"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mozilla"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.quora.com/Engineering-Management/Why-are-software-development-task-estimations-regularly-off-by-a-factor-of-2-3">
    <title>The best &quot;why estimation is hard&quot; parable I've read this week</title>
    <dc:date>2012-02-02T10:02:02+00:00</dc:date>
    <link>http://www.quora.com/Engineering-Management/Why-are-software-development-task-estimations-regularly-off-by-a-factor-of-2-3</link>
    <dc:creator>jm</dc:creator><description><![CDATA['A tense silence falls between us. The phone call goes unmade. I'll call tomorrow once my comrade regains his senses and is willing to commit to something reasonable.']]></description>
<dc:subject>agile development management programming teams estimation tasks software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:c04b6424baf4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:estimation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tasks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.tridgell.net/?p=111">
    <title>Andrew Tridgell's pair programming experience</title>
    <dc:date>2010-12-06T23:12:25+00:00</dc:date>
    <link>http://blog.tridgell.net/?p=111</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Pair-programming with another SAMBA developer over the course of a year, using a SIP server and a VNC-shared desktop. very positive review indeed]]></description>
<dc:subject>pair-programming xp tridge coding collaboration agile vnc sip</dc:subject>
<dc:identifier>https://pinboard.in/u:jm/b:9faa1eb00d21/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:pair-programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:xp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tridge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:vnc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sip"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.pivotaltracker.com/learnmore">
    <title>Pivotal Tracker</title>
    <dc:date>2010-03-26T12:17:37+00:00</dc:date>
    <link>http://www.pivotaltracker.com/learnmore</link>
    <dc:creator>jm</dc:creator><description><![CDATA[hmm, nice-looking Scrum tool]]></description>
<dc:subject>scrum collaboration dev management project-management tools agile</dc:subject>
<dc:identifier>https://pinboard.in/u:jm/b:3ecfaea9fd7f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:dev"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:agile"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>