Sitegeist Blog - Beiträge vom November, 2009

Agile isn’t a methodology…

Friday, 20. November 2009 10:50

This might be a post about Agile, the action-packed software development methodology that’s been damming up waterfalls for a few years now.

Agile development is about iterations, working software, self-organised teams and the ability to adapt to change quickly. It casts aside massive functional specifications, requirements documents and 18-month lead times. There’s a lot to love.

It’s worth a look if you’re not familiar. The Wikipedia entry on Agile is a good start. And, like all utopian religions, it even has a manifesto.

But this isn’t a post about Agile. It’s about being agile. Sure, there’s cross-over. The methodology wants to be truly agile. And when it is, it’s terrific and exciting. But more often than not, it isn’t. And whether Agile is agile or not comes down to the people involved.

In my experience, failed Agile processes come unstuck when practitioners approach the process with a religious zeal that doesn’t take the project’s individual circumstances into account.

Two stated Agile principles that derail projects are:

  • Business people and developers must work together daily throughout the project.
  • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

In an interpretation straight out of the Old Testament, too many Agile team leaders and ‘Agile Coaches’ have dictated that the business owner and the development team must sit in the same room. Or maybe a room nearby. With an open door.

This becomes a rule slavishly followed, despite two facts:

  • humans have ‘worked together’ without being co-located for millennia
  • ‘most efficient and effective’ does not mean ‘only’

When the business owner is actually located in another building, suburb, city or even country, developers too often decide that the process is ‘corrupted’ or – worse still – work as if the business owner was in the room.

In Agile, we don’t waste time with pesky documentation. We stick cards on the wall (if we can find a bit of wall not covered by a whiteboard). So if the business owner isn’t in the room to look at the cards…bad luck. Not here to answer a question? Tough.

Stupid.

Ah, but this isn’t a post about Agile, remember? It’s about a mindset; about being. Substitute ‘agile’ for ‘nimble’ or any other synonym that comes to mind. Think about how to work faster and more effectively. There is much to like about the Agile Manifesto. There is much to be disappointed about when considering what it becomes in the hands of neo-technical report-o-phobes.

If you’re working on software development…or development of any kind (including content)…you’d be foolish not to consider working in an agile way. Iterate, discuss, show the boss, review, tweak, and – most of all – actually do it.

But you might want to consider what is being sacrificed by substituting that little ‘a’ for a capital letter…

Thema: Being bad, Trends, Web dev | Kommentare (311) | Author:

One more persona

Friday, 6. November 2009 10:41

Lots of product development and marketing processes call for the creation of personas. Personas are fictional characters, based on real user information, that we then use to test our ideas out on.

If we know that our target market is female, university educated, aged 30-39, married with one child, and interested in netball, we might create a character and name her Fiona. We then assign attributes in keeping with our demographic knowledge, and then flesh her out with additional details we make up.

Her favourite magazine is Marie Claire, she still listens to the Cure, she met her husband Chris at RMIT where they both studied journalism. He’s now a web manager and she’s a marketing director. And so on…

And now, with a small handful of personas, we can ‘market test’ product decisions, marketing initiatives, development ideas and more. It’s not as good as real market testing, but it’s fast and cheap.

Right, so personas are good. They help writers write, designers design, developers build and marketers sell.

But maybe there’s one more persona you should add to your toolbox. Your product – be it a company website, a software product, a blog, a shoe or a brand of coffee – probably has a ‘personality’ and a voice. Why not add flesh to this by developing an internal product persona?

This embodiment of your message can then be used by anyone who has anything to do with the product in question. You’re more likely to create consistent experiences for your consumers/users if everyone in your organisation is channeling the same character and characteristics.

This doesn’t mean that everyone pretends to be ‘Jason’ in the call centre, just that product messages, tone, values and approach are consistent.

And – if you get it right – your persaona might even give you ideas for your next successful step…

Thema: Being good, Trends, Web dev | Comments Off | Author:

Simple & Great

Contact Sitegeist

PO Box 466
Brunswick VIC
Australia 3056

[email protected]

T: 1300 364 116

Search posts