Sunday, 12 January 2014

Who's writing your user stories? Or, Agile under analysis.

The programming change from Waterfall to Agile methods was driven by the need to respond faster to client's needs in a digital age. The lack of speed was one of the biggest grumbles from clients as the market shifted before a project was complete. Speed of development was and still is crucial so anything that might streamline the development process was embraced. Now, enter Agile methodology with its sprints, scrums and user stories.

We've discussed the spin-off difficulties that Agile caused for project management because the iterative development cycle was difficult to cost upfront with a projection. This is because in Agile, small pieces of the whole are defined and developed and tested (usually meaning from a programming functionality perspective), shown to the client and approved, amended or thrown out. Some companies have got around this by reckoning from their experience on the usual number of sprints that a project undergoes and estimating a development cost based around this for the clients. There would be provisos that more would cost more and fewer would be less based again on the average cost of a sprint of work. So far so good.

But – isn't there always a but! The small pieces to work on in a sprint have been defined along user stories. This means defining that a typical user would want X and need to do Y to achieve Z (Andy touched on this in a recent post). The user stories are analysed and prioritised involving the client. Now here's the but. Do your user stories really work? Do they give good results when tested in situ with real users? How to write good user stories is generating lots of brain-cell energy. This is the big question.

Now programmers are not going to like the next bit. William Hudson, in his Nov/Dec 2013 article in ACM Interactions, User stories don't help users. Introducing Persona stories, (see also his draft fuller article) he queries whether allowing people not renowned for their interpersonal skills to define user roles is wise. He "found that technology-focused men working in IT had significantly reduced empathy". Don't shoot the messenger here!

Given that there are many people in the wider digital team who reckon that their specialism includes analysing user behaviour - digital architects, usability specialists, any human behaviour specialists such as HCI specialists, instructional designers, training analysts, marketing professionals, subject-matter experts and so on - then getting an acceptable definition of a user story might lead to inter-team debate. Do you suffer with this?

William Hudson makes some salient points. The usual way of defining user stories may miss out on how often the person needs to do this task and what variants might be needed under certain conditions. His fuller article gives a short overview of the history of user stories in Agile environments. The UK Government design brief for defining user stories uses the formula of actor, narrative, goal, for example. Where would this sit with William Hudson’s theory?

You may like the practical hints and tips given by Craig Strong in his blog What makes a Good User Story?, where a basic role definition for a user story is given but he does acknowledge that some stories might need more work.

This is a prickly problem – writing good user stories. Maybe a toolkit might help. See User Story Toolkit from Rally Software.

Anyone got any more tips?

Friday, 3 January 2014

How social are your media?

Happy New Year to all. I hope you're all doing well, and some of you will be sharing such information via social media of various kinds. There's the seemingly ubiquitous Twitter, the suit-and-tie LinkedIn, the snap-and-share Instagram and even the partly-owned-by-Justin-Timberlake musicality of MySpace ... and lots more. Enough social media to be sociable amongst themselves it seems with more interconnections than the New York Subway.

The days of needing to grow your own web pages, and even your own blogs, have moved on to an environment where we're all a kind of DJ, broadcasting our favourite moments and collecting followers like small boys collect stamps.

The Oxford English Dictionary defines social media as "web sites and applications which enable users to create and share content or to participate in social networking" and gives the origin of the term (or at least its first citation) as 2004 with a conference called The Business of Social Media ... so this could be its tenth anniversary, at least of the term itself. MySpace and LinkedIn were formed in 2003, Facebook in 2004, Twitter in 2006 and Instagram in 2010.

Wikipedia's list of social networking sites is instructive. The earliest one dated in the list is classmates.com in 1995 (the UK equivalent, Friends Reunited, dates from 2000). Older than I expected. Even more interesting, and extensive, is the page on social networking itself. This one reads a bit like an abbreviated PhD thesis! It's a big social world out there.

If you're a business it's very difficult to keep up. Since the sites will wax and wane in popularity you will need someone who can follow the trends and advise which networks fit best with your clients' communications. IMHO Twitter and LinkedIn are a minimum (and in my case probably the maximum as well). Facebook seems to be the leader, with most unique visitors, at least in the English-speaking world. The end of 2013 saw a brief flurry of questions about Facebook possibly losing its core teen audience because they didn't want to be on the same network as their parents. This needed more careful examination and fortunately that came from the BBC's Rory Cellan-Jones. Did you know that in part of Australia you can be served a summons via Facebook?

I've scored a couple of successes by contacting companies via Twitter and picked up some interesting followers. Pick the right 'DJs' that you want to follow ... for their news or their jokes or their photos. I'll tweet this iProfessionals blog entry and make the whole thing somewhat recursive. The main thing is that you need to make regular, even if occasional, use of your social media accounts and then people will know where to find you. I'm at @Delverie.

Thursday, 19 December 2013

Agile revisited

Last week's blog from the British Interactive Media Association was on the subject of Going Agile. It reports on a masterclass from Jo Wickremasinghe and Jim Bowes, one of an ongoing series of events from BIMA.

