Product risk analysis (PRA) is not only useful in testing but is also applicable during the various phases of sequential or agile system development. This article introduces a different application of PRA that elevates it from project level to domain level. It shows how you can go from risk and requirement-based testing to risk and requirement-based development.
The book fifty quick ideas to improve your user stories aims to help people to write better user stories, supporting teams in iteratively delivering products that satisfy the needs of their customers. InfoQ interviewed Gojko Adzic about the format of his new book, when and when not to use user stories, the ideas that the book provides, organizing product backlogs and prioritizing user stories.
Before you start a project, achieving team alignment is essential for efficacy and efficiency. High fidelity interactions with the whole team are far more effective for aligning a team than many emails, documents, and conference calls. This article describes how to do a single full-day inception meeting to get the extended team aligned.
This article shows how to do requirement development in agile environments, covering concepts and offering examples of how an agile team could run CMMI for Development targeted at level 3.
In this article, authors present an empirical study about the software architecture practices for managing non-functional requirements and decision making in software development processes. 2
Agile and CMMI complement each other well. Big organizations with self-organized teams can achieve technical maturity levels, by using a common metalanguage and a good-practices catalog. 1
Lean’s major concept is reducing waste: removing anything that is not adding value to the customer from the process. Steven Peeters explains how you can apply Lean principles in an IT environment. 2