-
Classical process models (waterfall model)
- Feasibility analysis (study do or not do), the output of "feasibility analysis."
- Needs analysis (what research to do), the output "requirements specifications" and product interface prototype drawing.
- Outline design and detailed design, the conceptual model of FIG output (ER FIG), a physical model diagram, class diagrams, timing diagrams.
- Coding / testing.
- On-line / maintenance.
The biggest drawback waterfall model is unable to embrace changes in demand, to see the end product of the entire process, team morale.
-
Agile (Scrum) - Product Owner, Scrum Master, R & D personnel - Sprint
- Product Backlog (user stories, product prototypes).
- Planning meeting (evaluation and budget).
- Daily Development (stand-ups, Pomodoro, pair programming, test first, code refactoring ......).
- Fix bug (problem description, Steps to Reproduce, testers, allegedly sent).
- release version.
- Review meeting (Showcase, users need to participate).
- Review Conference (to make a summary of the current iteration).
Added: Manifesto for Agile Software Development
- Individual and interactive than processes and tools
- Working software is higher than exhaustive documentation
- Customer cooperation than contract negotiation
- Respond to changes than following a plan
