In this guide, we’ll compare the three most popular agile frameworks (besides scrum): scrumban, iterative development, and lean development.

Scrum boards are an important elements of the software development process. They can help a PM and the engineering team deliver impactful products faster.

As a principle, only product backlog items that meet the definition of ready should be considered during sprint planning.

Taking the time to write and execute a spike can save your squad from creating anything that they are unsure about.

Kanban is the simplest way of visualizing the status of the work and understanding the next best action to keep the flow going.

Effective backlog management can make or break your product. By the same token, misunderstanding your backlog can lead to traps.

The stage-gate process divides projects into different stages with gates (reviews) in between them. Results of the previous phase are presented to stakeholders.

As a PM, tracking and managing work via a burndown chart is a shared responsibility with the engineering manager and scrum master of the team.

Review what iterative and incremental development means, weigh the pros and cons, and see how an iterative and incremental development process works in practice by looking at examples.

Deliverables can often feel like an imposed requirement without purpose. So, if agile is such a popular way of working, why are deliverables still around?

Both scrum and Kanban are great and can be practiced in any kind of project, provided you know how efficiently they can be used to deliver.

Scrum isn’t evil by design. It’s just like a game of telephone — by the end, it’s nothing like what it’s supposed to be.