{"id":37609,"date":"2015-10-26T12:10:00","date_gmt":"2021-02-10T11:00:15","guid":{"rendered":"https:\/\/www.globallogic.com\/latam\/insights\/blogs\/como-priorizar-el-backlog-en-metodologias-agiles\/"},"modified":"2025-01-30T11:27:03","modified_gmt":"2025-01-30T11:27:03","slug":"como-priorizar-el-backlog-en-metodologias-agiles","status":"publish","type":"insightsection","link":"https:\/\/www.globallogic.com\/latam\/insights\/blogs\/como-priorizar-el-backlog-en-metodologias-agiles\/","title":{"rendered":"C\u00f3mo priorizar el backlog en Metodolog\u00edas \u00c1giles"},"content":{"rendered":"
Agile methodologies propose capturing requirements from the user’s perspective. Agile requirements are expressed through <\/span><\/span>UserStories<\/span><\/span><\/em> ( <\/span><\/span>US<\/span><\/span><\/strong> ), which have a particular format:<\/span><\/span><\/p>\n

As a <role> I want <functionality> to achieve <goal><\/span><\/span><\/em><\/strong> .<\/span><\/span><\/p>\n

However, once the expected behavior of the system has been described in a set of UserStories (called a backlog), there is a problem to be solved: in what order will each of them be implemented, that is, where to start.<\/span><\/span><\/p>\n

There are different factors and dimensions to consider<\/span><\/span><\/p>\n