Change Vector Tracking in emergent design – Discuss Agile

Change Vector Tracking in emergent design

Home Forums Past Conference Talks Accepted Talks Proposals for Bangalore Change Vector Tracking in emergent design

This topic contains 1 reply, has 2 voices, and was last updated by  Saket Bansal 5 years ago.

  • Author
  • #4721
    Profile photo of Ranjith Tharayil
    Ranjith Tharayil

    Preface about the talk

    Software design is a field that has always fascinated me and I have tried to be an obedient student trying to learn this art. Like any other design problem, software design is also a wicked problem. Horst Rittel and Melvin Webber defined a “wicked” problem as one that could be clearly defined only by solving it, or by solving part of it .This paradox implies, essentially, that you have to “solve” the problem once in order to clearly define it and then solve it again to create a solution that works.

    Hence you need an architect with magical powers to get your design correct in the first go .This is the core philosophy behind emergent design in which we do not think too much about future . As Uncle Bob sarcastically points out, your customers somehow knows your design and they will come up with a requirement that will break your assumptions and thus your design. In emergent design you embrace aggressive refactoring religiously and few teams rebelliously for the good. It has also been observed that during emergent design refactoring step more focus is towards class design than higher abstract architecture elements. This creates technical debt which can go unnoticed for a long time.

    In this talk I will be introducing a novel technique called change vector tracking that will address the above described problem. Change Vector Tracking is a reflective design approach to achieve software design agility by modelling change as a vector and tracking it through ceremonies like Change Vector Tracking meetings.

    Structure of the talk
    Introduction: 3 min
    Problem definition: 7 min
    Solution, Change vector tracking: 10 min
    Modelling change as a vector: 5 min
    Weighted vectors: 5 min
    Process and ceremonies: 5 min
    Future work : 5 min
    Q&A : 5 min

  • #5810

    Saket Bansal

    Thank you for your talk proposal, we are happy to select it.

The forum ‘Accepted Talks Proposals for Bangalore’ is closed to new topics and replies.

Lost Password