<?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 (Vaguery)</title>
    <link>https://pinboard.in/u:Vaguery/public/</link>
    <description>recent bookmarks from Vaguery</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://arxiv.org/abs/2101.10291"/>
	<rdf:li rdf:resource="https://infodump.ghost.io/how-to-juggle-projects/"/>
	<rdf:li rdf:resource="https://adrianhoward.com/posts/failure-swapshop/"/>
	<rdf:li rdf:resource="http://martinfowler.com/articles/workflowsOfRefactoring/"/>
	<rdf:li rdf:resource="http://unrealnature.wordpress.com/2014/11/11/energy/"/>
	<rdf:li rdf:resource="https://code.google.com/p/gerrit/"/>
	<rdf:li rdf:resource="http://agileconsulting.blogspot.ca/2012/05/integrating-story-mapping-with-kanban.html"/>
	<rdf:li rdf:resource="http://net.tutsplus.com/tutorials/tools-and-tips/git-tips-from-the-pros/"/>
	<rdf:li rdf:resource="http://mobprogramming.org/"/>
	<rdf:li rdf:resource="http://agilefantasies.wordpress.com/2012/03/25/moral-hazard-the-implacable-enemy-of-agile/"/>
	<rdf:li rdf:resource="http://blog.intercom.io/design-and-premature-optimization/"/>
	<rdf:li rdf:resource="http://arxiv.org/abs/1112.4323"/>
	<rdf:li rdf:resource="http://cumulative-hypotheses.org/2011/09/16/iterative-incremental-kanban/"/>
	<rdf:li rdf:resource="http://sandofsky.com/blog/git-workflow.html"/>
	<rdf:li rdf:resource="http://stackoverflow.com/questions/930612/git-remove-oldest-revisions-of-a-file/931054#931054"/>
	<rdf:li rdf:resource="http://xprogramming.com/articles/kate-oneal-and-the-mythical-italian-restaurant/"/>
	<rdf:li rdf:resource="http://www.agileproductdesign.com/blog/the_new_backlog.html"/>
	<rdf:li rdf:resource="http://agilistry.com/events/agile-management/"/>
	<rdf:li rdf:resource="http://getmentalnotes.com/"/>
	<rdf:li rdf:resource="http://blog.wilshipley.com/2011/04/success-and-farming-vs-mining.html"/>
	<rdf:li rdf:resource="http://dashes.com/anil/2010/09/forking-is-a-feature.html"/>
	<rdf:li rdf:resource="https://elearning.industriallogic.com/gh/submit?Action=PageAction&amp;album=blog2009&amp;path=blog2009/2010/redefiningDone&amp;devLanguage=Java"/>
	<rdf:li rdf:resource="http://www.cs.brown.edu/people/acb/codebubbles_site.htm"/>
	<rdf:li rdf:resource="http://i-dont-trust-your-code.heroku.com/"/>
	<rdf:li rdf:resource="http://code.google.com/p/gource/"/>
	<rdf:li rdf:resource="http://xprogramming.com/articles/quality/"/>
	<rdf:li rdf:resource="http://unethicalblogger.com/posts/2010/04/rebasebased_workflow"/>
	<rdf:li rdf:resource="http://www.itskeptic.org/shit-happens-or-how-i-learned-love-incident"/>
	<rdf:li rdf:resource="http://github.com/guides/completely-remove-a-file-from-all-revisions"/>
	<rdf:li rdf:resource="http://catenary.wordpress.com/2009/11/29/against-semat/"/>
	<rdf:li rdf:resource="http://japhr.blogspot.com/2010/02/retrospective-week-one.html"/>
	<rdf:li rdf:resource="http://zenhabits.net/2010/02/completion-principles/"/>
	<rdf:li rdf:resource="http://theagileexecutive.com/2010/02/19/the-agile-flywheel/"/>
	<rdf:li rdf:resource="http://tgethr.com/welcome/tour"/>
	<rdf:li rdf:resource="http://pivotallabs.com/users/dan/blog/articles/1135-pivotal-tracker-api-new-version-v3-to-be-released-on-jan-23"/>
	<rdf:li rdf:resource="http://www.gcbl.org/blog/marc-lefkowitz/city-planning-throws-weight-behind-open-access-innerbelt-bridge"/>
	<rdf:li rdf:resource="http://nvie.com/archives/323"/>
	<rdf:li rdf:resource="http://blog.mountaingoatsoftware.com/build-trust-between-teams-with-ambassadors"/>
	<rdf:li rdf:resource="http://gojko.net/2009/12/04/eight-interesting-techniques-to-test-how-a-project-is-going/"/>
	<rdf:li rdf:resource="http://www.slideshare.net/ourfounder/personal-kanban-101"/>
	<rdf:li rdf:resource="http://pivotallabs.com/users/ian/blog/articles/1010-explaining-the-value-of-agile-rails-and-the-cloud"/>
	<rdf:li rdf:resource="http://codeintensity.blogspot.com/2008/12/github-post-receive-hook-for-pivotal.html"/>
	<rdf:li rdf:resource="http://github.com/tpope/pickler"/>
	<rdf:li rdf:resource="http://thedailywtf.com/Articles/Classic-WTF-The-Cool-Cam.aspx"/>
	<rdf:li rdf:resource="http://blog.crisp.se/henrikkniberg/2009/06/26/1246053060000.html"/>
	<rdf:li rdf:resource="http://github.com/scrumalliance"/>
	<rdf:li rdf:resource="http://bucketworks.org/concepts"/>
	<rdf:li rdf:resource="https://www.pivotaltracker.com/learnmore"/>
	<rdf:li rdf:resource="http://www.randsinrepose.com/archives/2009/03/23/the_makers_of_things.html"/>
	<rdf:li rdf:resource="http://www.exampler.com/blog/2008/05/21/everyone-needs-a-cryptic-slogan/"/>
	<rdf:li rdf:resource="http://www.nomachetejuggling.com/2008/12/11/my-least-favorite-interview-question/"/>
	<rdf:li rdf:resource="http://cavlec.yarinareth.net/2009/02/19/humanists-and-the-digital/"/>
	<rdf:li rdf:resource="http://www.michaelnygard.com/blog/2009/02/fast_iteration_versus_elegant.html"/>
	<rdf:li rdf:resource="http://blog.objectmentor.com/articles/2009/02/17/the-bloat-at-the-edge-of-duplication-removal-the-orange-model"/>
	<rdf:li rdf:resource="http://www.codinghorror.com/blog/archives/001226.html"/>
	<rdf:li rdf:resource="http://www.codinghorror.com/blog/archives/001227.html"/>
	<rdf:li rdf:resource="http://www.alistapart.com/articles/gettingrealaboutagiledesign"/>
	<rdf:li rdf:resource="http://kiloblog.com/post/sharing-code-for-what-its-worth/"/>
	<rdf:li rdf:resource="http://www.xprogramming.com/xpmag/whatisxp.htm"/>
	<rdf:li rdf:resource="http://www.redmine.org/"/>
	<rdf:li rdf:resource="http://culturedcode.com/things/"/>
	<rdf:li rdf:resource="http://areyouexpendable.com/a/"/>
	<rdf:li rdf:resource="http://cns2.uni.edu/~wallingf/blog/archives/monthly/2007-10.html#e2007-10-10T19_10_57.htm"/>
	<rdf:li rdf:resource="http://www.stateofflow.com/journal/51/estimation-xperiment"/>
	<rdf:li rdf:resource="http://www.owellprecast.com/15.html"/>
	<rdf:li rdf:resource="http://metacool.typepad.com/metacool/2007/07/more-garage-maj.html"/>
	<rdf:li rdf:resource="http://www.dhemery.com/cwd/2003/08/estimates_are_not_commitments.html"/>
	<rdf:li rdf:resource="http://scholar.google.com/scholar?hl=en&amp;lr=&amp;q=related:2hJ7JsgD0TIJ:scholar.google.com/"/>
	<rdf:li rdf:resource="http://www.retrospectives.com/"/>
	<rdf:li rdf:resource="http://malvasiabianca.org/archives/2007/02/dont-broadcast-information/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://arxiv.org/abs/2101.10291">
    <title>[2101.10291] The Shifting Sands of Motivation: Revisiting What Drives Contributors in Open Source</title>
    <dc:date>2022-03-13T10:59:53+00:00</dc:date>
    <link>https://arxiv.org/abs/2101.10291</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Open Source Software (OSS) has changed drastically over the last decade, with OSS projects now producing a large ecosystem of popular products, involving industry participation, and providing professional career opportunities. But our field's understanding of what motivates people to contribute to OSS is still fundamentally grounded in studies from the early 2000s. With the changed landscape of OSS, it is very likely that motivations to join OSS have also evolved. Through a survey of 242 OSS contributors, we investigate shifts in motivation from three perspectives: (1) the impact of the new OSS landscape, (2) the impact of individuals' personal growth as they become part of OSS communities, and (3) the impact of differences in individuals' demographics. Our results show that some motivations related to social aspects and reputation increased in frequency and that some intrinsic and internalized motivations, such as learning and intellectual stimulation, are still highly relevant. We also found that contributing to OSS often transforms extrinsic motivations to intrinsic, and that while experienced contributors often shift toward altruism, novices often shift toward career, fun, kinship, and learning. OSS projects can leverage our results to revisit current strategies to attract and retain contributors, and researchers and tool builders can better support the design of new studies and tools to engage and support OSS development.
]]></description>
<dc:subject>open-source community-formation project-management motivation cultural-norms online-life collaboration sociology</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:47b4e9445023/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:open-source"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:community-formation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:motivation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cultural-norms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:online-life"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:sociology"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://infodump.ghost.io/how-to-juggle-projects/">
    <title>How To Juggle Projects</title>
    <dc:date>2020-05-02T12:53:21+00:00</dc:date>
    <link>https://infodump.ghost.io/how-to-juggle-projects/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[“What are you working on?” is probably the question writers get asked most in the small-talk section at the beginning of a meeting. If I were to face that question today, the answer would be “Four feature films, two TV shows and a podcast series”. In addition, I’m also always involved with several pitches and some ongoing development conversations. That sounds like a lot, and it looks like a lot when I write it down. And this isn’t about bragging - I didn’t say all of these were paid jobs and certainly there have been plenty of times when NONE of them would have been paid work. This is about managing a workload; although it looks like I must be crazy busy, I rarely feel crazy busy - I still seem to have plenty of time in a day for meetings and for reading, watching stuff, staring into space etc. I always take time out at lunch to watch an episode of something, and I go to the gym (sometimes), go for a walk every day, do the shopping etc.

]]></description>
<dc:subject>project-management writing worklife organization productivity have-read have-done but-also:change-things-regularly</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:868a28d121d4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:writing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:worklife"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:productivity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:have-read"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:have-done"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:but-also:change-things-regularly"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://adrianhoward.com/posts/failure-swapshop/">
    <title>Facilitating Failure Swap Shops — adrianhoward.com</title>
    <dc:date>2020-02-06T23:33:56+00:00</dc:date>
    <link>https://adrianhoward.com/posts/failure-swapshop/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Which in turn reminded me of one of my favourite ways of celebrating learning from failure — Failure Swap Shop!
