A friend of name, a teenage actor, asked me about SEO stuff earlier today. She has a website and was concerned it wasn't rising up the rankings very well.
Using a third party website site doesn't give you a huge amount of control but the basics are the same under any circumstances: You need a page with information on the topic at hand; and you want other websites to link to it. I originally had Rachel's name in the title of this post, but since she's now dominating the rankings for here name, I guessed it was no longer necessary! It does help if you have a name like Rachel Kevern though - shared by only a handful of other people in the world 😉
In 2013 I saw Rachel acting & singing in Les Miserables and also saw her singing last night as part of The Voice. Which was excellent! After that, she got the role of Vi, the Reverend's wife in Footloose, at the Z-arts centre in Manchester. Find her at http://rachelkevernactor.wix.com/rachelkevern.
If a team or organisation wants to adopt agile, should they do it all in one, or gradually? How do you overcome problems in agile adoption?
Agile Principles when Adopting Agile
Agile is not about process and methodology; it's about people, relationships and learning and so turns out to be very much democratic and consensus based. Effective adoption presupposes that you've got the team(s) on board; if you have to impose agile, you're probably doing it wrong. You can't adopt faster than your teams and individuals are motivated to adopt.
If you apply the agile manifesto to the project of 'adopt agile' then you'd adopt agile incrementally, of course. I suggest an obvious principle: You can't adopt faster than you can learn.
Agile's take on organisation & adjustment is that teams self-organise with regular reflection, which enables you to see what's not going well and consider ways to correct. There is no learning without feedback. Adopt incrementally with regular reflection and adjustment.
Agile teams puts work items in priority order, in to deliver the greatest business value first. Look at your current pain points – what's not working well – and find out which practices are found to address them. Prioritise changes which add most value.
Risk management is arguably a missing subject in agile, so let's add that here: soberly consider what, at this stage, you are capable of adopting successfully. First adopting practises you're capable of to maximise your chance of early success. The choice to deliver value or to attack risk first is a judgement call. When you're doing something new the risk of failure is high, so that judgement is largely about knowing how new to your team(s) the changes you're making really are.
Finally, agile starts with the vision of a wider community learning. Any fool can learn from their mistakes but the wise learn from others' mistakes too. In the past 10 years, others have already tried out all the mistakes for you. Call in someone in who's done it before.
I'll be speaking at the International Association of Software Architects UK Summit in April, together with Alan Gawthorpe.
Our subject is "Doing architecture with agile teams" and in a short session we'll be covering both the 'human' angle of working with agile teams and the more technical question of what kind of architecture might count as agile (and is it any better than non-agile architecture).
It's been decades since software people started to think about how to cope with requirements changing during the course of an engagement, though other areas of endeavour have surely been doing it since the stone age. Literally.
The state of the art for software, and increasingly for other areas of IT, is Agile. Yet the recognition of agile in contractual relationships has lagged behind, which is odd given that a large part of IT is done by contracting someone.
When all is sunshine and daises this doesn't matter. The time you really really want your written agreements to be right is when things go awry. If you're doing business even with friends & family, it can help to have something in writing.
But how to write a contract for something when you know it's going to change?
This problem came up in a linked-in architects' discussion and I immediately reached for google to find my notes from Susan Atkinson's presentation on Agile Contracts (I saw her present at a Rational User Group conference a couple of years ago). I reduced it to bullet points in /p1201/susan-atkinson-features-of-an-agile-contract, and she was good enough to drop by to correct & update it. She's been developing an Evolve Contract Model with Gabrielle Benefield and the website should be up soon. Meanwhile there is a recent presentation on slide-share at Contract Metrics For Agile.
For those not yet convinced that there's anything wrong with a waterfall-style contract and project, you can read the IEEE 2013 conference paper at http://www.slideshare.net/SusanAtkinson2/ieee-2013-the-flaws-in-the-traditional-contract-for-software-development. nb Open it full-page mode for easy reading.