Ideation-to-Release

In envisioning our product development process at Lean , I've strived for a structure that not only made sense for our company in 2020 (the year we finished POC ) but continues to resonate today. I am jotting the thought process here in hopes that it helps others in the community.

Assumptions:

We've collectively committed to operating under a "product-led - engineering-executed" organisational framework. This terminology might carry varied interpretations, thus necessitating clarification.

What that means:

The delineation is clear: the product team holds the final authority in delineating our product strategy, ensuring its alignment with the overarching company vision and strategy. Conversely, the engineering team retains the ultimate say in executing, maintaining quality, and ensuring timely delivery. The clarity in these roles fosters efficient collaboration and minimises ambiguity.

What it doesn’t mean:

Crucially, the designation of "final say" isn't intended to foster silos or rigid boundaries between teams. Instead, it's a safeguard to prevent diffusion of responsibility, encouraging cross-functional collaboration. While fluidity between roles is welcomed, decision-making within designated responsibilities must remain clear-cut.

5 stages of the process:

1. Ideation: Visibility on feature request process should be maintained through a central public repository, outlining how requests transition through stages and the frequency of updates. This could be a page, matrix, database, Jira or whatever works for organisation.
   • Ideas are valued regardless of their origin, and crucial questions are addressed, including tracking mechanisms and prioritisation criteria.
   • As needed, brainstorming sessions are conducted and documented, weighing the value proposition against cost and strategic alignment.
   • Agreement on priorities precedes handover to the product team, resulting in a well-prioritised list of product requests, sometimes accompanied by a working proof of concept.
2. Feasibility and Design:
   • Product conducts thorough research, gathering additional feedback as necessary, and crystallises requirements into user stories and use cases.
   • Designing project requirements precedes handover to the engineering team, ensuring comprehensive coverage from basic to edge cases.
   • The outcome includes well-defined use cases, user stories, and a high-level project estimation.
3. Engineering Design and Development:
   • Engineering validates the feasibility of development based on provided specifications, collaborating closely with the product team.
   • Engineering design specs, deliverables, and estimations are produced, accompanied by mapped user stories and tasks for development sprints.
   • The output includes comprehensive design specifications, deliverable agreements, and estimated release timelines.
4. Testing and Validations:
   • Collaborative efforts across engineering disciplines culminate in a comprehensive release plan, including staged rollout strategies.
   • Test cases are meticulously crafted and integrated into development sprints, with reports generated to track acceptance of deliveries.
   • The outcome encompasses detailed test plans, validation reports, and a structured release timeline leading to product deployment.
5. Improvement/Feedback until maturity:
   • A pivotal phase ensuring continuous refinement through feedback loops across all stages, emphasising transparent communication.
   • Discussions focus on feedback collection methods, integration into the process, and risk identification/mitigation strategies.
   • The output entails process enhancements and the incorporation of new feature requests, ensuring ongoing evolution and maturation of our product development lifecycle.

Our exploration of product development has highlighted the paramount importance of establishing clear responsibility definitions and fostering a feedback-driven culture. From ideation to refinement, each stage plays a crucial role in driving innovation and efficiency within organizations. By embracing transparency, collaboration, and continuous improvement, businesses can navigate the complexities of the development journey with confidence, ultimately achieving their goals and delivering impactful solutions to their customers.