Inefficiencies and Off Shoring

 All  Comments Off on Inefficiencies and Off Shoring
Nov 162013

Was thinking about how some projects seem to be run where the developers think they are being paid per line of code, e.g. $1 per line – 100 lines = $100. At least some of the off-shored projects that we’ve had re-develop for our clients must have been taught this at school – 10,000+ lines of code for a form that should have been a tenth that? ūüėÄ

I wonder if in a typical project, a form could be gauged to be 1000 lines on average for a good developer, you’d end up with better code by the off shored service providers if you paid them for the lines less than the average that the developers didn’t code ‘below’ the average? You could have $1 per line as a starting value for a good developer and potentially double it for a master… Any lines of code outside the average, maybe they didn’t deserve to be paid.

Ideally such a metric isn’t perfect and would require some more thought… Time factors could also be added in a similar way in paying people for their efficiency rather than their deficiency. Could be a fun way to encourage projects to be more efficient.


Planners vs.Reactivists – you certainly wouldn’t build a house without putting up a ‘planned out’ frame first

 All, Business, Project Management  Comments Off on Planners vs.Reactivists – you certainly wouldn’t build a house without putting up a ‘planned out’ frame first
Nov 122013

I was having a good discussion with JC last night around the Agile project methodology and a few good points were raised.

For example, when implementing an Agile Methodology it is important not to forget about Planning and Reflection to become a more efficient team.

This is clearly outlined in the very last paragraph of the Agile Manifesto – “At regular intervals, the team reflects on how¬†to become more effective, then tunes and adjusts¬†its behavior accordingly.” –¬†

It is also clearly outlined in Agile’s Declaration of Interdependence – “We¬†improve effectiveness and reliability¬†through situationally specific strategies, processes and practices.” –¬†

It is too easy to get bogged down in simply delivering to a customer and “keeping them happy” and not devoting or allocating any time to Planning. ¬†The Agile Methodology dictates a fine balance of Planned and Re-Activist based approaches therefore a lean towards either direction also means to stray away from being Agile.

A ‘Spike’ is a very important part of Planning and I can’t stress how important they are to an Agile project.

Therefore make sure they included in between sprints within your Agile based project.

“Spikes will usually¬†take place in between sprints” –¬†

I suppose I just wanted to stress to all ‘Agilists’ out there that they should at least try and allocate more time to Planning to ensure resources are being used efficiently throughout all aspects of your Agile project. ¬†This will surely bring success to all involved.


“Agile on the other hand is a truly open and transparent system of working, one that still gives the client the secure knowledge of fixed charges and fixed timescales by simply adjusting the breadth of features that can be accomplished. So whilst the product owner might not get all of the lower priority features they wished for at that the project‚Äôs conception, they are still guaranteed a viable, usable, and working product for no extra or hidden charges. Likewise, less of the job‚Äôs budget is spent on project management, change orders and scope limitation so more money goes straight to where its needed: design, development and content.”

Web Renovators¬†certainly prides itself on delivering quality solutions to it’s customers and agrees that correct use of Agile project management can certainly assist with this.