Luke Williams came up with the format, and I first saw him facilitate a session at BarCamp Bournemouth about ten years ago. I've run it many times since with clients and at events and it's always been informative and fun!
So — what is a Failure Swap Shop?
]]></description>
<dc:subject>teams software-development project-management institutional-learning culture-building morale barcamp</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:6660841ac6c8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:institutional-learning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:culture-building"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:morale"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:barcamp"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://martinfowler.com/articles/workflowsOfRefactoring/">
    <title>Workflows of Refactoring</title>
    <dc:date>2014-11-14T12:22:35+00:00</dc:date>
    <link>http://martinfowler.com/articles/workflowsOfRefactoring/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[In this deck I explore various different workflows. I hope it will encourage teams to integrate refactoring more deeply into their work, resulting in a better designed code-bases that will make it quicker and easier to add new features.
]]></description>
<dc:subject>agile software-development refactoring slide-deck quite-good planning the-nature-of-software-development project-management philosophy-of-engineering</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:d141b5e7ced1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:refactoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:slide-deck"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:quite-good"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:the-nature-of-software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:philosophy-of-engineering"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://unrealnature.wordpress.com/2014/11/11/energy/">
    <title>Energy | Unreal Nature</title>
    <dc:date>2014-11-14T11:32:03+00:00</dc:date>
    <link>http://unrealnature.wordpress.com/2014/11/11/energy/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[… André Masson has been an ambitious painter from the beginning, one who accepts and tries to solve the most difficult problems proposed by art in this age. Very little he has done is without interest; yet little so far seems capable of lasting. There is some lack in Masson of touch or “feel” — a lack dangerous to an artist who relies, or professes to rely, so much on automatism or pure spontaneity. A line either too Spencerian or too splintery weakens his drawings; an insistence upon multiplying and complicating planes, while combining two such color gamuts as violet-blue-green-yellow and brown-mauve-red-orange, renders his painting turgid, overheated, and discordant. Energy is dissipated in all directions.

]]></description>
<dc:subject>criticism project-management painting Clement-Greenberg the-audience-and-the-critic it's-a-fair-cop-but-Modernism-is-to-blame</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:9bab3d1053d7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:criticism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:painting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Clement-Greenberg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:the-audience-and-the-critic"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:it's-a-fair-cop-but-Modernism-is-to-blame"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://code.google.com/p/gerrit/">
    <title>gerrit - Gerrit Code Review - Google Project Hosting</title>
    <dc:date>2014-11-14T11:15:09+00:00</dc:date>
    <link>https://code.google.com/p/gerrit/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Gerrit is a web based code review system, facilitating online code reviews for projects using the Git version control system.

]]></description>
<dc:subject>via:nelson collaboration programming code-review project-management git</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:ff2be33ad142/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:nelson"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:code-review"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:git"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://agileconsulting.blogspot.ca/2012/05/integrating-story-mapping-with-kanban.html">
    <title>Lean Transformation: Integrating Story Mapping with Kanban</title>
    <dc:date>2013-10-24T10:57:25+00:00</dc:date>
    <link>http://agileconsulting.blogspot.ca/2012/05/integrating-story-mapping-with-kanban.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[We have had great experience using story mapping to help teams address the challenges that often find in a typical business requirement document. We have been integrating story mapping with Kanban to enable teams to start thinking in an agile approach from day 1.
]]></description>
<dc:subject>story-mapping kanban lean project-management planning</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:d6a3b0e950b8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:story-mapping"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:kanban"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:lean"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://net.tutsplus.com/tutorials/tools-and-tips/git-tips-from-the-pros/">
    <title>Git Tips From the Pros | Nettuts+</title>
    <dc:date>2013-02-17T13:09:37+00:00</dc:date>
    <link>http://net.tutsplus.com/tutorials/tools-and-tips/git-tips-from-the-pros/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[In this article, we're not going to review the basics of source control management, regardless of which one you use. Let's just assume that you already know how to get around. What we are going to cover is how the pros use git. We'll take a look at some of the advanced features and workflows that you might not already be familiar with. Hopefully, you’ll walk away with your mouth agape at the sheer possibilities that git provides!
]]></description>
<dc:subject>git tutorial advice project-management software-development collaboration</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:f9c694fd1583/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:advice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:collaboration"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mobprogramming.org/">
    <title>Mob Programming</title>
    <dc:date>2012-12-30T13:23:05+00:00</dc:date>
    <link>http://mobprogramming.org/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[We always discuss the things we discover during a retrospective and try to find some action we can take.  In this case, we decided to take some time to mull things over and meet later to discuss how to proceed.  We are flexible – remember: no practice is written in stone. Except for DO RETROSPECTIVES.  That actually IS written in stone.

