This is the fifth article in my series on building Apps. Part I covered the basics of vision and marketing. Part II was a discussion on the importance of reviewing App store guildelines. Part III covered writing requirements and Part IV was about prioritising those requirements.

In Part I of this series we discussed the importance of having a marketing vision and plan before embarking on your new App project. In Part II of this series we discussed how one would go about reviewing App store guidelines prior to creating your App.

We’ve been thinking a lot recently about how to work out if an Agile team is healthy. By healthy I broadly mean happy and productive. It’s not as easy as it sounds. Sick teams will sometimes effectively hide the fact that they are poorly from their managers as they feel that there may be a… Read more »

The topic of feature (or User Story) size is usually a surprising one for teams that are new to Agile. Teams are frequently used to working and releasing very large user stories. Although there is no definite “correct” size for a user story, my vague rule of thumb is that User Stories should on average… Read more »

As part of work I often get involved in security reviews for my software development clients. If you are selling software to a listed company (plc etc) or a larger privately owned company, the chances are that sooner or later you will face one of these beasts. Generally the security review is first presented to… Read more »

In addition to developer-drive unit and integration testing, it is very important to create realistic data sets for acceptance / gui / performance / “ility” etc testing. Creating such a realistic data set is challenging. Realistic data is not ideal data. It is frequently “invalid” data that should not even be in the system in… Read more »