This article shows how to do requirement development in agile environments, covering concepts and offering examples of how an agile team could run a CMMI for Development SCAMPI to become appraised at a targeted level 3 for the areas of requirements development and verification.
In this article, authors present an empirical study based on a survey about the software architecture practices for managing non-functional requirements (NFRs) and decision making in software development process. They also discuss about how these requirements are elicited, documented, and validated at different organizations.
Agile methodologies have become mainstream because they provide a better fit to the modern, changing software world. CMMI is a cross-organizational approach which has proven successful in terms of quality assurance and cost when executed properly. Big organizations with self-organized agile teams can achieve technical maturity levels, by using a common metalanguage and a good-practices catalog.
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