The basic process we followed for this particular discussion was similar to a “Lean Coffee”.  We all suggested topics and wrote them on post-it notes, prioritized them, and discussed them in prioritized order, taking a few minutes per item, until we had sufficient actionable ideas.  We gathered a list of about 20 ideas on ways we could improve our developer skills, and we talked over about half of them.  Some of the ideas seemed to fit together naturally so we grouped them, and pretty soon we had a few things we decided we’d like to try.   These are what we call “action items”.

]]></description>
<dc:subject>agility agile-management project-management software-development-is-not-programming retrospectives teams</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:17821e4c194d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development-is-not-programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:retrospectives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:teams"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://agilefantasies.wordpress.com/2012/03/25/moral-hazard-the-implacable-enemy-of-agile/">
    <title>Moral Hazard: The Implacable Enemy of Agile « Agile Fantasies</title>
    <dc:date>2012-03-28T12:25:37+00:00</dc:date>
    <link>http://agilefantasies.wordpress.com/2012/03/25/moral-hazard-the-implacable-enemy-of-agile/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["If you adopt economical driving habits, you’ll end up putting less gasoline in your tank.  But if you skip past the economical driving habits and just put less gas in your tank, you’ll end up muttering grim imprecations as you trudge down the highway with a gas can."]]></description>
<dc:subject>agile-practices project-management social-engineering pedagogy management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:ec05250f8f2e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:social-engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:pedagogy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.intercom.io/design-and-premature-optimization/">
    <title>Design and Premature Optimization | The Intercom Blog</title>
    <dc:date>2012-01-20T13:07:10+00:00</dc:date>
    <link>http://blog.intercom.io/design-and-premature-optimization/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Are you wasting development time polishing things that you don’t yet understand? "]]></description>
<dc:subject>agile-practices design premature-optimization project-management self-assessment via:mitten</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:9b840be607b4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:premature-optimization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:self-assessment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:mitten"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://arxiv.org/abs/1112.4323">
    <title>[1112.4323] Between theory and practice: guidelines for an optimization scheme with genetic algorithms - Part I: single-objective continuous global optimization</title>
    <dc:date>2012-01-02T21:52:26+00:00</dc:date>
    <link>http://arxiv.org/abs/1112.4323</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[The rapid advances in the field of optimization methods in many pure and applied science pose the difficulty of keeping track of the developments as well as selecting an appropriate technique that best suits the problem in-hand. From a practitioner point of view is rightful to wander "which optimization method is the best for my problem?". Looking at the optimization process as a "system" of intercon- nected parts, in this paper are collected some ideas about how to tackle an optimization problem using a class of tools from evolutionary computations called Genetic Algorithms. Despite the number of optimization techniques available nowadays the author of this paper thinks that Genetic Algorithms still play a central role for their versatility, robustness, theoretical framework and simplicity of use. The paper can be considered a "collection of tips" (from literature and personal experience) for the non-computer-scientist that has to deal with optimization problems both in the science and engineering practice. No original methods or algorithms are proposed.
]]></description>
<dc:subject>meta-optimization pragmatism-almost genetic-algorithm agile-almost project-management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:a0eb9f6c54ff/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:meta-optimization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:pragmatism-almost"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:genetic-algorithm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-almost"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://cumulative-hypotheses.org/2011/09/16/iterative-incremental-kanban/">
    <title>Iterative, Incremental Kanban « cumulativehypotheses</title>
    <dc:date>2011-09-16T12:15:44+00:00</dc:date>
    <link>http://cumulative-hypotheses.org/2011/09/16/iterative-incremental-kanban/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Iterative development plans to rework items. Not because they are of low quality, not because they are defective, not because they are unacceptable, but because we chose to limit the scope of them earlier so that we can get to learn something about them sooner. This is a product development technique. Kanban is mainly a manufacturing technique. Software development resembles manufacturing to a degree of approximately 0.0 so it’s a bit of a puzzle why this manufacturing technique has become quite so popular with software developers. Added to which the software industry has a catastrophically bad track record at adopting management ideas from manufacturing in an appropriate way. We in IT are perennial confused about manufacturing, product development and engineering, three related but very different kinds of activity."]]></description>
<dc:subject>agile-practices kanban analogies-breaking-down project-management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:ebb170c26e74/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:kanban"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:analogies-breaking-down"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sandofsky.com/blog/git-workflow.html">
    <title>Understanding the Git Workflow</title>
    <dc:date>2011-08-03T14:54:36+00:00</dc:date>
    <link>http://sandofsky.com/blog/git-workflow.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Think of branches in two categories: public and private.

Public branches are the authoritative history of the project. In a public branch, every commit should be succinct, atomic, and have a well documented commit message. It should be as linear as possible. It should be immutable. Public branches include Master and release branches.

A private branch is for yourself. It’s your scratch paper while working out a problem.

It’s safest to keep private branches local. If you do need to push one, maybe to synchronize your work and home computers, tell your teammates that the branch you pushed is private so they don’t base work off of it."]]></description>
<dc:subject>git project-management distributed-work version-control advice design-patterns</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:1e0dba597771/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:distributed-work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:version-control"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:advice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design-patterns"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://stackoverflow.com/questions/930612/git-remove-oldest-revisions-of-a-file/931054#931054">
    <title>git remove oldest revisions of a file - Stack Overflow</title>
    <dc:date>2011-06-30T22:40:53+00:00</dc:date>
    <link>http://stackoverflow.com/questions/930612/git-remove-oldest-revisions-of-a-file/931054#931054</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Now, I don't think there is a way to directly tell git-filter-branch to skip any commits. However, since the commands are run in a shell context, it shouldn't be too difficult to use the shell to remove all but the last X number of revisions. Something like this:…"]]></description>
<dc:subject>git version-control hints project-management fundamentalism-be-damned</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:28f6dc9625c1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:version-control"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:hints"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:fundamentalism-be-damned"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://xprogramming.com/articles/kate-oneal-and-the-mythical-italian-restaurant/">
    <title>Kate Oneal and the Mythical Italian Restaurant | xProgramming.com</title>
    <dc:date>2011-06-10T15:01:23+00:00</dc:date>
    <link>http://xprogramming.com/articles/kate-oneal-and-the-mythical-italian-restaurant/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA['“The artist suggested this: ‘Let’s set a deadline and total budget. I’ll keep you posted on how much is being spent, and of course we’ll have the picture on the wall to look at. By the time we’re about half-way through, it should be of high enough quality, and have enough picture elements, that we could stop any time. You’ll have more ideas, of course, but by then we’ll both have a sense of how fast we can progress, and you can choose the most valuable things to add or change. You’ll have total control over how the picture winds up, and if you want to, we can stop on or before the money runs out.’

“Guido wasn’t entirely convinced. He wanted to know how he could be sure he wouldn’t be left with a horribly ugly wall. The artist told him that she would guarantee to paint it back over and stop any time he wanted, and said she would start by working in some temporary pigment like chalk, so they could erase and change things easily.']]></description>
<dc:subject>project-management metaphor agile-management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:c52ed72af596/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:metaphor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.agileproductdesign.com/blog/the_new_backlog.html">
    <title>The new user story backlog is a map</title>
    <dc:date>2011-05-28T14:03:51+00:00</dc:date>
    <link>http://www.agileproductdesign.com/blog/the_new_backlog.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["I find that the big things on the top of the story map look a little like vertebrae. And the cards hanging down look a little like ribs. Those big things on the top are often the essential capabilities the system needs to have. I refer to them as the "backbone" of the software. I stole this term from Dr. Dan Rawsthorne who might use the term slightly differently than I do.



