Video review

Video Review The two refer to models that aid in the management of projects and share the same project fundamentals and standards. Though the two have similar objectives, they have striking subtle differences as Erin finds out. The Iron Triangle was an invention in 1975 to showcase the connection between time, cost and output. Erin finds out that as much as the connection still exists, the concept of the iron triangle is fading and becoming more complicated (Beierwaltes 1).
Agile project management involves a version called scrum which could suit an alteration of requirements to a substantial degree. That is, it could be fitted to be suitable to what the engineers or customers wanted. The traditional iron triangle of waterfall was more rigid and could not accommodate some alterations. The modifications included things that could suit new customer behaviours.
Contrary to the traditional iron triangle of Waterfall the agile model allowed an accelerated time to the market and allowed for aligning of IT to the business. With agile, the results depict an increase in productivity and software quality. There is also greater project visibility and a reduction of risks when compared to the iron triangle model of project management (Beierwaltes 1). Finally, it is less costly for a company or an individual to apply the agile model than the Iron Triangle of Waterfall. It is less costly to maintain the software involved in Agile than that of Iron triangle of Waterfall.
Agile could be used on our project efficiently. The first reason is due to its cost effectiveness both in initial set up as well as the costs of maintenance. In addition, we could quickly alter its specifications to suit the needs of our projects better. There will be increased productivity and better results as a result of the software’s high quality (Beierwaltes 1).
Works Cited
Beierwaltes, Erin. Product Discovery & Agile. 8 October 2014. Retrieved from https://prezi. com/cydv7osqspwt/product-discovery-agile/