An interesting short article challenging the artificial division between “tactical” and “strategic” solutions, arguing that a continuum from simple solutions with less risk to more complex ones with more risk is also a valuable way of thinking through such decisions.
It seems a comon problem. One of the first steps in implementing an agile process (such as scrum) is to put in place a fixed iteration cycle in development, but but then find difficulties fitting post-development testing (a.k.a “system testing” or “integration”) into the mix.
The main problem with testing after development is that any fixes to problems identified in the follow-on testing have a tendency to become tangled in upcoming work for the next iteration. This in turn can lead to no iteration ever being “clean” enough to actually release.
One possibility for a solution is to reconsider the development-led nature of an iteration, and instead lead it from a set of acceptance tests which are estimated, developed and executed alongside the scheduling and implementation of code changes.
Gojko Adzic, one of my current favourite bloggers on the subject of testing, has attempted to map out an iteration structure which incorporates this approach:
Gojko Adzic » Fitting agile acceptance testing into the development process
I’m definitely enjoying reading Mark Needham’s blog. Today it included an interesting article discussing productivity among individuals, pairs and teams.
Team Productivity vs Individual Productivity at Mark Needham
Hmm. One of those theoretically great but practically useless ideas. An iPhone app aimed at helping commuters and hitch-hikers pair up seems in reality to be a great way for potential thieves to be alerted to the fact that someone else is carrying a valuable iPhone. D’oh!
DEMO: Avego’s Mobile App Spawns Hitchhiking 2.0 — iPhone — InformationWeek
The history of human-computer interaction is littered with alternative ways to enter and manipulate text. From one-handed keyboards through defining every letter as a different stylus swirl to predictive text on a numeric keypad. Here’s another one Swype is a way of entering a whole word with a wiggle of a finger or stylus on a touch screen.
This one looks like it’s building some buzz – I have already seen a blog entry elsewhere where the author wishes that the iPhone would hurry up and get a Swype implementation.
Move over T9, here comes Swype | Crave, the gadget blog – CNET
Hiring software developers is always on the agenda for many companies. The tricky bit is finding the good ones. I linked to an article on this subject back in April, but it’s nice to see that Mark Needham is also writing thoughtful stuff on the topic.
Dreaming of making your fortune selling your great idea for a software app to millions of iPhone users? Perhaps you should read this before you start work.
Apparently Apple have a habit of refusing to sell competing applications through their store. Unfortunately their idea of what that may encompass is vague and seemingly broad. Together these things can result in an otherwise promising application being refused admission, and without Apple’s blessing, nobody can use or buy the application.
A nice article about the potential benefits of colocated working.
AGILE IN ACTION: Why would I want to sit with that bunch of nutters?
An interesting article, apparently based largely on the keynote from Agile 2008. Some clever stuff about estimation, averages, and the wisdom of crowds in the context of software development teams.
For years Frank Carver has been paying attention to the strange world of convergent technology. During that time he has discussed and researched broad subject areas, come to some surprising conclusions, produced and distributed digital media, scattered ideas and opinions like sparks from a firework, and above all consulted for businesses both large and small to help develop and deploy successful systems, services, and products in this highly complex arena.
