Resource Library

Resource management is always an issue in any project, especially when the stakeholders from whom we need time have operational duties to perform.  If our requirements team was at our disposal 100 percent, always completed activities on target, and worked a full eight hour day without distraction or a loss of productivity, then estimating time would be simple. In this paper, we explore standard approaches to time estimation, the dangers of multi-tasking, and estimation alternatives, which consider work habits and productivity norms.

Linking business analysis skills with the methods of The Open Group’s Architecture Framework, TOGAF®, facilitates stronger IT results that drive business value.

We build requirements at a quantum level to connect the vital elements, which are needed to realize a requirement. As we consider the relationships between the behaviors, actions, and responses, we begin to identify and associate the characteristics and conditions, which will drive and constrain the behaviors. Realizing a requirement means joining these elements together and noting them as elements of the requirement.

The principles in this white paper help you introduce greater predictability into your own Agile requirements activities, both individually and across your organization. As you start to apply these ideas and pose these questions, you'll likely see certain patterns emerge that will help you establish your own set of practices that make Agile work for you.

Effective requirements collection at the outset of the project is the key step that will ensure that the project manager can deliver what is actually expected. In this respect, the business analyst must become a key ally and advisor to the project manager. Most project managers are not trained business analysts, so taking advantage of the skill set that a business analyst can offer can greatly enhance the possibility of project success.