Posted by Adrian Smith
on August 15, 2009
In many organisations (especially larger commercial or government) it is common for the project governance processes to require an estimate of project costs before funds can be released and the project launched. Therefore, it is necessary to develop an estimate that can be used as the basis of a go/no-go decision.
In the example discussed below, I was asked to create a process for developing an estimate that satisfied the above requirements. Rather than simply creating process flow and swim-lane diagrams, I tried to consider how the process could be adapted and matured over time as the organisation changed over time. In doing so I found the many agile/lean principles were being subtly introduced.
Continue reading…
Posted by Adrian Smith
on February 23, 2009
Before I started work on a recent project, I was asked if Agile methods could be applied to a systems integration project. Naturally I said yes, (responding more from instinct rather than first hand knowledge) – but as soon as I got a chance I typed ‘agile‘ and ‘systems integration‘ into the Google search bar.
Normally this is a pretty fail-safe approach (used by consultants globally) but I was a bit disturbed by how little information related to this activity. Apart from one excellent post and subsequent discussion – there was little to go on.
Continue reading…
Posted by Adrian Smith
on June 27, 2008
I’ve had a couple of first hand experiences using both Follow the Sun and Remote Working models for both engineering design and software development. In each case the model was based on moving the work between sites in different time-zones/geographic locations and the results were mixed. Recently, the issue has come up again at work, as a result of a recent business acquisition and there have been numerous debates on how this might work. So the help clarify my thoughts, I want to consider the costs and benefits, together with some ideas for making and objective decision.
Continue reading…
Posted by Adrian Smith
on January 20, 2008
Agile software development methods evolved as a reaction to traditional project management methods that focused on documentation, change control and the linear execution of tasks. Agile methods recognize the complex and highly non-linear nature of software development and address the associated risks by encouraging a range of working practices. While these practices are well accepted within the software industry, they have not yet permeated into the more traditional engineering design disciplines found in the aerospace or automotive engineering industries. The following considers the how some of the main agile principles and practices associated with Scrum, eXtreme Programming and Test-Driven Development, could be applied.
Continue reading…