Jaian Cuttari - Suited Project Management Methodologies

1. Jaian Cuttari - Suited Project Management Methodologies Basically, project management methodology is defined as a system of practises, procedures and rules used to manage a project. It is always important to select the right methodology for project management. Although there are plenty of methodologies, each with their own specialties. Jaian Cuttari defines some suited project management methodologies. Agile Agile methodology is one of the more recognizable methodologies suited for iterative and incremental. This process deals with demands and solutions evolve through the collaborative effort. Agile enables face-to-face interactions and collaboration between business stakeholders and developers throughout the project. It supports a consistent development pace. Projects that require flexibility, Agile is the best suited. Scrum Scrum methodology consists of some values like, commitment, courage, focus, openness and respect. This has the goal to develop, develop and sustain complex products through accountability. Scrum team has roles: Product Owner Development Team The scrum events include Sprint (accomplishment of goals), Daily Scrum (every day of sprint and previous day's achievements) Kanban This methodology focuses on early releases with collaborative and self-managing teams. It is a visual method that aims to deliver results by painting a picture of the workflow process. It achieves efficiency by using visual cues that signal various stages of the development process. Lean This methodology promotes customer value while minimising the waste. Using fewer resources, Lean aims to create more customer value. This identifies following types of wastes (known as 3 Ms): Muda (about getting rid of wastes) variances in the workflow) Waterfall Waterfall is one of the traditional project management methodologies with a linear, sequential design approach where progress flows like a waterfall (downwards in one direction). This methodology stresses the importance of documentation. According to Jaian Cuttari, it emphasises you to move onto the next phase after completion of the other. These phases include: System and Software Requirements Analysis Design Scrum Master Mura (about eliminating Muri (about removing overload) Coding Testing Operations