In today’s article, we talk about the common pitfalls that teams make when using an agile framework such as Scrum or Kanban, and what to do about it.

Esteban

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

This post discusses the common pitfalls of using agile frameworks, the concept of Wagile, and the importance of prioritizing business value in agile projects.

When Agile, isn't agile

<p>ironic how it’s called “agile” even though it’s purposefully restrictive in order to be able to update clients on a project’s progress</p>
