Question

You have just completed two (2) projects in your assessments, Assessment 2 used the PMBOK method, Assessment 3 used the Agile Method.

You have been asked to conduct a review on both projects. With PMBOK a post project review focuses on what went well, issues and any improvements for future projects (Learnings). For Scrum it is done after every sprint in the Sprint Retrospective.

Describe what well with your Agile project

Answer 1

Agile projects come with a set of challenges and problems that are different from those faced by projects following a traditional methodology. This paper covers a selection of considerations for addressing the challenges, failures, and problems that occur in agile projects. Based on an Internet search, just under 50 challenges were identified in introducing agile methodologies into an organization or working with agile projects. The problems include issues with (1) communicating; (2) managing day-to-day operational problems; (3) gaining buy-in from management, customers, and team members; (4) changing culture and mindset; and (5) gaining experience and making it work. Of course, some of the issues and challenges are unique and occur due to differences and idiosyncrasies in the organization or the project.

The Ambler report concluded that agile projects do not fail more than other projects. They succeed at the same level as other iterative methodologies. However, agile projects face a set of challenges and problems related to applying a different approach to project management. According to VersionOne, the top three reasons for agile project failure are:

• Inadequate experience with agile methods
• Little understanding of the required broader organizational change
• Company philosophy or culture at odds with agile values

During the sprint retrospective, the entire team inspects the iteration and decides what can be done to improve the process. The outcomes of retrospective meetings are communicated to all the members; and, the suggestions are incorporated in the next iteration. It makes the retrospectives a never-to-miss exercise for short-cycled improvement and modification to varied circumstances.

7 Key Benefits of Sprint Retrospectives:

1. It helps the support team to identify and resolve the conflict areas.
2. It helps the Agile team to improve the processes continuously by knowing ‘what can be improved’.
3. It allows all the members to share their views for improvement with the feel of ownership.
4. It provides the roadmap for ‘start, stop doing & continue’.
5. It helps the project managers to keep the project on the right track by fixing the priorities and directions.
6. It helps to identify the risk and problem factors at an early stage.
7. It creates transparency and builds trust among the team members that strengthen the team spirit.

Summary: On being asked about the sprint meetings, the majority of Scrum Masters say that they simply ask- ‘What went well? ‘What didn’t work well?’ and ‘What can be improved?’. The importance of sprint retrospective in Agile –Scrum project management lies in learning because it leads the team members towards- ‘what did we learn?’ The continuous monitoring for improvement is the fundamental of Agile project management; and, the sprint retrospective brightens the success prospects.