When it comes time to prioritize stories, I don't prioritize the backbone. It just "is." I do prioritize the ribs - the stories hanging down from the backbone. Place them high to indicate they're absolutely necessary, lower to indicate they're less necessary. When you do this, you'll find that all the stories placed high on the story map describe the smallest possible system you could build that would give you end to end functionality. This is what Alistair Cockburn refers to as the "walking skeleton". I always try to build this first."]]></description>
<dc:subject>planning agile-practices card-sorting project-management techniques</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:ea7366a9157f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:card-sorting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:techniques"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://agilistry.com/events/agile-management/">
    <title>Agilistry Studio - Agile Management</title>
    <dc:date>2011-05-20T11:59:08+00:00</dc:date>
    <link>http://agilistry.com/events/agile-management/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Several studies indicate that “old-style” managers are the 
biggest obstacle in transitions to Agile software development. 
Development managers and team leaders need to learn what their new role is in Agile software development organizations. This course will help them."]]></description>
<dc:subject>management agile-management project-management class Jurgen-Appelo</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:557ed6ac1c12/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:class"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Jurgen-Appelo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://getmentalnotes.com/">
    <title>Get Mental Notes</title>
    <dc:date>2011-05-12T12:09:53+00:00</dc:date>
    <link>http://getmentalnotes.com/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["In the midst of a busy project it's all too easy to forget the nuances that distinguish great products. Mental Notes brings together 50 insights from psychology into an easy reference and brainstorming tool. Each card describes one insight into human behavior and suggests ways to apply this to the design of Web sites, Web apps, and software applications."]]></description>
<dc:subject>inspiration habit cards web-design project-management via:mitten</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Vaguery/b:c7001ef6abb1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:inspiration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:habit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:web-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:mitten"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.wilshipley.com/2011/04/success-and-farming-vs-mining.html">
    <title>Call Me Fishmeal.: Success, and Farming vs. Mining</title>
    <dc:date>2011-04-17T14:31:30+00:00</dc:date>
    <link>http://blog.wilshipley.com/2011/04/success-and-farming-vs-mining.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["The idea part is cheap. Try to think of an idea that’s actually worth something on its own. “I wish I’d thought up the web browser.” Bullshit. The web browser had been thought up at least twenty years before those high-energy frogs coded one up on NeXTstep (c.f. Dynabook, 1968). It was the actual shipping product they wrote that caused the internet revolution, not the idea."]]></description>
<dc:subject>entrepreneurship entrepreneurship-as-pathology cultural-assumptions business-culture capital_types-of project-management sustainability</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:f4b3bc033f93/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:entrepreneurship"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:entrepreneurship-as-pathology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cultural-assumptions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:business-culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:capital_types-of"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:sustainability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dashes.com/anil/2010/09/forking-is-a-feature.html">
    <title>Forking is a Feature</title>
    <dc:date>2010-09-25T12:12:37+00:00</dc:date>
    <link>http://dashes.com/anil/2010/09/forking-is-a-feature.html</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>via:nelson project-management software-development cultural-norms software-development-is-not-programming git GitHub</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:2150803296c4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:nelson"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cultural-norms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development-is-not-programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:GitHub"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://elearning.industriallogic.com/gh/submit?Action=PageAction&amp;album=blog2009&amp;path=blog2009/2010/redefiningDone&amp;devLanguage=Java">
    <title>2010 BLogic: Redefining Done</title>
    <dc:date>2010-08-02T13:20:53+00:00</dc:date>
    <link>https://elearning.industriallogic.com/gh/submit?Action=PageAction&amp;album=blog2009&amp;path=blog2009/2010/redefiningDone&amp;devLanguage=Java</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["A story isn't done until it is being used by real users in production and has been validated to be a useful part of a product."
]]></description>
<dc:subject>agility lean agile-practices project-management progress</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:8399bed254de/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:lean"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:progress"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cs.brown.edu/people/acb/codebubbles_site.htm">
    <title>Code Bubbles Project: Rethinking the User Interface Paradigm of Integrated Development Environments</title>
    <dc:date>2010-05-16T12:03:33+00:00</dc:date>
    <link>http://www.cs.brown.edu/people/acb/codebubbles_site.htm</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[I want this for Ruby, and not in Eclipse.
]]></description>
<dc:subject>software-development user-interaction user-interface project-management visualization GUI coding</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:788824ac49ef/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:user-interaction"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:user-interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:GUI"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:coding"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://i-dont-trust-your-code.heroku.com/">
    <title>Presentation</title>
    <dc:date>2010-05-16T11:07:10+00:00</dc:date>
    <link>http://i-dont-trust-your-code.heroku.com/</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>rubygem software-development cultural-norms version-control installation library-structure project-management etiquette</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:cd625d9963da/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:rubygem"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cultural-norms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:version-control"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:installation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:library-structure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:etiquette"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/p/gource/">
    <title>gource - Project Hosting on Google Code</title>
    <dc:date>2010-05-14T15:02:26+00:00</dc:date>
    <link>http://code.google.com/p/gource/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Software projects are displayed by Gource as an animated tree with the root directory of the project at its centre. Directories appear as branches with files as leaves. Developers can be seen working on the tree at the times they contributed to the project."
]]></description>
<dc:subject>software-development project-management open-source visualization want</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:2c2dc00df1f3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:open-source"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:want"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://xprogramming.com/articles/quality/">
    <title>Quality vs Speed? I Don’t Think So! | xProgramming.com</title>
    <dc:date>2010-05-01T15:11:05+00:00</dc:date>
    <link>http://xprogramming.com/articles/quality/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Is it possible that if we keep our focus on longer term sustainability, we can still go just as fast in the short term? I believe that it is possible, and that we already have credible evidence that it is possible.

