The purpose of this spreadsheet is present an integrated, end-to-end set of requirement statement examples, based on the Trips-R-You Case Study. In IIBA® BABOK® V3 terminology, end-to-end means from Business Requirements to Stakeholder Requirements to Solution and Transition Requirements. The case study, and associated artifacts, use the more traditional business terms Goals, High-level Requirements (HLRs), and Detailed Requirements.

Section 3 begins by presenting one additional tool - a Data Dictionary. As the detail for a given HLR is discussed, the data-specific business needs involved are captured using this tool. The idea is to add entries about record types and fields (i.e. entities and attributes) the first time their need is discussed (e.g. an HLR for a specific screen or report). Once captured, those data-specific details are available for reference when those needs come up again, as they will, during discussions involving other HLRs. The detail in the data dictionary is shown to support a transition requirement for a new or updated database schema.

I have created Product Backlog Template, which is attached here.  As, i am new to Agile, i want you guyz to go through it and let me know what additions/changes i should do in it.

Features include: Product Backlog, Sprints Backlog, Product Burndown Chart, User Stories

UPDATED for the BABOK Guide 2.0 !

This familiar checklist uses a Likert scale, and the Knowledge Areas of the BABOK Guide 2.0, to capture a personal estimation of readiness for the CBAP certification exam.

In a summary form, it provides a high-level review of the breadth of knowledge required of certification candidates. With this understanding they can chart an effective course of study, and gain confidence in their readiness as they prepare for the IIBA's professional certification.

Look yourself in the mirror. Get prepared. Take the plunge.

This checklist will help you keep track of your sense of readiness for the CBAP exam.

Estimating the amount of work required to deliver software is hard. Estimating the amount of work in the very early stages of a project is even harder. A method was developed to estimate the amount of work required by analyzing what the system will allow its users to do. That method is called Estimating With Use Case Points.

This MS Excel traceability matrix could be used when a software tool is not available. It lists the business requirements and the functional requirements on a project related to them.