It’s common for NFRs to take a back seat in requirement gathering sessions. Topics like scalability and security are rarely met with the same excitement or urgency as customer facing features, yet they are critical to a development project’s success.
The goal of this initial preparatory Sprint is to front-load any work necessary to allow the teams to commence Sprint 1 effectively and without impediments. This includes preparing the Project Roadmap, creating the basic skeleton and plumbing for the project and readying the team for feature development.
4 major issues with a vanilla Google Analytics setup, and how to avoid them.
In an age of machine learning, artificial intelligence, hover boards and self-driving cars, are Google, Bing and Yahoo! still reliant on such primitive snippets of information?
It’s common knowledge that the cost of acquiring new customers is often ten-fold that of keeping existing ones.
These days “average” performance just doesn't cut it. To deliver bleeding-edge solutions that differentiate us from our competitors we need bleeding-edge people. Yet when it comes to expansion and hiring new staff, we use age old techniques and science tells us they just don’t work.
Daily stand up meetings energize and empower teams to create better software.
Retrospective sessions help us learn from our experiences and improve the way we work both independently and as a team. Getting together and discussing “how things went” is one approach but for the session to be truly valuable we need to add a little structure to the conversation.
Building a killer product? Learn how to apply proven psychological techniques to grow your user base.
Microsoft products can be useful, and their enormous market share means that everyone knows how to use them. But are they always the best tools for the job?
A brief look at old and new school approaches to team culture and the astounding benefits that many companies are afraid to explore.
An example of an eCommerce site that NEARLY got it right. Learn what they did wrong and how you can avoid the same pitfalls.
Studies show that every additional 1 second in page load time results in a 7% loss in conversion. If you are running an e-commerce site, slow page loads directly affect your revenue. This isn’t big news. But how do you go about addressing performance issues?
Last month I wrote an article highlighting the ease of creating web connected Pebble watch apps. Since then I’ve been keeping an eye out for other wearable devices that are designed to do interesting things with the help the internet.
Forms can be boring. On paper we spend time carefully filling out tiny boxes hoping that the person (or machine) that’s receiving them can interpret our handwriting. Online we hope that our browser can remember enough of our personal information to get us at least half way there. We can’t get away from them but that doesn't mean they have to feel like a chore.
With wearable tech making quite a splash in the media at the moment I thought it timely to write about a recent experiment of mine.