Software product development process:
The figure below shows a software product development is generally subjected to all processes required:
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
During the design phase, the designer 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) Development
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 long difficult stage , is the core software.
6) Functional Test
The 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) end to end testing
In the end the testing phase, testers based on a complete end to end business process design test cases can cover the whole process, and then thoroughly test cases based on the end of each module of the system, ensure that the system can meet the needs of quality and acceptance criteria .
8) User Acceptance Testing
User acceptance testing phase, is usually the UAT (User Acceptance Test) stage, user acceptance testing is the final stage of the end-user can check the software meets business requirements. UAT understand the requirements of end-users to build and understand the purposes of the software. This test is the last test before the execution of software running. End-users to use real-life scenarios and build UAT test cases for real data, user acceptance testing and validation before the end-user on-line software meets these business requirements play an important role.
9) on the line
All tests passed, and after trial operation with customers or superiors agreed systems, on-line after stabilization.
On-line include: on-line deployment, post-deployment validation, finishing deliverable (requirements documents, design documents, manual deployment of installation, product help, and so on) and the transfer of operation and maintenance.
10) ending
The final stage of the project, the transfer of project results, the release of the project team, the project reviewed, the project report, completed projects knot.
How to use Leangoo support phase-in software product development
First we Leangoo, create a project (project selection phase type)
In the staged project, it is recommended to use leangoo in "stage software development project" Project template.
In "stage software development project," project template, the system automatically creates a 10 stage billboards for you, a defect billboard, a billboard and a risk management change management Kanban.
As shown below:
At each stage kanban, the reference samples are provided to the phase of the target needs to be done, by reference ~
1) staged Kanban
A standard phase billboards include: milestones, to-do, in progress, completed, as shown below:
- 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. (Red box as shown above)
- In progress: ongoing task.
- Completion: completed tasks.
2) defects Kanban
For managing product defect tracking system has set a good flow of defect treatment for you. (You may need to customize the process)
3) Risk management Kanban
Kanban is a risk management project risk identification, analysis, processing and monitoring of the process, it is important to project management activity management, software implementation of effective risk management is to ensure the successful completion of software development work of the project
4) Change Management Kanban
The 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 properly defined, assessment and approval before.
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 -