Most of us believe that over the longer term, speed is maximized by operating at a high, but not stupidly high, level of quality. The question is, what is “longer term”?"
]]></description>
<dc:subject>agility project-management planning quality speech software-development-is-not-programming</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:2339d253f7b2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:quality"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:speech"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development-is-not-programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://unethicalblogger.com/posts/2010/04/rebasebased_workflow">
    <title>A rebase-based workflow | unethical blogger</title>
    <dc:date>2010-04-05T18:59:54+00:00</dc:date>
    <link>http://unethicalblogger.com/posts/2010/04/rebasebased_workflow</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Creating concise commits is probably the most important reason to use rebase, when working in a topic branch I will typically commit every 20-40 minutes. In order to not break my flow, the commit messages will typically be brief and cover only a few lines of changes, atomic commits are great when writing code but they're lousy at informing other developers about the changes.…"
]]></description>
<dc:subject>git project-management distributed-teams open-source version-control workflow</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:addec8afc170/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:distributed-teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:open-source"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:version-control"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:workflow"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.itskeptic.org/shit-happens-or-how-i-learned-love-incident">
    <title>Shit happens, or how I learned to love the incident | The IT Skeptic</title>
    <dc:date>2010-03-09T16:03:13+00:00</dc:date>
    <link>http://www.itskeptic.org/shit-happens-or-how-i-learned-love-incident</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["This seems a reversal of some things I have said in the past about the need for change control. I said that "shit happens" is not an excuse any more. I still believe that. Just because some incidents will remain unpreventable doesn't mean that many others can't be prevented. Just because fixing a problem in one place means higher risks will be taken elsewhere doesn't mean we shouldn't fix the problems. And just because complex systems are impossible to stop breaking doesn't mean that there isn't negligence behind some breakages."
]]></description>
<dc:subject>project-management management risk-management cultural-assumptions engineering complex-systems failure</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:1dbcedc43474/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:risk-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cultural-assumptions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:complex-systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:failure"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://github.com/guides/completely-remove-a-file-from-all-revisions">
    <title>Completely remove a file from all revisions - Guides - GitHub</title>
    <dc:date>2010-03-04T11:56:09+00:00</dc:date>
    <link>http://github.com/guides/completely-remove-a-file-from-all-revisions</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Don’t you hate when you can’t remove that file full of cleartext passwords from your github account? Even if you git rm it, it still is accessible in previous versions of the tree. So, you need to rewrite the entire tree. Fortunately, this is really easy with git."
]]></description>
<dc:subject>GitHub protip project-management security how-to version-control woops</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:bffc94df932b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:GitHub"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:protip"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:how-to"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:version-control"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:woops"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://catenary.wordpress.com/2009/11/29/against-semat/">
    <title>Against SEMAT « Catenary</title>
    <dc:date>2010-02-25T14:43:08+00:00</dc:date>
    <link>http://catenary.wordpress.com/2009/11/29/against-semat/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["The rest of the items in SEMAT’s proposal are mush. Of course our theories need to address technological and social issues. Of course they need wide support by several communities to be successful. Of course they must be flexible. But what should they consist of? What stake is SEMAT putting on the ground? Unfortunately, beyond a wish to be more like an engineering discipline, this proposal is completely vague, and therefore I cannot support it."
]]></description>
<dc:subject>engineering-philosophy engineering-design cultural-assumptions bad-philosophy agility project-management theory-and-practice-sitting-in-a-tree</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:6d869b3e31d9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:engineering-philosophy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:engineering-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cultural-assumptions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:bad-philosophy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:theory-and-practice-sitting-in-a-tree"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://japhr.blogspot.com/2010/02/retrospective-week-one.html">
    <title>japh(r): Retrospective: Week One</title>
    <dc:date>2010-02-19T19:28:37+00:00</dc:date>
    <link>http://japhr.blogspot.com/2010/02/retrospective-week-one.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Simply put, you will not improve unless you strive to get better. You will not improve unless you:
look back on what you accomplished
reflect on what prevented you from doing even better
try to apply lessons learned the next time around
It almost seems so obvious that it's not worth the 15 minutes that it takes your team. But, as anyone that has ever practiced regular retrospectives knows, they are an invaluable tool for identifying group problems that might have otherwise gone unnoticed."
]]></description>
<dc:subject>retrospectives agile-management agility agile-practices project-management self-organization</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:4a93852224b6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:retrospectives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:self-organization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://zenhabits.net/2010/02/completion-principles/">
    <title>4 Simple Principles of Getting to Completion | Zen Habits</title>
    <dc:date>2010-02-19T14:15:54+00:00</dc:date>
    <link>http://zenhabits.net/2010/02/completion-principles/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["1. Keep the scope as simple as possible.… 2. Practice ‘Good Enough’.… 3. Kill extra features.… 4. Make it public, quick."
]]></description>
<dc:subject>project-management planning advice software-development openness productivity simplicity</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:ae950143351d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:advice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:openness"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:productivity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:simplicity"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://theagileexecutive.com/2010/02/19/the-agile-flywheel/">
    <title>The Agile Flywheel « The Agile Executive</title>
    <dc:date>2010-02-19T14:09:07+00:00</dc:date>
    <link>http://theagileexecutive.com/2010/02/19/the-agile-flywheel/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Scrum set the flywheel in motion and caused the rest of the IT process life cycle to respond.  ITIL’s processes still form the solid core of service support and we’ve improved the processes’ capability to handle intense work velocity. The organization adapted by developing unprecedented speed in the ability to deliver production fixes and to solve root cause problems with agility."
]]></description>
<dc:subject>agility project-management business-culture disintermediation-in-action innovation communities-of-practice management</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:bd5ab949c567/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:business-culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:disintermediation-in-action"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:innovation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:communities-of-practice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tgethr.com/welcome/tour">
    <title>Feature Tour: tgethr</title>
    <dc:date>2010-01-24T14:12:28+00:00</dc:date>
    <link>http://tgethr.com/welcome/tour</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Email is still the easiest way to collaborate with a group of people.