We've commented on Agile in the past. One difficult perception has been how to reconcile the inherent flexibility (which is a good thing) with budgetary planning and hitting deadlines. Jo Wickremasinghe noted that an agile approach has flexibility to cope with big changes that can (and usually do) derail waterfall projects. Change a major parameter and how would the project cope? This becomes especially crucial where a project has a long time scale. (Cue notes about big UK Govt and BBC IT projects.)

You can build mid-term re-assessment into long projects. The European Commission did this with large long-term research projects, even allowing changes of consortium partners. In iMedia terms though this is rather like trying to dam the waterfall part-way down. Having relatively short and clearly defined mini-projects (ie agile sprints) and having the flexibility to plan individual sprints almost as you go along, as circumstances and stakeholder minds change, has to be a better way.

It is easiest if the project can be divided into constituent parts that can be sprinted almost independently, in any order. If you can make features functionally independent then you can sprint them individually. I am about to start on a project like this and even though it's being scoped and checked by potential users we know that real users only come up with good suggestions when they start to use the 'completed' system. Taking an agile approach means features can be released along the timeline, giving more scope for changes.

Moving back to the BIMA presentations, one of Jim Bowes's slides shows a product vision board. With this you can elucidate the target market, what they need, what the product is and what is the value of doing it. He boils it down to one sentence: "As a user I can do this and I get that benefit". For example, "As a user I can find the latest digital camera reviews so I can choose the right one for me".

I recommend checking back to the BIMA blog occasionally, and maybe their events will make it useful for your company to join, especially if you're London-based.

Thursday, 5 December 2013

Educating clients – worth every effort

Often your client's way of thinking is a world away from your development perspective on what is right for them under the circumstances.

Does this statement ring true for you? Winning projects and keeping clients happy are not easy. You are often pulling in different directions, either because you know the technology and what it is capable of, you know they can't afford what you could really give them, or you know how their customers relate to technology and the client isn't the listening type.

Maybe you should consider educating your clients regularly by a drip feed of soft training advice. This is best offered when you're actually not in the throws of a project as they can react badly to such advice then. They are, after all, the clients and paying you to produce what they want.

We came across a few bits of advice that are really worth passing on. Avara - internet marketing consultants - list their five top tips as:
  1. Be careful what you wish for, (really telling the client to think carefully before directing you, the developer, to do something.)
  2. You are not your customer, (sound advice to get the client focused).
  3. Never use the words like/dislike with feedback, (difficult to grasp without the explanation but very compelling so take a look. They suggest substituting, 'that doesn’t work because...').
  4. There's usually a good reason, (this encourages clients to trust your experience before they comment).
  5. What do you want your website to do? (tips on how to get clients to give you clear statements of what they want by agreeing what they wouldn’t want).
How and when to get your soft training messages across might be the subject of some debate. Avara does it on their website. But perhaps you could offer to send through a bi-monthly short article link for your clients, written by you and of interest to you both. This might be a solution. (Or you could direct them to suitable posts in this blog perhaps.) You know your clients and you'll know what is right. The strategy might vary for different clients, but it will be worth it to save some of the differences of perspective that always lead to debate/hassle in projects.

Top marks to Avara for analysing the prime issues they have found problematic with clients and for translating these into a credible, non-threatening set of tips. Their 'related news, views and advice' are worth noting too.

How do you educate your clients?

Friday, 22 November 2013

Templates available for digital project management

Once your processes and procedures are defined, they can be codified into templates to help guide the next generation of your project managers. They should be refined according to your own business practices and experiences and then they act as efficiently and useful as they can be for YOU.

It’s so refreshing to find templates because they can save so much time and energy, as long as they really suit the way you work. They can cut out major headaches analysing what has proved most successful for you. The sticking point is suit the way you work. You still need to adapt them but they can be strong pointers in a right direction. They can serve as a sounding board for checking if you have analysed your way of working without missing out any of the stages.

Often the processes and procedures you are applying are rooted in your company’s high-level approach to managing projects and these in turn are often affected by your market sector. These approaches often relate to the methodology of waterfall, agile or Prince2 project management processes. Can you identify what you are using? Maybe your company uses all of these for different projects according to the client’s needs. Maybe you use a combination of these approaches in one project – this seems to be a trend because the different approaches have their own strengths and weaknesses. We can’t go into this here but you can look up our blogs on the three different approaches or take a squint at: Project Management Methodologies: How do they compare? by Jean Scheid (19/9/12).

Here then are some templates to look at. Some are free, some are not, some are market sector specific, some are software driven. But they do act as a high-level guide to managing projects. They can be used as a sounding board within your company and/or for refining your own processes. Get other people from your company to react to them. Start a business conversation with them. This will be embryonic training in the raw where you’ll do your own needs analysis. Good Luck.

Friday, 15 November 2013

Content marketing and the print versus infographics debate

We’ve all come across the mantra ‘content is king’ but have we really understood what that implies in the digital world? Yes, we understand that consumers skim and scan online information more than printed mediums. Their behaviour has changed, driven by the need to make faster decisions whilst faced with masses of available data. Another mantra we’ve come across is ‘a picture is worth a thousand words’ but that has been hard to prove until now.

