Product Managers knife to derive and organize Product Increment

Product Managers knife to derive and organize Product Increment

I would like to start with a question. Have you felt frozen, do you procrastinate, panic, get overwhelmed or have felt completely lost by looking at the amount of decisions and tasks which needs to get done by a specific time.

Every one of us face this situation you be in the role of Students, Scientists, Scholars, Researchers, Politicians,  Authors, Project Managers, etc. I'll discuss this from the perspective of Product Managers as I work with them closely and have lived through various product launches, Product Managers are under constant pressure to deliver value in VUCA environment. 

Need not to mention but  Product managers are the foundations of progressive and new edge organizations and they are rewarded by the value created by the crafted product served to the customers in increments and some of the successful product managers have learned the art of dealing this complexity of delivering value to customers in slices, each slice satisfies the customer need.

In-cases when product managers have fair idea of the end product and business case is available it is likely that a thick requirement document is supplied to team who then could pull work for development. Usually in an environment of large and complex product development: multiple tasks and decisions have to be taken by various stakeholders including product managers, project managers and team and they may get stuck and overwhelmed. To deal with this situation product managers and business analysts slice and dice the work in Salami slices  (features/stories) for development team.

These development Salami slices are of various thickness and they should not be sliced and diced in a food processor (at one go with equal size), once each byte of a single Salami is consumed and feedback loop is completed, Product Managers adjust the outcome and are ready for slicing the next Salami slice (feature/ user story), which produces another potential shippable increment. 

Rule 1: Never break your work upfront in equal slices 

Customer feedback loop is plugged along with each slice of delivery and the whole loop only gets completed when the process of Consumption of outcome, Gather experiences, Learn insights and application of feedback is completed. 

Once customer feedback loop is plugged into the process, the original requirement (the original unfinished work - unfinished Salami roll) is transformed into new Salami Slice which is an outcome of MVP and customer feedback actions. This process results in the value creation for all related stakeholders.

Rule 2: Each slice of your work must be plugged along with customer feedback loop, usually a standard documented practice in organizations.

These series of Nano wins build a momentum of series of success which in-turn results in motivation, empowerment, happiness and success across the eco system.

To Conclude

This techniques is one among the popular technique to divide and concur a mammoth task. Swiss Cheese method and Salami Slice method are other popular methods to eat an elephant one byte at a time. These techniques are generally applied for efficient use of time management and is effective in managing product backlog and increments 

Agile Coaches and Scrum Masters must educate, collaborate and work with Product Owners, Product Managers and Enterprise Architects to effectively utilize the time.

History of Salami Slice

Salami slicing tactics, also known as salami slicing, salami tactics, the salami-slice strategy, or salami attacks,^[1] is a divide and conquer process of threats and alliances used to overcome opposition. With it, an aggressor can influence and eventually dominate a landscape, typically political, piece by piece. 

Reference: https://en.wikipedia.org/wiki/Salami_slicing_tactics