Chris Lukassen - From Product Manager to Product SamuraiChris LukassenProduct Strategy ConsultantXebia
schedule 6 days agoSold Out!
Agile transformation does not mean more effectiveness. We adopt a new way of working but what does it take to reap the benefits? How can the small (Scrum) team beat the incumbent competitor? How can a new product outgrow the companies flagship product? How can a 7 year old judoka throw a much larger and stronger opponent?
Using the principles of Judo we explore what makes Agile product development effective. We make a deep dive in the character traits and behavior of the product owner and finally we look at the environment, what do you need to build products, companies and people to dominate your competitors.
This lightweight talk will offer practical solutions and insights on how to become a better Product Owner, Product Manager or anyone responsible for setting out a Product Strategy. Based on my personal experience as Product Manager, Director, Coach, Teacher (and martial artist).
For it is our responsibility to save the world of crappy products and lead our teams like the Samurai.
Ranjith Tharayil - Change Vector Tracking in emergent designRanjith TharayilSoftware Craftsman | CoachSolutionIQ
schedule 9 months agoSold Out!
A reflective design approach to achieve software design agility by modelling change as a vector and tracking it to aid refactoring decisions.
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.
Change vector tracking doesn’t prevent customers from coming up with requirements that would invalidate previous design assumptions, it helps us in monitoring these changes and aids in making informed decisions of where and when to redesign. It helps us keep a check on design debt which otherwise would be overseen and not addressed at the right time .Design debt is invisible to tools initially, only when it grows beyond a scale tools can catch it. Change vector tracking is a technique to capture this design debt in a very early stage. “A stitch in time saves nine”.
No more submissions exist.