My Photo

My Company

My Blogs

  • The zAgile Story
    Chronicle of an adventure and the incubation of a software company
  • The S-Curve
    The S-Curve of Software Development
  • Overtures
    Personal opinions, thoughts and blah blah blahs

Twitter Updates

    follow me on Twitter

    « Whither "The S-Curve" ;) | Main | Software Predictions for 2006 (At a TIE monthly event) »

    November 18, 2005

    Comments

    Leo

    While writing up a project plan last night, this blog popped up in my head all of a sudden. So I decided to be opinionated again ...

    I have seen many software engineering projects not going as smoothly as expected due to communication gaps among departments. In particular, a commonly seen gap is the one in between product functionality requirements and the engineering specifications. Department managers spend most of their time in back-to-back meetings just to cover various aspects of projects at hand. Such exhaustive exercise is supposed to synchronize mutual expectations among different functional groups. Yet, much of the outcome from these endless meetings often fades away as quickly as the sound wave in the conference rooms and historical email in inboxes.

    With an interactive system containing the essence of a project, communications no longer have to filter through department managers to their own staff. Essentially, this system is a centralized repository keeping the essential elements of a project, at both strategic and tactic levels, up to date at all time and first-handed with minimal "distortion" to all participants across departments. It also serves as a version control system of the entire project. More importantly, it is the reflection of expectations in synchronicity.

    Core strength of such a system lies in the intelligence of how various pieces of information are associated with different components of a project and merged into the flow of the process. In addition, how they get propagated accordingly to individual participants of different roles also decidedly determines the effectiveness of the system.

    Doug

    "Robots cannot deliver software; humans are having enough trouble with it."

    Right. The impulse to routinize work arises out of people's desire to get paid for NOT thinking.

    The comments to this entry are closed.