Agile projects requirements breakdown structure

fibonacci series in nature

In Agile projects, when a set of requirements are received from Clients, it may consist of (a mix of) A few needs, objectives, goals and some partial stories (even though it would have come in a structured document). Re-organizing (re-arranging) those into a requirements breakdown structure (RBS) helps ask right questions to…

Continue reading

You don’t Need User Stories to be Agile

Someone probably told you that you must have user stories to be Agile, right? But really, you don’t need user stories to be agile! I would have you consider what kinds of stakeholders and requirements you have and are trying to meet. Continue reading

Agile Change Requests

Gold dollar symbols falling through an hourglass 3d Rendering.

There are change requests and then there are agile change requests. Now, I hear some of you saying to yourselves: “He is crazy, there is no such thing as ‘agile change request’!” You are right, partly, I agree that agile methods were designed to avoid change requests. But! All change…

Continue reading

Prioritized backlog versus Release-based Planning

Prioritizing a backlog is hard. Using release based planning is easier.

Continue reading

Agile Requirements and the Agile Backlog

Are backlog items and requirements the same thing?

Continue reading