from SCRUM perspective means an iterative and incremental approach to optimize predictability and control risk” (Tomanek and Juricek, 2012:385) By using Agile, risk is minimized as there are short iterations and clearly defined deliverables (Azanha et al., 2017) This is seen as the solution to going over budgets, missing deadlines, and low-quality outputs in projects. An example of this comes from a study administered by Augustine et al. (2005) showcased a project failing and behind schedule using traditional PM methodology such as Prince2. Called in to recover the project, Augustine and Payne used Agile to rescue and sustain the project. As a result, the project was completed within 5 months, within the timeframe and budget and with increased customer satisfaction and business value. Communication with Stakeholders Unlike traditional methodologies which use extensive documentation, to develop the project Agile offers direct communication with stakeholders (Azanha et al., 2017) Agile decreases waste deeply rooted in redundant project meetings as well as repetitive planning and excessive documentation (Rigby, Sutherland and Takeuchi, 2016) The underpinned principles of Agile project management gives more authority to project team members as Agile encourages self-managing teams (Mahalakshmi and Sundararajan, 2013; Agile practice guide, 2017) The involvement and commitment from the project team leads to an increase in motivated (Azanha et al., 2017) However, this could also viewed as a weakness. As in Agile approaches such as SCRUM, the dedication from team members is important and team work is deeply essential. Agile Alliance (2001) state that for a flat and autonomous management structure agile project management teams should contain more individuals. Due to this, if there’s a lack of cooperation, the project will face failure (Mahalakshmi and Sundararajan, 2013) Despite these strengths, Agile mustn’t be used for all projects as it is most suitable for projects that are dynamic with complex problems and unclear solutions (Rigby, Sutherland and Takeuchi, 2016) Understanding the depth of the project before deciding on the project management methodology used is important (Priyanka, 2016) The projects have uncertainty and constant change as traditional methods such as Prince2 don’t have the flexibility to adapt to change within the project (Azanha et al., 2017; Rigby, Sutherland and Noble, 2018)