We built tgethr in response to the increasingly complex world of online collaboration. Why set up a project management site or an entire social network when all you need is to correspond by email more efficiently?"
]]></description>
<dc:subject>maybe collaboration teams project-management infrastructure distributed-teams</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:1fc7935ba565/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:maybe"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:distributed-teams"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://pivotallabs.com/users/dan/blog/articles/1135-pivotal-tracker-api-new-version-v3-to-be-released-on-jan-23">
    <title>Dan's Blog - Pivotal Tracker API - new version (V3) to be released on Jan. 23</title>
    <dc:date>2010-01-24T00:44:10+00:00</dc:date>
    <link>http://pivotallabs.com/users/dan/blog/articles/1135-pivotal-tracker-api-new-version-v3-to-be-released-on-jan-23</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["We're planning a Pivotal Tracker upgrade on Jan 23. As part of this release, we will be introducing a new API version (V3), which will make it easier to follow project activity, allow you to add file attachments, move (re-prioritize) stories, associate source commits with stories, and more."
]]></description>
<dc:subject>API Pivotal-Tracker project-management tools software-development agility agile-management</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:6a1ca625cf76/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:API"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Pivotal-Tracker"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.gcbl.org/blog/marc-lefkowitz/city-planning-throws-weight-behind-open-access-innerbelt-bridge">
    <title>City Planning throws weight behind open access for Innerbelt Bridge | GreenCityBlueLake</title>
    <dc:date>2010-01-23T20:51:13+00:00</dc:date>
    <link>http://www.gcbl.org/blog/marc-lefkowitz/city-planning-throws-weight-behind-open-access-innerbelt-bridge</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["The Commission’s resolution also included a call for ODOT to attend their next meeting on February 2 (9 am at City Hall) to discuss the benefits of a bike/ped path included in the bid process. ODOT will release the RFQ that same day, so Brown pointed out that the resolution and alternative technical specification in the RFQ will have to be sent to ODOT this week. ODOT will host a meeting for parties interested in designing the Innerbelt Bridge on Feb. 9. Kuri asked if this was a public meeting (and offered after that a group of advocates might consider forming as a design ‘firm’ to bid on the project – for at least the purpose of attending the Feb. 9 meeting. The guidlines for bidding on the Innerbelt Bridge can be found here.)"
]]></description>
<dc:subject>city-planning collaboration openness government2.0 public-policy engineering-design funding project-management</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:2678fe1d0f87/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:city-planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:openness"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:government2.0"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:public-policy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:engineering-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:funding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nvie.com/archives/323">
    <title>nvie.com » Blog Archive » A successful Git branching model</title>
    <dc:date>2010-01-21T14:54:45+00:00</dc:date>
    <link>http://nvie.com/archives/323</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["In this post I present the development model that I’ve introduced for all of my projects (both at work and private) about a year ago, and which has turned out to be very successful. I’ve been meaning to write about it for a while now, but I’ve never really found the time to do so thoroughly, until now. I won’t talk about any of the projects’ details, merely about the branching strategy and release management."
]]></description>
<dc:subject>git version-control project-management programming software-development tutorial control strategy workflow branching dvcs</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:ede29257bf8c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:version-control"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:control"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:strategy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:workflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:branching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:dvcs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.mountaingoatsoftware.com/build-trust-between-teams-with-ambassadors">
    <title>Build Trust Between Teams with Ambassadors | Mike Cohn's Blog - Succeeding With Agile®</title>
    <dc:date>2009-12-29T13:33:45+00:00</dc:date>
    <link>http://blog.mountaingoatsoftware.com/build-trust-between-teams-with-ambassadors</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["On a distributed Scrum project, individual team members need to meet each other face to face. If the whole team cannot get together, one or two members from each team, at least, should spend time visiting team members in other cities. Think of them as ambassadors. I’ve found that the personal relationships established by ambassadors can be extremely valuable even long after the ambassador returns to native soil."
]]></description>
<dc:subject>distributed-teams Scrum agile-management project-management social-engineering social-dynamics good-ideas</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:d192ef633bd7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:distributed-teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:social-engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:social-dynamics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:good-ideas"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gojko.net/2009/12/04/eight-interesting-techniques-to-test-how-a-project-is-going/">
    <title>Gojko Adzic » Eight interesting techniques to test how a project is going</title>
    <dc:date>2009-12-06T12:50:54+00:00</dc:date>
    <link>http://gojko.net/2009/12/04/eight-interesting-techniques-to-test-how-a-project-is-going/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Pick up a document, turn it over and see what’s on the back. If you find diagrams, that suggest the need for clarity as people were drawing on it to explain things."
]]></description>
<dc:subject>complexity project-management social-engineering agility agile-management rules-of-thumb metrics XP</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:7a046319e3de/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:complexity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:social-engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:rules-of-thumb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:metrics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:XP"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.slideshare.net/ourfounder/personal-kanban-101">
    <title>Personal Kanban 101</title>
    <dc:date>2009-11-19T12:23:27+00:00</dc:date>
    <link>http://www.slideshare.net/ourfounder/personal-kanban-101</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["How to create your first Personal Kanban and visualize your work."
]]></description>
<dc:subject>project-management productivity simplicity work-in-progress kanban focus</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:b06f425a0bb2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:productivity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:simplicity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:work-in-progress"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:kanban"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:focus"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://pivotallabs.com/users/ian/blog/articles/1010-explaining-the-value-of-agile-rails-and-the-cloud">
    <title>onChange - Explaining the Value of Agile, Rails and the Cloud</title>
    <dc:date>2009-11-02T22:27:09+00:00</dc:date>
    <link>http://pivotallabs.com/users/ian/blog/articles/1010-explaining-the-value-of-agile-rails-and-the-cloud</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["The question should not be, “is Rails a safe choice,” but “[how long] can we justify the expense of traditional development approaches.”"
]]></description>
<dc:subject>Rails cloud-computing Ruby RoR economics project-management business-practice</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:1068eeecdb30/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cloud-computing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:RoR"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:economics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:business-practice"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://codeintensity.blogspot.com/2008/12/github-post-receive-hook-for-pivotal.html">
    <title>Code Intensity: GitHub Post-Receive Hook for Pivotal Tracker</title>
    <dc:date>2009-09-16T23:12:29+00:00</dc:date>
    <link>http://codeintensity.blogspot.com/2008/12/github-post-receive-hook-for-pivotal.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["The service supports multiple GitHub repos and Tracker projects, so you can run a single service that integrates multiple projects. The service will figure out which commits go to which projects based on a config file on the server that associates a GitHub repo URL (make sure to use the http version of the URL, not https), to a Tracker project ID. For example:"
]]></description>
<dc:subject>GitHub Pivotal-Tracker tools agile-management software-development project-management</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:8a2dd927d5ae/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:GitHub"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Pivotal-Tracker"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://github.com/tpope/pickler">
    <title>tpope's pickler at master - GitHub</title>
    <dc:date>2009-09-16T22:54:36+00:00</dc:date>
    <link>http://github.com/tpope/pickler</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Synchronize user stories in Pivotal Tracker with Cucumber features."
]]></description>
<dc:subject>Cucumber Pivotal-Tracker BDD collaboration Ruby agile project-management tools</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:4fa7fea2b601/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Cucumber"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Pivotal-Tracker"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:BDD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://thedailywtf.com/Articles/Classic-WTF-The-Cool-Cam.aspx">
    <title>Classic WTF: The Cool Cam - The Daily WTF</title>
    <dc:date>2009-09-08T10:53:29+00:00</dc:date>
    <link>http://thedailywtf.com/Articles/Classic-WTF-The-Cool-Cam.aspx</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Tim's "cool cam" saved European Air War. It went from a money-leaking embarrassment to a top-tier release for MicroProse. The weekly meetings got easier, more developers were brought on, and the team managed to put together one hell of a game. It reviewed well after its 1998 release and is still a popular game for history buffs. And it probably wouldn't have been released if not for a programmer that knew what the project needed most; the cool cam."
]]></description>
<dc:subject>marketing project-management portfolio-theory management programming games</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:fa779048bd4c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:marketing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:portfolio-theory"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:games"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.crisp.se/henrikkniberg/2009/06/26/1246053060000.html">
    <title>One day in Kanban land - Henrik Kniberg's blog</title>
    <dc:date>2009-07-01T11:49:00+00:00</dc:date>
    <link>http://blog.crisp.se/henrikkniberg/2009/06/26/1246053060000.html</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>project-management agility kanban Scrum agile lean</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:9e858f5222e2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:kanban"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:lean"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://github.com/scrumalliance">
    <title>scrumalliance's Profile - GitHub</title>
    <dc:date>2009-05-28T11:07:09+00:00</dc:date>
    <link>http://github.com/scrumalliance</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Redmine plugins for making the platform more project-appropriate.
]]></description>
<dc:subject>Redmine project-management plugin burndown agility tools</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:7bd8a0946631/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Redmine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:plugin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:burndown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bucketworks.org/concepts">
    <title>Concepts at Bucketworks | Bucketworks</title>
    <dc:date>2009-04-20T19:37:48+00:00</dc:date>
    <link>http://bucketworks.org/concepts</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Working in an collaborative environment that simultaneously supports business, technology, creativity, and performance give rise to new concepts. Below we list of some of the ideas we use in our work--terms you may hear or things you may experience if you become a member and spend some time in this unique environment."
]]></description>
<dc:subject>ideas workantile physical-wiki design-patterns community business-model cultural-engineering worklife project-management wikinomics</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:6889cb59a9d6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:ideas"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:workantile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:physical-wiki"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design-patterns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:business-model"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cultural-engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:worklife"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:wikinomics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.pivotaltracker.com/learnmore">
    <title>Pivotal Tracker - Why Use Pivotal Tracker?</title>
    <dc:date>2009-04-13T10:42:54+00:00</dc:date>
    <link>https://www.pivotaltracker.com/learnmore</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Tracker is a simple, story-based project planning tool that allows teams to collaborate and instantly react to real-world changes. It's based on agile software development methods, but it can be used on a variety of types of projects. Tracker frees you up to focus on getting things done, without getting bogged down keeping your plans in sync with reality."
]]></description>
<dc:subject>agile project-management planning coordination tools Scrum iterative-work project-driven-lifestyle</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:05b7229bf11e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:coordination"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:iterative-work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-driven-lifestyle"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.randsinrepose.com/archives/2009/03/23/the_makers_of_things.html">
    <title>Rands In Repose: The Makers of Things</title>
    <dc:date>2009-03-24T15:06:00+00:00</dc:date>
    <link>http://www.randsinrepose.com/archives/2009/03/23/the_makers_of_things.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["We are defined by what we build. It’s not just the engineering ambition that designed these structures, nor the 20 people who died building the Brooklyn Bridge. It’s that we believe we can and decide to act. I’m happy to report our new President agrees when he says,

