Software product development process:
shown in the figure is a software product development experience substantially all of the required process:
1 Start
In the project start-up phase, and its main objective to determine the feasibility of the project. We need the background of the project, stakeholders, solve problems, and so to understand. And prepare project charter and set up a project team, including: product managers, architects, UI engineers, development engineers, test engineers, and so on.
After completion of the above preparation, project start will be held, starting next step will be the end of the work.
2, planning
In the planning phase of the project, relevant stakeholders and project managers need to project the demand side, as well as the project to determine the scope of the project, create WBS, set milestones and project planning of the project. While developing the project management plan, including programs to predict and control the cost, quality, risk.
3) Demand
In the requirements phase, the need for acquisition demand needs analysis, preparation of documents PRD, UI design, high-fidelity design.
And finally into the needs assessment, the assessment by the next step of work
4) design
at the design stage, designers according to requirements documents, design of software systems, including data structures, architecture, business models and rules, process control, module interfaces. Output outline design, detailed design documents, and database design specifications and the like.
5) develop
after a clear demand, development engineers formal entry into the coding stage, depending on the product prototype map, UI rendering, design documentation, select the appropriate development environment, development tools, programming languages, etc. were implemented at this stage is a very very long difficult stage, and it is the core software.
6) functional testing
of software testing is an important means to ensure software quality. After the completion of development engineers to develop, test engineers can be handed over to the test. BUG test engineers to test for feedback to the developers, developers make changes. Functional testing often requires a lot of times until the test is passed, to meet quality requirements.
7）端到端测试
在端到端测试阶段，测试人员根据完整的业务流程设计可以覆盖全流程的端到端测试案例，然后基于端到端案例对系统的各个模块进行全面测试，确保系统能够符合需求和验收质量标准。
8）用户验收测试
用户验收测试阶段，也是通常的UAT(User Acceptance Test)阶段，用户验收测试是最终用户可以检查软件是否符合业务要求的最后阶段。UAT由了解要求并了解构建软件目的的最终用户执行。此测试是在软件运行之前执行的最后一次测试。最终用户使用现实生活场景并为真实数据构建UAT测试用例，用户验收测试在最终用户在上线之前验证软件是否满足这些业务需求方面具有重要作用。
9）上线
所有测试通过，并与客户或者上级达成一致后，系统进行试运行，稳定后上线。
上线包括：上线部署、部署后验证、整理交付物（需求文档、设计文档、安装部署手册、产品帮助等等）和运维移交。
10）收尾
项目的收尾阶段，移交项目成果，释放项目团队，进行项目回顾总结，项目汇报，完成项目结项。
用Leangoo项目管理软件管理阶段式软件产品开发
首先我们在Leangoo中，创建一个项目（选择阶段式项目）
在阶段式项目中，建议使用leangoo中“阶段式软件开发项目”项目模版。
在“阶段式软件开发项目”项目模版中，系统自动为您创建了10个阶段看板（一个阶段一个看板）、1个缺陷看板、1个风险管理看板和1个变更管理看板。
如下图：
在每个阶段看板中，都提供了该阶段需要完成的目标的参考样本，供参考～
1）阶段式看板
一个标准的阶段看板包括了：阶段目标，待办，进行中，已完成，如下图所示：
• milestones: placing a target at this stage need to reach each target a card account for a lane.
• To-do: Put in order to complete specific tasks (work items) milestones needs to be done, a target corresponding to a plurality of tasks. (As shown above the red frame)
• Ongoing: ongoing task.
• Completed: The task has been completed.
2) Defect Kanban
for managing product defect tracking system has set a good flow of defect treatment for you. (May need to customize the process) 
3) risk management Kanban
risk management Kanban is a project risk identification, analysis, during the processing and monitoring, it is important to project management in management activities, effective implementation of software risk management software projects ensure the successful completion of the development work
4) Change Management Kanban
change management process is the basis for the successful delivery of the project, change management to ensure that every change in the environment in the implementation of the project have been previously defined properly, assessment and approval. 
Track the progress of each stage
Tracking the overall progress of the project
Note: For different companies, different products may have different procedures and requirements. Above can be used as a reference -