Cross functional build factory - process improvement
David JonesSnr Project Manager| Jones Industries LtdCoventry, United Kingdom
Hi Guys,
I am currently managing a set of projects using a "build factory" style set up, wherein the three core technologies (SAP, Mainframe and MQ in the middle).
Each of the build factories are managed separately, with a team leader for each area.
Requirements come in via a team of business analysts, and its up to the project managers responsible for solution delivery to patch things together and identify a completion date for a work package (based on the three delivery dates from the build factories) for a work package then plan that work package's path through the test region into production.
Now... I have been here for the tail end of one project, and the issues identified seem to point to a fundamental lack of communication between the three teams. Essentially, the first time that an end to end test is initiated is at the point the last build factory has finished (sometimes weeks after the others), and in most instances the "ends" do not match, leading to rework, frustrated resource planners, project over run and increased cost.
One solution I have used successfully in the past is the concept of co-locating the developers with the business analyst (and ideally a tester), and giving them X amount of time to "get it done" - obviously X varies considerably and all usual planning caveats apply here.
The goal being that the guys actually cutting the code work closer so that end product is much better aligned with expectations.
Yes, this is basically an agile process.
Now, to my question - agile, seems to be a dirty word in this organisation. I do not have the influence to change that.
The build factories are geographically very disparate (in some cases on different continents).
I would like to propose that we, use an "agilesque" approach and link the developers using Skype (we all have webcams) to take away the psychological barrier that exists in picking up a telephone, and have the working team be responsible as a group for delivering a working package into test.
How have you guys approached such a pitch in the past, where agile is not considered a viable approach, and the different functional towers are, separated geographically.
Have you implemented such processes - do you have any lessons learned?
