Agile Methodology

My opinion, Agile Methodology is best used in projects that demand flexibility, continuous improvement, and close collaboration. It supports dynamic project management needs, especially when dealing with an evolving requirements and seeking rapid delivery and feedback cycles that need a third party or a organisational (like Apple) approval.

Agile Project Management responsibilities include developing project plans using Agile methodologies (preferably Scrum), defining project scope, and assigning team members to tasks.  

Agile sprint sessions, manage deliverable timelines and customer expectations. Resources, and budgets planning, proactively to prevent risks, run regular project meetings, update project and RAID logs on a daily or weekly basis. 

Compile weekly summary reports on user stories and key metrics, maintain project documentation and conduct post-project reviews and feedback sessions.

A long with the above detail, the 5 points below are constantly checked off as a key stages in Agile methodology.

  1. Backlog Refinement (or project Backlog Grooming):

    This stage involves refining and prioritising items in the project backlog. Project backlog items (PBIs) are reviewed, clarified, and estimated by the Scrum team in collaboration with the project owner. The goal is to ensure that the backlog contains well-defined and prioritised user stories or requirements for upcoming sprints.

  2. Sprint Planning:

    At the beginning of each sprint, the Scrum team conducts a sprint planning meeting to select items from the project backlog to work on during the sprint. The project owner presents the highest-priority items, and the team collaborates to determine the tasks needed to complete them. The team commits to delivering a potentially shippable increment of work by the end of the sprint.

  3. Sprint Execution:

    During the sprint execution phase, the Scrum team works on the tasks identified during sprint planning. Daily stand-up meetings are held to provide updates on progress, discuss any obstacles or blockers, and adjust the plan as needed. The team focuses on completing the sprint backlog and delivering the agreed-upon increment of work by the end of the sprint.

  4. Sprint Review:

    At the end of each sprint, the Scrum team holds a sprint review meeting to demonstrate the completed work to stakeholders and gather feedback. The project owner presents the increment of work delivered during the sprint, and stakeholders provide input on its functionality, usability, and alignment with their expectations. The team discusses lessons learned and potential improvements for future sprints.

  5. Sprint Retrospective:

    Following the sprint review, the Scrum team conducts a sprint retrospective meeting to reflect on the sprint process and identify opportunities for improvement. The team discusses what went well, what didn't go well, and any potential actions to take in the next sprint to enhance projectivity, collaboration, and overall effectiveness.