“In reaffirming the greatness of our nation, we understand that greatness is never a given. It must be earned. Our journey has never been one of shortcuts or settling for less. It has not been the path for the faint-hearted — for those who prefer leisure over work, or seek only the pleasures of riches and fame. Rather, it has been the risk-takers, the doers, the makers of things — some celebrated but more often men and women obscure in their labor, who have carried us up the long, rugged path towards prosperity and freedom.”"
]]></description>
<dc:subject>via:deusx engineering engineering-design project-management planning futurism aspiration inspiration history innovation management optimism</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:56236e8d1348/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:deusx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:engineering-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:futurism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:aspiration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:inspiration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:innovation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:optimism"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.exampler.com/blog/2008/05/21/everyone-needs-a-cryptic-slogan/">
    <title>Exploration Through Example » Blog Archive » Everyone needs a cryptic slogan</title>
    <dc:date>2009-02-25T01:51:59+00:00</dc:date>
    <link>http://www.exampler.com/blog/2008/05/21/everyone-needs-a-cryptic-slogan/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Retro-Futurist Micro-Scale Anarcho-Syndicalism"
]]></description>
<dc:subject>agile post-agile teams project-management</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:4f7a7b266403/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:post-agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nomachetejuggling.com/2008/12/11/my-least-favorite-interview-question/">
    <title>My Least Favorite Interview Question » Absolutely No Machete Juggling</title>
    <dc:date>2009-02-24T23:08:35+00:00</dc:date>
    <link>http://www.nomachetejuggling.com/2008/12/11/my-least-favorite-interview-question/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["I have no idea what the interviewer’s expectations are, so I have to guess. I have, essentially, a 50/50 shot at guessing correctly. To make matters worse, my answer will likely go through a number of different interviewers, and I have a 50/50 shot at having guessed correctly with each of them. Assuming that a single “no” from one of the interviewers means I don’t get a job offer, having 2 interviewers gives me a 25% chance of success. Three interviewers gives me a 12.5% chance. A team of 6 or 7 interviewers (extremely common in up-and-coming companies) gives me virtually no chance at all."
]]></description>
<dc:subject>Nudge programming interview hiring specification assumptions project-management business-culture</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:2962542e9d13/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Nudge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:interview"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:hiring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:specification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:assumptions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:business-culture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://cavlec.yarinareth.net/2009/02/19/humanists-and-the-digital/">
    <title>Caveat Lector » Blog Archive » Humanists and the digital</title>
    <dc:date>2009-02-22T13:08:29+00:00</dc:date>
    <link>http://cavlec.yarinareth.net/2009/02/19/humanists-and-the-digital/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Another common thread in the grad students’ stories was dissuasion, both passive and active, from engagement with the digital. From bureaucratic hassles to tepid advising to being actually barred from computing facilities built for faculty (think about that for a moment; it’s appalling on so very many levels), the message goes out loud and clear: technology is a toy, it’s a diversion, it’s fine for the classroom, but it’s not how you do your work."
]]></description>
<dc:subject>academia pecking-order academic-culture humanities worklife project-management disintermediation-targets</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:e1c54a2d5c15/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:academia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:pecking-order"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:academic-culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:humanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:worklife"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:disintermediation-targets"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.michaelnygard.com/blog/2009/02/fast_iteration_versus_elegant.html">
    <title>Wide Awake Developers: Fast Iteration versus Elegant Design</title>
    <dc:date>2009-02-22T12:55:37+00:00</dc:date>
    <link>http://www.michaelnygard.com/blog/2009/02/fast_iteration_versus_elegant.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["So why is Linux everywhere, and we only hear about 386BSD in historical contexts? There is exactly one answer, and it's what Eric Raymond was really talking about in The Cathedral and the Bazaar. TCatB has been seen mostly as an argument for open-source versus commercial software, but what Raymond saw was that the real competition comes down to an open contribution model versus closed contributions. Linus' promiscuous contribution policy simply let Linux out-evolve 386BSD. More contributors meant more drivers, more bug fixes, more enhancements... more ideas, ultimately. Two people, no matter how talented, cannot outcode thousands of Linux contributors. The best programmers are 10 times more productive than the average, and I would rate Bill and Lynne among the very best. But, as of last April, the Linux Foundation reported that more than 3,600 people had contributed to the kernel alone."
]]></description>
<dc:subject>agility competitiveness project-management planning collaboration</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:ba6e51db17e4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:competitiveness"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:collaboration"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.objectmentor.com/articles/2009/02/17/the-bloat-at-the-edge-of-duplication-removal-the-orange-model">
    <title>The Bloat at the Edge of Duplication Removal (The Orange Model)</title>
    <dc:date>2009-02-21T18:30:22+00:00</dc:date>
    <link>http://blog.objectmentor.com/articles/2009/02/17/the-bloat-at-the-edge-of-duplication-removal-the-orange-model</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Here’s what duplication removal does, structurally. It allows you to pull out redundant bits of pulp from big sections, yielding smaller sections, but the side effect is that you end up with more fascia. Duplication removal increases the ratio of fascia to pulp. If the amount of pulp you are able to remove exceeds the size of the fascia you introduce, the net amount of code decreases, otherwise it might increase.

In general, I think that a high fascia to pulp ratio is better for maintenance. It gives us is a higher surface area to volume ratio for our code. This can enhance testability and make it easier to compose new software – we already have smaller more understandable pieces."
]]></description>
<dc:subject>project-management design emergent-design agility refactoring programming software-development</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:e85a349107ed/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:emergent-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:refactoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software-development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.codinghorror.com/blog/archives/001226.html">
    <title>Coding Horror: Are You An Expert?</title>
    <dc:date>2009-02-21T12:56:34+00:00</dc:date>
    <link>http://www.codinghorror.com/blog/archives/001226.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[[indirect but key]
"Practice, practice, practice!
Don't confuse experience with expertise.
Don't trust folklore -- but learn it anyway.
Take nothing on faith. Own your methodology.
Drive your own education -- no one else will.
Reputation = Money. Build and protect your reputation.
Relentlessly gather resources, materials, and tools.
Establish your standards and ethics.
Avoid certifications that trivialize the craft.
Associate with demanding colleagues.
Write, speak, and always tell the truth as you see it."
]]></description>
<dc:subject>expertise learning-by-doing teams project-management social-norms assumptions skepticism self-image pragmatism</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:effef8809829/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:expertise"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:learning-by-doing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:social-norms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:assumptions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:skepticism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:self-image"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:pragmatism"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.codinghorror.com/blog/archives/001227.html">
    <title>Coding Horror: The Bad Apple: Group Poison</title>
    <dc:date>2009-02-21T12:05:43+00:00</dc:date>
    <link>http://www.codinghorror.com/blog/archives/001227.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["The Depressive Pessimist will complain that the task that they're doing isn't enjoyable, and make statements doubting the group's ability to succeed.

The Jerk will say that other people's ideas are not adequate, but will offer no alternatives himself. He'll say "you guys need to listen to the expert: me."

The Slacker will say "whatever", and "I really don't care."
]]></description>
<dc:subject>via:nielsen group-dynamics management TEAM: inagility project-management diagnosis</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:babc6fed2edd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:nielsen"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:group-dynamics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:TEAM:"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:inagility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:diagnosis"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.alistapart.com/articles/gettingrealaboutagiledesign">
    <title>A List Apart: Articles: Getting Real About Agile Design</title>
    <dc:date>2009-01-04T23:25:35+00:00</dc:date>
    <link>http://www.alistapart.com/articles/gettingrealaboutagiledesign</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[/replace "design" with "science"/ as well

