際際滷

際際滷Share a Scribd company logo

The 7 deadly sins of a product team

Download as PPTX, PDF
Ciprian Sorlea CSM-CSPO
Ciprian Sorlea CSM-CSPO

My presentation at IT Days 2016, talking about the 7 deadly sins of a product team, things that a team "can do" to prevent their product to even have the chance to become successful.

1 of 11
Download to read offline
Ciprian Sorlea Chief Technology Officer @ Nordlogic Software The 7 Deadly Sins of a Product Team
Why do we talk about the sins of a Product Team?
Because everybody loves Unicorns!
What is a Product?
People PRODUCT Processes Technology
What kind of sins are we talking about?
The 7 deadly sins of a product team
Over engineering Over optimization Excessive technology usage Feature creep Pleasure for large quantities of code Over usage of Design Patterns Lack of any decent optimization or consideration for budget No interest in resource usage Lack of interest in Definition Of Done, Definition Of Ready Refusal to use any basic processes and/ or metrics Lack of interest towards Usability, Marketing, SEO and other non- core related areas Pure laziness
Technical debt Blaming the code, previous team, tools, etc. Refusal to understand the stack, end to end and work on specific bits Refusal to understand and own the business responsibility Desire to adopt technology that other people use (without needing it) Lack of unit tests (or any kind of tests) and Continuous Integration Missing/ bad communication Failure to receive / give feedback Unhealthy competition
Key Takeaways
The 7 deadly sins of a product team

More Related Content

The 7 deadly sins of a product team

  • 1. Ciprian Sorlea Chief Technology Officer @ Nordlogic Software The 7 Deadly Sins of a Product Team
  • 2. Why do we talk about the sins of a Product Team?
  • 4. What is a Product?
  • 6. What kind of sins are we talking about?
  • 8. Over engineering Over optimization Excessive technology usage Feature creep Pleasure for large quantities of code Over usage of Design Patterns Lack of any decent optimization or consideration for budget No interest in resource usage Lack of interest in Definition Of Done, Definition Of Ready Refusal to use any basic processes and/ or metrics Lack of interest towards Usability, Marketing, SEO and other non- core related areas Pure laziness
  • 9. Technical debt Blaming the code, previous team, tools, etc. Refusal to understand the stack, end to end and work on specific bits Refusal to understand and own the business responsibility Desire to adopt technology that other people use (without needing it) Lack of unit tests (or any kind of tests) and Continuous Integration Missing/ bad communication Failure to receive / give feedback Unhealthy competition