Enter the ‘infographic’: a structured visual analysis of a lot of information presented in a visual way. These might look easy to understand and relate to, but they represent a lot of hard analysis of data and the facility to represent this graphically. These are increasingly important skills that have been neglected. Infographics don’t come cheap but they can pay for themselves in the number of people who look at them, the time spent with them and the number of recommendations they get for others to look at them. All these aspects ring the bells for content marketers.

Take for example Accenture’s Infographic of their report for ‘Turbulence for the CMO: Charting a path for the seamless customer experience’, which is based on their survey in 2012 of CMO Insights. We’ll draw your attention to point number 3, 65% of CMOs say digital focus of the company is important but only 7% sat their performance is leading edge. And, point 5 where they want to drive digital orientation throughout the company but 16% meet internal barriers. Equally, apart from those stats and what they mean to us in the digital industry, the medium of the infographic itself is significant. There’s a good deal of synthesis of data presented graphically.

The principle that you need to ‘entertain and educate’ with your content was strongly expressed in the 2013 Content and Marketing Show as discussed in Quba’s blog 12th November, ‘Entertainment, Eyeballs and Personas: insights from the 2013 Content and Marketing Show’.

Doesn’t the concept of infographics (also referred to as data visualisations) meet this principle if handled correctly? Just look at the buzz around Time & Space Visualiser: The story and history of Doctor Who as data visualisations, a book by Paul Smith about Dr. Who that has been controversial for its comedic look and feel (infographic?). Isn’t it designed to entertain and educate?

Where is this leading? Well, Shell Robshaw-Bryan has strong views in her analysis of ‘9 Marketing Insights to Drive Online Success in 2014’, 28th Oct. 2013, where her 9th point emphasises creativity, agility and innovation are needed to grab and hold the attention of audiences. Would infographics fit here? Actually they might help answer some of her other points too – all worth noting.

The rise of ‘Instagram’ and ‘Pinterest’ as social media offshoots is causing a stir in marketing circles too. Instagram is more visually driven while Pinterest lends itself better to sharing visuals than Tweets allowed. There are interesting stats on these at Digit*ally, where more infographics are evident on the Content Marketing page.

However, to be fair, we will try to place the push for infographics in a wider context by mentioning that print content is not dead. Quocirca Insights, November 1st, cover ‘Print Renaissance’, in this digital world. Tangibility, Trust, Retention and Digital Integration are cited as strong reasons for not throwing print out with the bath water. After all, we are print-biased here, as you see, so how could we not promote the balance?

Friday, 8 November 2013

Language? What language?

A long time ago, in a locality far, far away, a group of sixth-form maths students were let loose on the local authority's mainframe computer. Since this was a time when the Beatles were still in the recording studio, there wasn't much choice of programming language. In our case it was FORTRAN 4. This language was designed to fit on punched cards and the syntax was geared to the restrictions that brought.

Actually, it was somewhat amazing that the local council's mainframe ran FORTRAN, since that was the language of the mathematicians and scientists (it had built-in support for complex numbers!). The 'proper' use of the computer was to 'count brooms' and run the payroll, and for that it would have almost certainly used COBOL. As I said, the choice of programming languages in the late 1960s was small. (See the Wikipedia history of them.)

Fast forward to today and while the boxes have shrunk the choice of languages has rocketed (and Fortran is still alive and updating although it has lost its capitalisation, as is COBOL).

I came across several surveys which rank computer programming languages. The way they define is broadly similar (some count SQL, some not ... something to do with infinite loops) but how they get the ranking varies. Here you can find out what's hot and what's not, and possibly tailor your training or hiring policies.

The TIOBE Programming Community Index for October 2013 uses a complicated analysis of appearances in web searches. Their top-5 for last month is C, Java, Objective-C, C++ and PHP, with PHP having moved up one since September to displace C#. Fortran (25th) and COBOL (20th with a bullet) are still hanging in there.

Langpop.com also trawls search engine results together with Craigslist postings, Ohloh and Github. Their top-5 ranking is C, Java, PHP, Javascript and C++. The web site engine allows you to try different searches for the ranking, so that using Github alone you get a top-5 of ObjectiveC, JavaScript, Ruby, Java and Python ... reflecting the more hardcore nature of Github.

Finally (in my straw trawl) came Statistic Brain. This particular listing isn't bang up to date but it provides an interesting comparison between Craigslist (listing programmer jobs ie wants) and SourceForge (listing open source projects ie users). The wants top-5 are PHP, SQL, C++, C and JavaScript ... and the user list is Java, C++, C, PHP and Perl. Other lists show that Perl is losing popularity so that ranking should definitely have changed and C# or JavaScript would probably be in that top-5 now.

Do these stats fit your experience? If someone on your staff asks you what to learn next what would you say? A final word goes to Craig Buckler on Sitepoint. He looked at this very question at the beginning of 2013 and concluded
Ultimately, pick technologies which interest you and never stop learning. Programming skills are always transferable and it'll make you a better candidate when a suitable job eventually arises.