We had an independent code review by Readify. It's overdue, but worthwhile. It was a catalyst for addressing a bugbear or two.
You know those design decisions that were made early on and have always been difficult to live with? You know you have to fix it, but you are used to it so it's not urgent.
The good news is that a most of the design decisions and the coding itself got validated. Yes, there is always room for improvement, but we don't have a disaster on our hands.
What was interesting was the workshop going through the review feedback invested a substantial amount of time into 'professional practices.' Topics discussed included taking personal accountability for your work, agreeing on and working to a clear definition of done, abandoning your ego and seriously reflecting and learning.
It was a classic consulting moment where the outsider comes and tells the tam exactly what it's been saying to itself, but the outsider's voice is better heard.
So; A code review. Go get one yourself.
Here is the justification
A code review by an third party helps manage a risk for the organisation by providing independent statement of whether your team are working to a sufficient quality, and that you won't be receiving a difficult to manage application from the project team.
28 April 2010
Subscribe to:
Post Comments (Atom)
Popular Posts
-
I have been having a bit of a discussion over at the IIBA blog with Kevin (VP BOK) and Julian (Chief architect.) It’s migrated over to ...
-
Due to popular demand I have aggregated some information on User Stories and created a simple template. If you feel this would be useful to...
-
Better Projects Templates I am uploading a couple of project document templates to Google Docs. As I add more I'll post them up here. You...
-
You've heard many reasons why project fail. Here is a discussion hosted by BCS on why projects work. The discussion covers four dimensio...
-
The Precedence Diagramming Method ( PDM ) was developed in the early 1960s by H.B. Zachry in cooperation with IBM. It has largely repla...
-
In the below video some of the #10yrsagile participants discuss the role of the Business Analyst. A question for you; Do you agree or di...
-
This is a guest post by Jeff Hobbs. Jeff is a project manager at ActiveState Software who provide pm and collaboration software. Email, ...
-
In one of the Carnivals of Business Analysts the theme was “ Requirements Analysis ." I searched the web far and wide and came up with a n...
-
The definition of a stakeholder is controversial. For example, project team members are generally not considered stakeholders, but in virtua...
-
I have written about the V-Model across several posts. The V model is a testing focused expansion of the software development lifecycle. In ...

0 comments:
Post a Comment