Implementing an analytics tool for analyzing site traffic and basic user behavior is pretty easy these days. For most people Google Analytics will work just fine — it’s free, it has a great interface, and it’s trivial to implement.
At Krrb our needs are slightly more complex. While Google Analytics supports the majority of our traffic analysis, it doesn’t give us everything we need.
This article was originally published on Adage.com as the second in a three-part series authored by AREA 17’s leadership team.
At one time or another every agency has considered creating a commercial site that has nothing to do with its client work. Developing a new product takes time, focus and the ability to go into it with your eyes open. And when handled correctly, the payoff can be huge.
At AREA 17 we’ve done it—several times. It has been part of our evolution from a design studio to a full-service agency and has completely changed the way we approach our client work and relationships.
Here at AREA 17 we like to track project scope with User Stories. I completed Scrum Master Certification a few years ago and have been trying to find a suitable alternative to a physical project board ever since. In my opinion there isn’t any better way to track a project’s progress than using physical story cards pinned to a board. Having a visible representation of project status for everyone to see works incredibly well.
At AREA 17 almost all of our projects have a distributed team — often in very distant locations (New York, Paris, Argentina, London, Manchester). This makes sharing project status using a physical device almost impossible.
This is a post that I published on my (now defunct) personal blog a while ago. It’s a general comparison of some concepts in Scrum and their equivalent in a traditional project management workflow. I’ve intentionally avoided mentioning the advantages or disadvantages of either — you can make up your own mind about that.