"Fortunately, we can learn from other fields. Filmmakers operate in a similarly agile fashion, filming scenes in an order dictated purely by logistics. To ensure vision, coherence, and narrative continuity they employ specialists: directors and script supervisors. On the web, designers can play a similar role, but must volunteer and adapt it for themselves. This means getting involved in writing user stories and trying to guide product owners away from over-hasty solutions."
]]></description>
<dc:subject>design agility cultural-norms project-management development management productivity methodologies</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:5ec214e535d2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cultural-norms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:productivity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:methodologies"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kiloblog.com/post/sharing-code-for-what-its-worth/">
    <title>Alan’s Kiloblog » GitHub and Git: Sharing Your Code, for What It’s Worth, Without a Begging Entry into Open Source Communities</title>
    <dc:date>2008-11-27T12:59:22+00:00</dc:date>
    <link>http://kiloblog.com/post/sharing-code-for-what-its-worth/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["With these people, there is nothing more offensive than the fork. You are going to split the community, take away committers. It is heresy. It is a schism.

The nature of open source on the SourceForge model is academia at it’s most petty, because the stakes could not be lower. It is not about the source code, it is about the source code repository and control to access thereof.

GitHub puts an end to this nonsense. I can develop my software and I can use GitHub to publish my software. I don’t have to work within an arbitrary community, but grow support for my software through my own social and professional network."
]]></description>
<dc:subject>open-source collaboration control cultural-norms software practice project-management sensibility Mercurial GitHub</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:fefd41a6e787/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:open-source"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:control"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:cultural-norms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:practice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:sensibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Mercurial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:GitHub"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.xprogramming.com/xpmag/whatisxp.htm">
    <title>What is Extreme Programming?</title>
    <dc:date>2008-01-24T01:38:13+00:00</dc:date>
    <link>http://www.xprogramming.com/xpmag/whatisxp.htm</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>XP extreme-programming practices methodologies definition article development essay process project-management Ron-Jeffries</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:084f6340796d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:XP"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:extreme-programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:methodologies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:definition"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:article"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:essay"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:process"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ron-Jeffries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.redmine.org/">
    <title>Redmine - Overview - Redmine</title>
    <dc:date>2008-01-03T12:22:08+00:00</dc:date>
    <link>http://www.redmine.org/</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>via:bkerr organization agile collaboration project-management development freeware management open-source planning svn Rails RoR Ruby software wiki tools</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:1638cb92b121/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:bkerr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:freeware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:open-source"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:svn"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:RoR"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:wiki"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://culturedcode.com/things/">
    <title>Things : Cultured Code</title>
    <dc:date>2007-11-21T12:22:24+00:00</dc:date>
    <link>http://culturedcode.com/things/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[PUBIC BETA
]]></description>
<dc:subject>via:deusx GTD getting-things-done project-management time-management todo lists applications productivity MacOS Leopard</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:f24a7feb56d4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:deusx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:GTD"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:getting-things-done"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:time-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:todo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:lists"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:applications"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:productivity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:MacOS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:Leopard"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://areyouexpendable.com/a/">
    <title>Are YOU Expendable?</title>
    <dc:date>2007-10-30T11:34:02+00:00</dc:date>
    <link>http://areyouexpendable.com/a/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Strength. Sacrifice. Strongness."
]]></description>
<dc:subject>via:logista worklife business-plan business-culture mad-science planning project-management movie</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:669798d5cd64/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:via:logista"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:worklife"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:business-plan"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:business-culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:mad-science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:movie"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://cns2.uni.edu/~wallingf/blog/archives/monthly/2007-10.html#e2007-10-10T19_10_57.htm">
    <title>Knowing and Doing: October 2007 Archives</title>
    <dc:date>2007-10-21T15:11:23+00:00</dc:date>
    <link>http://cns2.uni.edu/~wallingf/blog/archives/monthly/2007-10.html#e2007-10-10T19_10_57.htm</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>agility agile-management problem-solving design pedagogy project-management structure</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:b42e0340d075/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:problem-solving"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:pedagogy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:structure"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.stateofflow.com/journal/51/estimation-xperiment">
    <title>State of Flow: Estimation XPeriment::journal</title>
    <dc:date>2007-09-17T12:37:57+00:00</dc:date>
    <link>http://www.stateofflow.com/journal/51/estimation-xperiment</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>agility agile-management planning project-management extreme-programming XP decision-making business-plan decision-support</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:d7dfba1f4844/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agile-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:extreme-programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:XP"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:decision-making"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:business-plan"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:decision-support"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.owellprecast.com/15.html">
    <title>Owell Precast - Hollow Core</title>
    <dc:date>2007-08-12T11:39:19+00:00</dc:date>
    <link>http://www.owellprecast.com/15.html</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>concrete construction residential design architecture planning project-management contractor</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:cdc0b6c154f1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:concrete"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:construction"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:residential"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:contractor"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://metacool.typepad.com/metacool/2007/07/more-garage-maj.html">
    <title>metacool: More Garage Majal...</title>
    <dc:date>2007-07-08T19:58:51+00:00</dc:date>
    <link>http://metacool.typepad.com/metacool/2007/07/more-garage-maj.html</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA["Successful open source projects combine meritocratic leadership, "doing" more than "talking", and breadth..."
]]></description>
<dc:subject>openness institutional-design management project-management open-source networks social-norms knowledge</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:538aea0126ac/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:openness"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:institutional-design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:open-source"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:networks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:social-norms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:knowledge"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.dhemery.com/cwd/2003/08/estimates_are_not_commitments.html">
    <title>Dale H. Emery - Conversations with Dale - Estimates Are Not Commitments</title>
    <dc:date>2007-06-17T12:42:51+00:00</dc:date>
    <link>http://www.dhemery.com/cwd/2003/08/estimates_are_not_commitments.html</link>
    <dc:creator>Vaguery</dc:creator><dc:subject>XP agility software development planning project-management estimates prediction engineering</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:6d7f93155843/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:XP"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:estimates"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:prediction"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:engineering"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://scholar.google.com/scholar?hl=en&amp;lr=&amp;q=related:2hJ7JsgD0TIJ:scholar.google.com/">
    <title>Linton: Analysis, ranking and selection of R &amp; D projects in a portfolio - Google Scholar</title>
    <dc:date>2007-06-13T18:58:59+00:00</dc:date>
    <link>http://scholar.google.com/scholar?hl=en&amp;lr=&amp;q=related:2hJ7JsgD0TIJ:scholar.google.com/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Among other things, testing the ability to bookmark a "related articles" link at Google Scholar.
]]></description>
<dc:subject>data-envelopment-analysis DEA project-management benchmarking research management portfolio planning</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:eec5907c1c8c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:data-envelopment-analysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:DEA"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:benchmarking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:portfolio"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:planning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.retrospectives.com/">
    <title>Welcome to retrospectives.com</title>
    <dc:date>2007-04-29T13:19:24+00:00</dc:date>
    <link>http://www.retrospectives.com/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[Formalizing good habits in collaborative workflows
]]></description>
<dc:subject>benchmarking learning-by-doing retrospectives project-management knowledge teams project methodologies collaboration worklife</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:19fb801ed316/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:benchmarking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:learning-by-doing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:retrospectives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:knowledge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:methodologies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:worklife"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://malvasiabianca.org/archives/2007/02/dont-broadcast-information/">
    <title>malvasia bianca » Blog Archive » don’t broadcast information</title>
    <dc:date>2007-02-16T14:01:47+00:00</dc:date>
    <link>http://malvasiabianca.org/archives/2007/02/dont-broadcast-information/</link>
    <dc:creator>Vaguery</dc:creator><description><![CDATA[A constant thread in my musing lately: What about the Academy? Can academic research become agile?
]]></description>
<dc:subject>agility information-architecture project-management toyota knowledge management design collaboration</dc:subject>
<dc:identifier>https://pinboard.in/u:Vaguery/b:8d7806887590/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:agility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:information-architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:project-management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:toyota"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:knowledge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Vaguery/t:collaboration"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>