Blog
There is no silver bullet in terms of an ideal working model for product development. However, there are countless working models that are universally bad, no matter the context.
You have to build one that is ideal for the situation, by mixing elements (principles, behaviors, methods, tools, processes, roughly in this ranking of diminishing importance) from different sources, while taking into account aspects such as (not exhaustive):
- what is being developed and in which timeframe,
- the individuals and teams involved,
- the decision-makers and other stakeholders,
- the organizational culture.
For a larger organization with multiple products in the same domain (e.g., all products are web apps, or all are mobile apps, or sensors, etc.), a mostly-capable (never “ideal”) working model will evolve over time through practice and deliberate continuousimprovement.
For an organization with heterogeneous development targets and domains, e.g. hardware sensors + mobile companion app + web app + various backends, there will never be one working model applicable across all of them.
Finally: what worked 𝙩𝙝𝙚𝙧𝙚, 𝙩𝙝𝙚𝙣 with 𝙩𝙝𝙤𝙨𝙚 people will not necessary work as well 𝗵𝗲𝗿𝗲, 𝗻𝗼𝘄 with 𝘁𝗵𝗲𝘀𝗲 people.
…except the ability to be cognizant of trade-offs and deliberately adapt!
That last part sounds like “agility” to me. You know, without the roles, rituals, and process straitjackets.
