Surprise, surprise…
I actually put together a blog post. Who’d have thunk it?
Posted on Tuesday 12 January and comments.
agile.brazism
What killed us was “one more thing.” We could have easily done three major releases that year if we had drawn a line in the sand, said “finished,” and shipped the darn thing. The problem is that the longer it’s been since your last release the more pressure and anticipation there is, so you’re more likely to try to slip in just one more thing or a fix that will make a feature really shine. For some projects, this literally goes on forever.
-
1.0 Is the Loneliest Number — Matt Mullenweg
Good article about the need to actually ship - “Great artists ship” - that’s summed up in one sentence:
But if you’re not embarrassed when you ship your first version you waited too long.
Getting your product out the door, in front of users, is still the best way to find out what they actually want and need, instead of studies and surveys and interviews. Get people to use it, get them to complain about it, and that single act will provide you with all the information you need to prioritize the “What’s Next” list of features for 1.1, 2.0, 3.0 and beyond.
Ship it. Get it out the door.
Posted on Wednesday 10 November and comments.
A meeting has two critical components: an agenda and a referee.
-
Rands In Repose: How to Run a Meeting
I ♥ Rands.
(And, as an aside while looking up the heart character, I also love that Apple has an entire section in their Character Viewer titled “Divination Symbols”. What I like even more is that they’re all the I-Ching.)
Posted on Thursday 19 August and comments.
If you don’t have good leadership skills, the rest of it fundamentally doesn’t matter… If you do not lead and do not take the risk to lead, the transformation won’t occur. One of the barriers for the profession today is that many architects are not prepared to take the risk of leadership.
-
InfoQ: The Role of the Enterprise Architect
Good article, but like many things on InfoQ, light on actual, actionable things to *do*.
The more I get to be an actual architect, instead of an extra pair of hands or a firefighter, the more it’s blatantly obvious that being an architect of course deals with technology, but is mostly understanding what an organization wants to do, how to use technology to get there, and then having the leadership – both the political savvy and the force of will – to get from Here to There.
Crowdsourced testing is the powerful combination of combining web and cloud economics with the effectiveness and efficiency of crowdsourcing. Could this be a game changer?
-
InfoQ: Crowdsourced Testing, Changing the Game
A whole lot of vapor surrounding a pretty good idea, in general: Mechanical Turk meets test scenarios, perhaps? I can imagine how it would work, but I don’t see how it would scale, when there are things like CloudTest and JMeter+EC2 to bring millions of virtual users to bear in a load test.
Revolutions are like that. They invent and destroy and they only go one way.
- Seth’s Blog: First and never
Posted on Saturday 20 March and comments.
Here’s my question: do you or do you not want be the person someone trusts when they need help? Manager or not, do you see the act of someone trusting you as fitting with who you are?
-
Been a while, I know. But, it’s Rands that got me to post this little bit here, and for that I thank him.
Trust is something I feel really strongly about, especially after watching it get eroded quite a bit around here. How do you rebuild this trust, when it’s so severely damaged?
Posted on Friday 19 March and comments.
