Agile Product Management

Product Strategy

Product Strategy

Doing the right thing is more important than doing the thing right.

A Strategic plan that accounts & focus on the vision, goals, purpose of the product, product differentiators, business goals and investment by company, is referred as product strategy. Product Strategy is not only influenced, it’s also is inline with product vision and business strategy. 

Elements of product strategy.

3 elements where Product Strategy is derived from are 

  • The market & customer needs.
  • The key features &  differentiators, 
  • The business goals.
 

The market & customer needs : Every product has a target customer and the primary focus area to solve a problem space. Knowing the customer, the market needs is essential as we create the product strategy. Zomato and Uber-eats focus on busy people and solve their hunger needs on the go. while Ola cabs focus on transportation made easy. 

The key features &  differentiators: Every product must be competing with products that are already existing in the market and hence the few key features and differentiators identified would drive the product strategy, remember these are the features that can boost your product sales in competing market. 

The business goals: Sponsor of the product, i.e company look forward to always invest into the best, competitive, high ROI and product that builds a brand for the company. Business goal drives the product strategy. Uber-eats as brand extension for Uber to offer single platform for transportation & food services to their existing customer base. 

Product Strategy

Product Strategy shouldn’t be fixed, and it should be reviewed to constantly accommodate the changes in market needs, business goals and product differentiators.

Test Driven Development - Engineering Practices

Test Driven Development helps the team to focus on quality over quantity. Quality thinking starts before writing a line of code.

Test Driven Development

Test Driven Development (TDD) sometimes is also referred as Test First Development, as the name suggests, this is a technique where the tests for the requirement is written first and then just sufficient code is developed to pass the test, as the test pass, code refactoring is performed and the next requirement is picked up to continue the loop.  

When this engineering practice is used by the team members benefits are,

  • Simple & just sufficient design
  • Achieve high quality product
  • Identify issues and bugs early and quickly
  • Focus on customer requirements / functionality
 
Unfortunately tests suits are not automated or partially used by team members,  they think code developers shouldn’t write tests & the designs don’t emerge if test driven development is followed.

Collective Code Ownership

Collective Code Ownership is a strategy that basically removes the individual ownership on any piece of code developed and invites everyone to own and have rights to edit the code as necessary.

When this engineering practice is used by the team members benefits are,

  • Everyone is accountable for the delivery & quality
  • Reduces the delay in fixing issues due to bureaucracy
  • Develops sense of common goal. 
 
Due to the team structures, roles/responsibilities, and evaluation strategies employed by organizations results in associating individual’s identity with their work. Team members & leaders are scared of the situations when something goes wrong and no one takes the accountability. This results in team member’s behavior that’s far from collective code ownership. 
Engineering Practices Collective Code Ownership

Collective Code Ownership strategy when employed would result in best products, high quality & outcome that is more goal focused. 

Learn more from our certification & training programs

For any inquiries contact

Email : contact@12principles.in
Mobile : +91 9980 505 003, +91 9945 381 381

Naveen Nanjundappa, Certified Scrum Trainer

12 Principles Consulting Naveen NanjundappaWell known for his unique teaching style, Mr. Naveen Nanjundappa has over 19 years of service in IT industry, with experience in most of the standard roles of software development life cycle such as developer, tester, leader, manager of projects and products. He was introduced to XP & Scrum in 2005. Following his passion for coaching, he has spent last 8 years coaching agile transformation, Scrum teams, trained over 4000+ people from various organizations. Expertise in Scrum, Leadership Agility, Organizational Agility, Process Agility, Team Agility, Product Management & Project Management.

CSM / CSPO certification by Naveen Nanjundappa is Transformational, with lot of examples from real life and Indian working culture. Participants will feel empowered, focused and knowledgeable to handle situations at work & most importantly you transformed not just certified!  

Know more about Naveen Nanjundappa

Naveen Nanjundappa, Certified Scrum Trainer

12 Principles Consulting Naveen NanjundappaWell known for his unique teaching style, Mr. Naveen Nanjundappa has over 19 years of service in IT industry, with experience in most of the standard roles of software development life cycle such as developer, tester, leader, manager of projects and products. He was introduced to XP & Scrum in 2005. Following his passion for coaching, he has spent last 8 years coaching agile transformation, Scrum teams, trained over 4000+ people from various organizations. Expertise in Scrum, Leadership Agility, Organizational Agility, Process Agility, Team Agility, Product Management & Project Management.

CSM / CSPO certification by Naveen Nanjundappa is Transformational, with lot of examples from real life and Indian working culture. Participants will feel empowered, focused and knowledgeable to handle situations at work & most importantly you transformed not just certified!  

Know more about Naveen Nanjundappa