You are here: Home » Archives for estimation

Tag Archives: estimation

Poverty Over – A Case Study, Part 1 – Thinking

Written by Andy Weir. Filed under Blog, production, project management, work. Tagged , , , , , , , , , , , . 200 Comments.

Yesterday we launched povertyover.christianaid.org.uk. It was a fantastic, yet challenging project to work on and over the next few days I’ll be describing the craft of producing this interactive infographic. I say craft because I truly believe that is what we do. We take an idea, whittle it, shape it and fashion it into something that makes sense in the digital arena. Something that the target audience will take meaning from and hopefully – share it with their friends – which was the goal of this website.

When BMB approached us with this brief we were extremely excited to be involved. Robin and I follow a lot of infographic blogs and from the outset we were enthusiastically researching these and looking for great examples of map based infographics. The thought of being paid to create infographics that moved and reacted to data, time and various other filters was very appetising.

From the outset, the data we were to display was clearly defined. For each of the existing 285 countries of the world, a statistician had put together a 500 year history (where possible) of their relative poverty or wealth. Read more here for how these figures were calculated. We were supplied a figure from between 0.1 and 1.0 for each country for every year. It was our job to make this look beautiful, allow people to explore the data in an interesting way and highlight the following key parts of the story:

1. The world has, on the most part, moved out of poverty especially over the last 60 years.
2. There are however vast parts of Africa and Asia that still have a a way to go.
3. Countries that have been extremely poor before they’ve come out of poverty.
4. With further investment, development and aid – it is possible to move the countries remaining in poverty into prosperity.

Initially we looked at many influences and considered lots of different directions for how we were going to start representing the data. We loved Aaron Koblin’s work (Robin blogged about his show at the V&A last year here) and whilst we respect what he does, we quickly realised that we needed to be extremely graphic in our communication style – which was probably quite far removed from Koblin’s work . There were quite a few variables in our brief; wealth, poverty, maps and time. We needed to be single minded in our approach to how this was represented. Here are some of the approaches and influences we looked at:

 

 

 

 

 

 

 


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Carl and Simon – the most excellent creative team at BMB had also researched many different types of maps (this is a whole cartographic language on it’s own). They provided us with some great books like this one.  We were able to find inspiration from many examples here – but also it started reinforcing lots of map do’s and don’ts!

Initially Carl and Simon were extremely keen to represent the data as a globe that the user could spin around themselves. We knew that until we actually started experimenting with the data and the visuals that we just couldn’t be so conceptually ‘nailed down’ just yet. To their (and the BMB producer Tyrone’s) credit they allowed us to be pretty non-specific with how we were going to display the map at this stage. We entered our prototyping phase with gusto, knowing that the team were in for some serious experimentation!

Any period of prototyping needs to have some clear questions to answer. We had three:

a) What was the infographic world going to look like? Was it to be a globe, a flat map, a 3/4 view?
b) How would we represent the changing HDI value? By colour? By the size of countries? By height or behaviour?
c) How far could we push the tech spec? A world map, with all of the country borders etc has hundreds of edges. If we are doing something in 3D how was Flash going to handle all of the interpretation of the data on the fly and then rendering it as 3d values. Should we use Papervision? Away 3D? Should we use 3D models from 3DStudio Max? What could we get away with before it fell over?

We finished our ‘Think’ stage of the project knowing that we had only planned the project in terms of the objectives and the potential of the raw data. Now… looking at the project from outside eyes, this might sound a bit irresponsible and lacking in “traditional” planning techniques, after all it might appear that we had simply created a list of questions based around look and feel, style and technical possibilities. We felt though that we had now fleshed out exactly what the website needed to communicate and we were now in an extremely good place – our Design stage was ready to go.

In my next blog post I will describe how we prototyped and started working out a visual style for the infographic.

 

Agile reading list

Written by Robin Wong. Filed under Reading. Tagged , , , . 26 Comments.

Here’s a collection of some great agile books, in no particular order.

Getting Real, by the guys at 37signals. This book is good at helping you to focus on real value-adding activities. Stay nimble, stay lean, work in short sprints, react to change quickly, and celebrate your victories regularly. They have a nice way to think about prioritising high-value low-cost activities first in a project – start with the UI, it’s going to have the biggest impact on user experience, don’t spend too much time on the back-end to start with, it’s likely to change. lots more gems.

Slack, by Tom de Marco, who wrote a similar book back in the day called Peopleware. A great view on how to best manage your teams to avoid burning them out and increasing their efficiency, the answer? give them some space to do their job. 100% utilisation is madness, I’ve seen people trying to claim it’s possible to plan this and yet still be efficient. Motivated teams with space to do the best job possible will produce a better product that is far more likely to lead to further growth. The flipside is that if you stack people with too much, they end up feeling like a hamster on a wheel, with no sense of autonomy, and they leave.

Agile Project Management with Scrum, by Ken Schwaber. One of the original founding fathers of Scrum, along with Jeff Sutherland. Essential reading for anyone interested in the subject. He does spend a lot of book trying to help you understand why scrum doesn’t work, but this is vital. In the end, it’s helpful when trying to diagnose if things don’t go to plan during a retrospective.

Agile estimating and planning, by Mike Cohn. This book goes hand in hand with the previous one, and gets into more detail on how to set up backlogs, prioritise, monitor burn-down and estimate touchdown for your agile project.