Primavera Gets Agile
School
CIS/525
Instructor
November 22, 2014

Primavera Gets Agile
There is always a best practice and critical success factors an organization can adopt to turn the organization’s entire development organization around in the most amazing way. Prior to adopting agile project management, Primavera development organization experienced problems. Agile techniques should be considered when solving such problems while implementing strategies in adopting agile methodologies. There will be challenges and obstacles that Primavera will face when transitioning to agile project management, but with hard work, these obstacles can be tackled. From since 2004, Agile has continued to have an impact on Primavera project management and its economic growth.
Problems prior to Agile
Some may look at a company like Primavera and think that they had all the necessary software to operate flawlessly, but that was never the case. While scuffling like everyone else, Primavera once maintained the tradition waterfall development approach with a team working tirelessly to dispense high-quality services to a growing and diverse market, as swiftly as possible. In an attempt to complete projects on time, team members had to follow a typical cycle that demanded late hours and weekends. Project managers basically used what was called a command-and-control philosophy. In other words, only managers made decisions without consulting or getting input from their team. This cause the relationship between the development team and other subdivisions to depreciate, since expectations were rarely satisfied. The company itself had a very negative perception of its own team. There was a high level of dependency on the organizational hierarchy. Despite changes made following the development of a software release in 2003, Primavera recognized it was time for more significant changes.