Process of Agile Methodology
1. Plan
This step involves defining the scope of work, requiring clarification, and setting out a roadmap for development. The tick list-icon means making plans. This requires drawing up a to-do list of tasks that have to be done.
2. Design
Here the team designs the structure of the software program; and develops its user interface and different parts of machinery. The layout method is displayed by the icon of a person drawing on the ground: when programming design involves developing sketches, wireframes, and other drawings to visualize the software program.
3. Develop
In this step, one writes the code for the software program. The coding symbols (curly braces) symbolize the improvement system: write, try out, and debug.
4. Test
In this step, the team evaluates whether the software meets the needed specs and doesn’t have any bugs. A symbol of a tool and a test mark stands for the trying-out section, in which you walk computerized checks to develop an eye for defects.
5. Release
This step involves rolling out the software to production. Deployment represents the arrow that points outwards from a container. It involves packaging up the software and making it available to users.
6. Feedback
At this point, the team begins gathering customer feedback to improve the software. The thumbs-up and down icons suggest a rate or feedback. This refers to collecting user comments, as well as those of shareholders and other interested parties for use in improving the software.
How does PMBOK related to Agile?
The Project Management Body of Knowledge (PMBOK) is a comprehensive guide published by the Project Management Institute (PMI) that outlines traditional project management practices. This article focuses on discussing how PBOK is related to Agile.