<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.8.4" -->
<rss version="0.92">
<channel>
	<title>traceinthesand.com Blog</title>
	<link>http://traceinthesand.com/blog</link>
	<description>Musing about architecture, architecting and architects</description>
	<lastBuildDate>Sun, 28 Nov 2010 16:48:44 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>The Art of Change: Fractal and Emergent</title>
		<description>Our "The Art of Change: Fractal and Emergent" Executive Report covers

	a model of change, showing how the vectors of change are different at different points in the lifecycle, so that agility means different things, depending on where in the lifecycle the product-market is
	a discussion of how the meaning of business ...</description>
		<link>http://traceinthesand.com/blog/2010/11/28/the-art-of-change-fractal-and-emergent/</link>
			</item>
	<item>
		<title>Why Getting Past &#8220;But&#8230;&#8221; is Important</title>
		<description>
You've probably read Getting to Yes and heard of Getting Past No, so why Getting Past "But"? Well, because "but..." is insidious, making it harder to get past than an outright "no." The person who says "yes, but..." is ostensibly aligning with you. Ostensibly agreeing but for this teensy caveat—this ...</description>
		<link>http://traceinthesand.com/blog/2009/01/14/why-getting-past-but-is-important/</link>
			</item>
	<item>
		<title>Scaling Agile with VAP: Getting Past &#8220;But&#8230;&#8221;</title>
		<description>Our Getting Past "But..." executive report covers two essential areas: 

	
innovation, the circles of innovation model, the innovation process, and what all this means for architects. 

	
scaling agile development projects with VAP (emphasizing just enough design upfront or JEDUF).


These map roughly to the first and second halves of the report, ...</description>
		<link>http://traceinthesand.com/blog/2008/12/17/scaling-agile-with-vap-getting-past-but/</link>
			</item>
	<item>
		<title>Conway&#8217;s Law</title>
		<description>
The Wikipedia community describes Conway's Law like this; I paraphrase it like this: if the architecture of the system and the architecture of the organization are at odds, the architecture of the organization wins. The organizational divides are going to drive the true seams in the system.
The architecture of the ...</description>
		<link>http://traceinthesand.com/blog/2008/02/13/conways-law/</link>
			</item>
	<item>
		<title>Elementary Lessons in Vision and Teaming</title>
		<description>Have you read The Goal? It is (still) a pivotal book in the Lean movement. I’ve been telling architects that The Wheel on the School (a children’s story by Meindert deJong) is the hidden jewel of that genre—namely novelization of business fundamentals. I believe it could be a pivotal book ...</description>
		<link>http://traceinthesand.com/blog/2007/09/28/elementary-lessons-in-vision-and-teaming/</link>
			</item>
	<item>
		<title>Architecture and the Agile Quest</title>
		<description>
If you're interested in Agile and Architecture, here's an interesting read, including the comments: The Demise of the Gantt Chart in Agile Software Projects, by Tate Stuntz on July 31, 2007. I have to agree with David Christiansen: "I’m not convinced there is such a thing as a methodology or ...</description>
		<link>http://traceinthesand.com/blog/2007/09/18/architecture-and-the-agile-quest/</link>
			</item>
	<item>
		<title>Agile Architecting</title>
		<description>The Agile Manifesto articulates the following core values:

	
Individuals and interactions over processes and tools

	
Working software over comprehensive documentation

	
Customer collaboration over contract negotiation

	
Responding to change over following a plan


In essence, informal, iterative, adaptive processes that rely on the collaboration of empowered individuals are strongly favored over formal, bureacratic process and its accoutrements (plans, contracts, comprehensive documentation).  If we ...</description>
		<link>http://traceinthesand.com/blog/2007/09/08/agile-architecting/</link>
			</item>
	<item>
		<title>That Vision Thing</title>
		<description>I get challenged on the question of vision. Is it management's responsibility to come up with the vision, or the architect's? Well, this is my push-back: the architect needs to be sure there is one. Remember: no vision, no destination, a random walk. 

If management has established a shared vision, and ...</description>
		<link>http://traceinthesand.com/blog/2006/10/25/that-vision-thing/</link>
			</item>
	<item>
		<title>Architecture Documentation: Courage to Fly in the Face of Convention</title>
		<description>I have learned what I know about good architecture from working with good architects, many of whom have set the bar for excellence in architecture documentation. That said, I am too often caused to lament that the only thing harder than getting engineers to read the architecture documentation is getting architects to ...</description>
		<link>http://traceinthesand.com/blog/2006/08/25/architecture-documentation-courage-to-fly-in-the-face-of-convention/</link>
			</item>
	<item>
		<title>Opening Up The Innovation Engine</title>
		<description>Corporate and product identity is important in helping customers narrow options and make choices in a flooded marketplace (Malan and Bredemeyer, June 2005).  Identity is a market simplifier. And it means that we have to think about markets and marketing differently. Take the iPod. It is all about identity. The ...</description>
		<link>http://traceinthesand.com/blog/2006/07/05/opening-up-the-innovation-engine/</link>
			</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.448 seconds -->

