Guideline: Design Techniques
Relationships
Related Elements
Main Description

Agile: This process allows projects to be processed in small phases or cycles, known as "Sprints". In these cases the focus is more on production than on documentation.

Waterfall: The most common model in software engineering, it consists of five steps that are performed in a linear manner: Ideas Engineering - System Design - Implementation - Tests and Validation - Maintenance

Scrum: The Scrum process tries to solve the problem of time that occurs in the Waterfall process, seeking in the planning phase, only to accomplish enough to start the project. It is based on the Agile structure, using scrum (sprints) that occur within a period of 1-3 weeks. "

PRINCE2: This model seeks from the beginning of the project to structure roles, themes, processes so that all members are well aware of their responsibilities for the successful execution of the project. It can be applied to any project of any nature, as it is a generic non-proprietary project management method "

PERT : In this technique, time is the most important, so an exact time for each task is determined because time is an important factor in project management since it also determines the project budget. "

Adaptive Project Framework: This process prepares teams to anticipate the unexpected and how to act, as in traditional project management, goals and results are adapted to the process, instead of adapting the process to the goals.

Extreme Programming (XP): This methodology, which also has its roots in the Agile structure, has as its main objective, the improvement of product quality, customer satisfaction. It has a short life cycle, seeking perfection in the development process. "

Kanban: Instead of having goals and sprints, your approach is with visual cues, allowing the project team to know what is expected from the tasks within the project in terms of quantity and quality, as well as when the tasks should be carried out.