Skip to main content

How to ensure quality (and performance) in outsourced software development projects?

This is a question I posed on the BCS Elite group on LinkedIn..

What ways to BSC Elite members ensure quality (and performance) in their outsourced software development projects?

I have only worked with in-house dev teams and we ensured quality by having a top-notch technical architect, well developed coding standards/processes and a strong QA function at the end (not that quality can be "inspected in" but knowing that little was going to get passed QA ensured better deliverables end-to-end).

But what is the best "formula" for an outsourced development project?

I could see how you might split the project between different vendors (effectively like we did in-house), with someone doing the design, another the development and another the QA and each acting as checks and balances on the other but I suspect that this would be (1) a contractual nightmare and (2) a recipe for "finger pointing" if things went wrong.

I am thinking in particular of SME's that might only have a very small (or no) in-house development capability that are looking for someone to develop a new application or website "end-to-end" so splitting the work would be a big headache.

The simplistic answer is "pick the right vendor" (a bit like picking the right builder or plumber) but most home owners can watch the building work each day and even someone with no building knowledge can have a gut feeling if its being "done right".

Software development is a "black box" to most senior managers and hence doing weekly code walkthroughs isn't really an option and ergo the first they know that they their new app or website is not a quality job is when it falls over on launch...

Any suggestions / checklists / advice gratefully appreciated!

If anyone reads the Blog please feel free to chip in via the Comments!

Comments

Popular posts from this blog

So what else does Operations do? Well, there is a whole organisation run by the UK govermnent to help answer that question! ITIL , or the IT Infrastructure Library, is a library of best practice information that basically tells you everything you need to do to run an IT department. Similarly developers have development methodologies such as RAD, JAD, Agile/XP, and Project Managers have PM methodologies such as Prince 2, PMBok etc to cover off their areas in more specific detail. ITIL breaks it down into 7 key areas: Service Support - deals with the actual provision of IT services such as the service (help) desk, incident management, problem management, release management etc Service Delivery - deals with ensuring that you can continue to DELIVER the service support functions with things like contigency planning, capacity management, service levels etc The Business Perspective - helps to ensure that the IT function is aligned with the organisation's business strategy and that how to...

Load Testing Case Study

Since we are talking about presentations here is another one I did for the Load Testing Expo in 2009. It’s a case study of how we did the performance testing for an internet-facing content/community/jobs site. Test Expo 2009 Site Confidence & Seriti Consulting Load Test Case Study View more presentations from Stephen Thair .

Alexa has performance rankings too!

I must confess that this one had slipped past me… I wasn’t aware that Alexa was now offering performance rankings as well! Alexa now shows an “average load time” as well as a “comparitive ranking” (i.e. 51% of sites are slower). Interesting data for your next website analysis! It’s worth noting that the quoted “1.404 seconds” is about the same as the “repeat view” measurement webpagetest.org (testing from the UK node shows that www.johnlewis.com takes about 7.2 seconds to load with an empty cache, and 1.6 seconds with a primed cache, median values over 5 runs). Presumably this is an average across all Alexa toolbar users, on all johnlewis.com pages (large and small) with empty and primed caches.