top of page

10 FAQs for Agile Project Managers

Updated: 2 days ago


Agile Project Management

 

Agile Project Management

 

As a Project Manager, having Agile frameworks like Scrum in your toolkit is more important than ever. However, there seems to be a lot of confusion about how exactly to use Agile frameworks to deliver projects. Should you have a charter? Should the Project Manager also be the Scrum Master? This article will discuss 10 common FAQs for Project Managers seeking to use Agile frameworks - like Scrum - to deliver projects.

 

Do you write a charter for an agile project?

Yes, there should be a charter, but it differs from a waterfall project charter. For example, an agile project charter might include a vision statement instead of scope or high-level requirements.

 

Can you have a deadline for an agile project?

Yes, you can, but the scope should be negotiable and learned as the project progresses. It's important to deliver value incrementally. See my recent article Can Scrum Work for Hard Deadlines.

 

How do you handle changing requirements during an agile project?

Agile projects embrace change. Requirements can evolve throughout the project, and the team adapts to these changes through frequent collaboration and iteration. Teams using Scrum to deliver a project should capture requirements in the Product Backlog. The Product Owner is accountable for the content and ordering of the Product Backlog.

 

What is the role of the project manager in an agile project?

The project manager often facilitates, removing obstacles, supporting the team, and ensuring smooth communication flow. They may also handle administrative tasks and help facilitate stakeholder engagement. Often, the Project Manager also takes on the Scrum Master accountability, which could include training the team members on how to use Scrum, facilitating Scrum events, and more.

 

How do you prioritize tasks in an agile project?

The Product Owner is accountable for the content and ordering of the Product Backlog.  Prioritization is typically based on value and urgency, with input from stakeholders and the team. Techniques like MoSCoW (Must, Should, Could, Won't) or Weighted Shortest Job First (WSJF) are commonly used. Ultimately, the Product Owner is accountable for creating an ordered list - the Product Backlog - which shows what the Scrum team will work on next.

 

How do you measure progress in an agile project?

Progress is measured through working software or tangible deliverables. Metrics such as velocity, burn-up or burn-down charts, and customer satisfaction are used to track progress and adjust plans as necessary. In Scrum, the Product Owner is accountable for forecasting future Product delivery. When a Project Manager is working with a Product Owner, then the Project Manager may gather information including a forecast from the Product Owner and use that information to update the status of the Project.

 

What is the difference between Scrum and Kanban?

Scrum is a framework with predefined roles, events, and artifacts, while Kanban is a visual management method that focuses on continuous delivery by limiting work in progress (WIP) and optimizing flow. When people ask me whether they should use Scrum or Kanban, I say, "why can't we do both?". See the Professional Scrum with Kanban class for more details.

 

How do you handle conflicts within an agile team?

The Retrospective is an excellent tool that Scrum teams can use to discuss how to improve the way they work together and how they handle conflicts.

 

How do you ensure effective communication in an agile project?

The Project Manager had an advantage here because the Scrum framework includes five events that help the team to collaborate.  The Scrum framework includes the Sprint, the Sprint Planning, Daily Stand up, Sprint Review and Sprint Retrospective.  Each of these events serves an important purpose and can help the Scrum Master and the Project Manager to ensure that the Scrum team is collaborating effectively and ensure that Stakeholders have a chance to provide input throughout the Agile project.  Additionally, the Scrum framework includes three artifacts - the Product Backlog, the Sprint Backlog and the Increment that is delivered each Sprint.  These artifacts increase transparency for the Scrum team and its stakeholders.

 

What happens if the customer changes their requirements mid-project?

Agile projects are designed to accommodate changes. The team collaborates with the customer to understand the new requirements, assess their impact, and adjust plans accordingly, focusing on delivering the highest value features first.

 

See our recent article Using agile in project management for more on how to run an Agile project).

134 views0 comments

Recent Posts

See All

Comments


bottom of page