Craftgate founder, SCTurkey alumni, Sony, eBay/GittiGidiyor, ACM, iyzico programming, since 2001 with love Payment Orchestration Platform Software Craftsmanship Community
efford estimations primary goal is to complete all tasks no time for testing in development custom frameworks are created to narrow focus and understanding new teammates join to go faster technical dept is accepted
is calculated tons of metrics with no real meaning are collected, like team productivity, velocity, code coverage performance appriasals based on metrics destroys justice & team spirit
will like it product owners as as analysts, no need to know the product internals feature prioritization is for catching the deadline poker planning for hours only few people touch and hear real customers
kept at seniors and architects, who form a separate team everyone has separate duty, has limited visibility on the big picture lack of skill development for others high turover rate with many outsources team mates
by a team a green-field project with latest technologies used an output of a Scrum team running sprints something developed iteratively something you demo at the end of every sprint an output of the team using a board and tasks a product if it is been built as if it is a project
every failure aim is sustainable satisfaction & growth there is no end for growth and development look for continuous improvement seek for good people and processes you touch your customer frequently building a product is like growing your own child
Rolleri EARLY STAGE SCALE STAGE LATE STAGE Main concern: Speed Quality Business Continuity Main Focus: Validation Growth Customer Satisfaction Customer Development Sustainability Customer Loyalty Developed: Product Projects MVP products start to die when it loses capability for innovation and adaptability SIGMOID CURVE OF BUSINESS