Content in the Resources category
Business is coming under increasing pressure to adopt agile practices to reduce costs and deliver more quickly. Agile Analysis describes your requirements and associated features using stories. Typically for use with agile development but it supports structured methods too giving a common analysis method throughout the organization.
QASymphony has announced the release of a comprehensive connector for JIRA Download Version 5 and higher to qTest, their enterprise test management solution. qTest provides a collaborative work environment for teams to manage requirements, design test cases, plan test execution, track defects, and generate status and quality-metrics reports. The qTest connector for JIRA combines the test management features of qTest with JIRA to create a complete QA management solution.
User Stories, designed to keep teams laser-focused on customer needs, are the driving force behind delivering valuable, high quality features, fast. This video discusses how to write great agile software user stories by defining customer value and keeping teams laser-focused on needs.
Hans Brattberg proposes a Scrum product owner checklist. It is a PDF file that presents on one page a mindmap listing all the Scrum product owner requirements, skills and activities.
Aspect-orientation provides a new way of modularization by clearly separating crosscutting concerns from non-crosscutting ones. While aspect-orientation originally has emerged at the programming level, it has now stretched also to the modeling activity.
The International Institute of Business Analysis (IIBA) is an independent non-profit professional association for business analyst. IIBA was established in 2003 as a Canadian Corporation. Its mission is to develop and maintain standards for the practice of business analysis and for the certification of its practitioners. IIBA local chapters exist in many cities in Canada, the USA and around the world.
In this blog post, Borig Gloger presents an Excel spreadsheet that he has created to support Product Owners. This spreadsheet contains a very simple Product Backlog template. You can list your user stories with priority and their number of story point. The spreadsheet then helps you to calculate the amount of story points per Scrum sprint and produce a suitable Burn Down Chart.
George Dinwiddie proposes a list of material that should help you in the task of splitting user stories used to manage requirements in Agile approaches. In his own handout, he explains the difference between stories in the backlog that are often called features or epics and stories selected for development that should generally be small enough to be done in a matter of hours to a couple of days at the most.
Because requirements engineering is recognized as critical to successful software projects we surveyed a number of software practitioners regarding their software development practices during recent software projects. Relationships between requirements practices and software project outcomes enable us to better understand requirements issues and their relationship with project success.
Usability.gov is the primary government source for information on usability and user-centered design. The web site has a page dedicated to use cases that explains what they are and how to use them.